Refactoring
Code restructuring and optimization
matt-pocock
by ajoslin
Routes software work through Matt Pocock planning and execution philosophy. Use when the user mentions Matt Pocock, PRD-first planning, PRD-to-issues decomposition, vertical slices, Ralph loop, behavior-first TDD, interface options, or refactor planning.
triz
by ThepExcel
TRIZ systematic innovation methodology with AI-enhanced prompts. Use when: (1) Technical contradiction - improve A but B worsens, (2) Physical contradiction - need opposite properties, (3) Cross-industry solutions via FOS/MOS, (4) Technology evolution prediction, (5) Complex engineering problems. Triggers: "TRIZ", "contradiction", "inventive", "trade-off", "improve without worsening", "ข้อขัดแย้งทางเทคนิค", "innovation breakthrough"
tdd
by helderberto
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow.
code-quality
by samhvw8
"Code quality improvement: review, refactoring, debugging. Phases: review feedback, systematic refactoring, root cause debugging, verification. Capabilities: SOLID/DRY compliance, code smell detection, complexity reduction, bug investigation, verification gates. Actions: review, refactor, debug, verify, validate code. Keywords: code review, refactor, debug, SOLID, DRY, code smell, bug fix, root cause, verification, technical debt, extract method, test failure, completion claim. Use when: reviewing code changes, improving code quality, fixing bugs, reducing technical debt, validating before merge/commit."
candid-validate-standards
by ron-myers
Validate Technical.md for vague rules, linter overlaps, and effectiveness issues
design
by booch
Software design principles and patterns. This skill should be used when making architectural decisions, designing classes or modules, or evaluating code structure. Use proactively when discussing SOLID principles, coupling, cohesion, connascence, refactoring structure, class design, module boundaries, dependency injection, or the Four Rules of Simple Design. (user)
sdlc
by booch
Software development lifecycle guidance. This skill should be used when planning development work, conducting code reviews, or establishing development workflows. Use proactively when reviewing code, preparing commits, creating pull requests, refactoring, or discussing development process and best practices. (user)
testing
by booch
Testing philosophy and practices. This skill should be used when writing tests, designing test strategies, or reviewing test code. Use proactively when discussing TDD, red-green-refactor, test doubles, mocks, stubs, fakes, RSpec, Jest, pytest, unit tests, integration tests, test coverage, or test-first development. (user)
dev-experts
by DeevsDeevs
"Apply opinionated developer personas for architecture decisions, production debugging, language-specific code review, comprehensive reviewer passes, and test strategy. Use when you need an architect plan, devops investigation, Rust/Python/C++ review, grumpy reviewer audit, or tester-driven test plan. Triggers: architect, devops, rust-dev, python-dev, cpp-dev, reviewer, tester, pre-merge review, refactor for maintainability."
split-decision
by ElliotJLT
When facing architectural decisions, technology choices, or strategic trade-offs, present options as a structured comparison and require explicit trade-off acknowledgment before proceeding. Triggers on words like "should we", "which approach", "what's the best way", or when Claude is about to recommend one approach over alternatives. Never present a single recommendation without showing viable alternatives first.
stay-in-lane
by ElliotJLT
Before making changes, verifies they match what was actually requested. Activates when about to modify files, add features, or refactor code. Catches scope creep before it happens - no "while I'm here" improvements.
safe-refactor
by ElliotJLT
When refactoring, rewriting, or migrating critical code paths, orchestrate a safe cycle: assess risks → implement → verify → document. Chains pre-mortem and prove-it with built-in implementation phase. Prevents "refactor broke production" disasters. Activates on "refactor", "rewrite", "migrate", or "clean up" for non-trivial code.
marketing
by aviflombaum
Marketing funnel modeling and conversion metrics. Use for ad spend analysis, CPM/CPC optimization, landing page conversions, waitlist economics, and funnel modeling. Triggers on "ad spend", "cpm", "cpc", "conversion rate", "landing page", "waitlist", "funnel".
business
by aviflombaum
SaaS unit economics and growth strategy. Use for LTV, CAC, MRR/ARR analysis, payback period, churn analysis, Rule of 40, and SaaS financial modeling. Triggers on "unit economics", "ltv", "cac", "mrr", "arr", "churn", "saas metrics".
clean-code-zh
by jackjin1997
éµå¾ª Robert C. Martin çã代ç æ´æ´ä¹éãååï¼è¿è¡ä»£ç 审æ¥ãéæåç¼åã涵çå½åãå½æ°ã注éåé误å¤ççæä½³å®è·µã
ask-questions-if-underspecified
by runkids
Clarify requirements before implementing. Use when serious doubts arise.
markdown-formatter
by maxvaega
Format and clean up markdown documents following best practices
planning-scope-minimization
by OzeroHAX
Minimize changes for bugs/incidents: the smallest safe fix
coder-rules-clean-code
by OzeroHAX
Clean code execution rules for coding agents with verifiable quality gates.
aar
by neurofoo
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
go-fx
by metalagman
Use this skill to build, refactor, or review Go applications using the Uber Fx dependency injection framework. It ensures idiomatic use of Fx for lifecycle management, module-based architecture, and boilerplate reduction.
swiftui-liquid-glass
by VladimirBrejcha
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.
meta.skill-optimizer
by kevinslin
Optimize existing skills and their associated files (SKILL.md, scripts, references, assets) for clarity, concision, and ease of use. Use when asked to optimize, streamline, simplify, or clean up a skill; consolidate duplicated or conflicting instructions; add small, clarifying examples; or run an evidence-based skill review using past runs/sessions and learnings.
typed-holes-refactor
by rand
Refactor codebases using Design by Typed Holes methodology - iterative, test-driven refactoring with formal hole resolution, constraint propagation, and continuous validation. Use when refactoring existing code, optimizing architecture, or consolidating technical debt through systematic hole-driven development.