Refactoring
Code restructuring and optimization
test-driven-development
by HJewkes
Use when implementing any feature or bugfix, before writing implementation code
tdd
by LukasStrickler
"Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests."
flutter-enterprise
by ajianaz
"Lightweight Flutter enterprise development skill focused on feature-based clean architecture. Use when user asks to: (1) Build enterprise Flutter apps with clean architecture, (2) Implement feature-based modular structure, (3) Set up scalable Flutter project organization, (4) Create maintainable enterprise codebase. Triggers: Flutter enterprise app, clean architecture Flutter, feature-based Flutter, enterprise Flutter structure, modular Flutter architecture"
swiftui-liquid-glass
by dagba
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
architecture-patterns
by EngineerWithAI
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
refactor
by DS-codi
One-command orchestrator for module refactors in this Project Memory MCP workspace. Use when the user asks to refactor a module with controlled planning, implementation, review, and testing.
Скоринг Facebook рекламы (крон)
by dengineproblem
ÐÑли Ð½ÐµÑ Ð°ÐºÑивнÑÑ directions или адÑеÑов â ниÑего не делай, не ÑообÑай.
cost-optimization
by EngineerWithAI
Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
self-improve
by HJewkes
Use when a session produced reusable insights, when the user says "learn from this", "remember this", or "improve yourself", or after completing a complex task where patterns were discovered
ask-questions
by ferueda
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
improve-skill
by ThomasRohde
This skill should be used when the user asks to "improve a skill", "optimize a skill", "review a skill", "audit a skill", "apply SkillsBench findings", "make a skill more effective", "refactor a skill", "fix a skill", or mentions improving, optimizing, or auditing an existing Claude Code skill based on research-backed best practices.
refactor
by thoreinstein
Analyze code and suggest refactoring opportunities with blast radius assessment, risk evaluation, and recommended order of operations
spec-refactor
by weegigs
Refactor specification workflow. Use when planning refactoring work to document current state, target state, and compatibility requirements.
improving-skills
by taisukeoe
Improve existing agent skills based on user feedback and best practices. Use when the user wants to fix, enhance, or refactor an existing skill. Gathers user feedback first, then applies technical analysis and implements improvements.
test-driven-development
by liauw-media
"Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor."
agent-orchestration-multi-agent-optimize
by ncdevshiv
"Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability."
spec
by weegigs
Prepare any work for execution planning. Routes to work-type specific workflow.
@tank/clean-code
by tankpkg
Reusable, modular, performant, readable code — guided by KISS, SOLID, and pragmatic design. Covers code smell detection, refactoring recipes, function design, KISS/YAGNI decision frameworks, modularity (coupling, cohesion, boundaries), performance-aware patterns, and readability through cognitive load management. Synthesizes Martin (Clean Code), Ousterhout (A Philosophy of Software Design), Fowler (Refactoring), Metz (Practical OOD), Hickey (Simple Made Easy), Beck (Implementation Patterns), grugbrain.dev. Trigger phrases: "clean code", "refactor", "code smell", "code review", "code quality", "KISS", "keep it simple", "SOLID", "single responsibility", "DRY", "YAGNI", "over-engineered", "too complex", "simplify", "modularity", "coupling", "cohesion", "dependency", "reusable", "modular", "performance", "readability", "cognitive load", "naming", "function design", "extract method", "technical debt", "maintainability", "is this too abstract", "should I abstract", "N+1", "data structure"
pm2-server-control
by viteinfinite
Start and stop a server with pm2 using pm2 start ./my-server --name <name> --no-autorestart, plus common supporting commands for status, logs, restart, and cleanup.
busirocket-refactor-workflow
by BusiRocket
Enforces strict refactoring workflow for TypeScript/React codebases. Use when
loop-codex-review
by corygabrielsen
Automated code review loop with progressive reasoning levels. Runs n parallel Codex reviews (configurable via -n), Claude addresses issues, climbs from low→xhigh reasoning until fixed point (all n clean). Human approval at each iteration.
refactor-clean
by dmonteroh
"Provides an incremental, test-first refactoring workflow for reducing complexity or duplication while keeping behavior stable, best used during technical-debt cleanup or design improvement."
test-driven-development
by trancong12102
"Guides strict Test-Driven Development (TDD) using the Red-Green-Refactor cycle. Ensures no production code is written without a prior failing test. Use this skill when implementing new features, fixing bugs, or refactoring code to ensure high test coverage and design quality. Triggers on phrases like 'TDD', 'write tests first', 'test-driven', 'red-green-refactor', 'watch it fail', 'test first', or 'behavior driven'."
critical-thinking
by spitoglou
Analyze arguments, detect biases, evaluate claims, and improve reasoning. Use when asked to fact-check, identify logical fallacies, evaluate arguments, analyze predictions, find root causes, or think adversarially about plans. Triggers include "evaluate this argument", "logical fallacies", "fact check", "analyze the claims", "identify biases", "devil's advocate", "red team this", "root cause".