global-constants
Generates src/shared/constants/global.ts file containing application-wide constants used throughout the application.
Script and automate repetitive tasks and workflows.
Generates src/shared/constants/global.ts file containing application-wide constants used throughout the application.
Refactors "code slob" (technical debt) into clean, idiomatic Python code, using rigorous verification to ensure zero regressions. Use when the user asks to "refactor", "clean up", or "optimize" a file.
Automatically invoked when writing formal documentation (specs, ADRs, reviews, plans). Ensures consistent structure, appropriate detail level, and proper file location.
Analyzes Claude Code session history to identify repeated workflows and suggest slash commands to automate them
Universal guide for all unmangleJS pass development tasks. Covers creating, modifying, debugging, refactoring, and documenting passes. Integrates with existing project documentation - see CLAUDE.md for complete Pass System guide.
Universal pre-PR checklist that works in ANY project, with or without MCP tools. Use before creating a pull request to ensure quality standards and reduce review iterations.
Use when setting up dotfiles on new machines or creating hostname-based configuration overrides for work/home/different environments
Intelligently update README.md to sync with code changes. LOAD THIS SKILL WHEN: User says "更新 README", "update readme" | new features added | dependencies changed | project structure modified. CAPABILITIES: Detect change type, update feature list, update installation, update examples, preserve license/contributing sections.
Apply Go idioms from “Effective Go” when writing, reviewing, or refactoring Go code so results remain idiomatic, maintainable, and performant.
A quick lookup guide for navigating a repository: where to find endpoints, business logic, models, tests, configs, docs, scripts, plus search patterns and commands
Keep oltre-content-ingestor documentation accurate when code/config/infrastructure changes. Use when implementing features, refactors, or fixes that affect main code, scripts, env vars, integrations (Strapi/Slack/scraping providers). Updates README.md, AGENTS.md docs/, and operational guides, and verifies links/commands stay correct.
Performs structural code search and refactoring using AST-based patterns. Use when searching for code patterns, refactoring code structurally, finding function calls, class definitions, or when the user mentions "ast-grep", "structural search", "code pattern", or needs to find/replace code that's difficult with regex.
Use before committing staged changes when you need to verify all related documentation is current - systematically checks README, CLAUDE.md, CHANGELOG, API docs, package metadata, and cross-references rather than spot-checking only obvious files
Render markmap (.mm.md) files to HTML for committing. Finds all .mm.md files in the project and runs npx markmap to generate interactive HTML mind maps.
After making changes, verify all integration points match. Uses HelixDB to find seams, Repo Prompt to inspect both sides. Trigger after any multi-file change before declaring done.
Base module providing reusable file operations patterns for CUI workflow scripts
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
Manage unpublished content in Quartz static site repos. Use when: (1) User wants to prevent files without `publish: true` from being committed (2) User asks about gitignoring based on frontmatter content (3) User wants to unpublish a note or remove it from git (4) User wants to purge files from git history (5) User asks about the publish workflow with `npx quartz sync` Triggers: "publish", "unpublish", "gitignore frontmatter", "purge from history", "quartz sync"
Backup dotfiles before changes and restore if needed
Update import statements across the codebase when modules are moved or renamed. This skill should be used after refactoring operations to ensure all imports remain functional and properly organized.
Monitor Laravel configuration file changes and automatically manage caches. Use immediately after .env modifications, config file edits, or when user reports "settings not reflecting" or "changes not applied". Prevents stale configuration issues.