semantic-safe-implementation-refactor
Use when the primary change is replacing an implementation while keeping the public surface and technology model materially stable. Triggers: rewrite a messy service behind the same interface, replace legacy logic with a clean module, reimplement a subsystem behind an existing contract, or introduce an adapter or facade so a new implementation can take over. Do not use when the main work is moving module, package, or caller boundaries (use semantic-safe-module-boundary-migration) or when a framework, runtime, version, module system, or programming model change is the main source of risk (use semantic-safe-technology-migration).
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore 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.
