commandkit-legacy-migration
Use only when legacy plugin usage already exists.
Works with
Agent Skills format with YAML frontmatter. Claude Code reads it as-is.
--- name: "commandkit-legacy-migration" description: "Use only when legacy plugin usage already exists." license: "MIT" --- # CommandKit Legacy Migration ## Activation guidance Use only when legacy plugin usage already exists. ## Required filesystem expectations - legacy and modern structures may coexist during phased migration - target end state uses `src/app/commands/**` and `src/app/events/**` ## Execution workflow 1. Detect legacy dependencies and plugin usage. 2. Inventory parity requirements. 3. Migrate incrementally by domain/feature slices. 4. Remove `legacy()` only after parity validation. ## Guardrails - Never recommend new legacy adoption. - Keep migration commits small and verifiable. ## Reference index | Name | Description | | ------------------------------------------ | ------------------------------------------------------- | | `references/00-filesystem-structure.md` | Coexistence strategy and target modern structure. | | `references/01-legacy-plugin-detection.md` | How to identify legacy plugin and handler usage points. | | `references/02-migration-plan-template.md` | Stepwise migration plan template with safety checks. | ## Tool index | Name | Description | | ----- | ------------------------------------------------ | | `N/A` | This skill currently has no helper tool scripts. |
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
