Refactoring
Code restructuring and optimization
tdd
by brianlovin
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 integration tests, or asks for test-first development.
simplify
by brianlovin
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
first-principles
by majesticlabs-dev
Apply first-principles thinking to break down complex problems into fundamental truths and rebuild solutions from the ground up. Use when solving strategic decisions, breaking through blockers, or challenging assumptions. Triggers on first principles, Elon Musk methodology, fundamental truths, strip assumptions, physics of the problem, rebuild from scratch.
anti-ai-writing
by cdeistopened
Transform AI-assisted drafts into authentic, human-sounding content. This skill provides patterns to detect and eliminate AI tells, frameworks for natural writing, and techniques for creating prose that reads as genuinely human. Use when reviewing any AI-generated content or when writing content that must not appear AI-assisted.
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.
karpathy-guidelines
by caidanw
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
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.
ask-questions-if-underspecified
by hainamchung
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
git-clean-history
by goncalossilva
"Reimplement the current Git branch on a fresh branch off main with a clean, narrative-quality commit history."
marketplace-liquidity
by liqiongyu
"Diagnose and improve marketplace liquidity (match rate/fill rate, time-to-match, reliability) by segment. Produces a Marketplace Liquidity Management Pack: liquidity definition + metric tree, fragmentation map, segment scorecard, supply/demand bottleneck diagnosis, experiment backlog, measurement plan, and operating cadence. Use for Growth teams running two-sided marketplaces."
managing-tech-debt
by liqiongyu
"Manage technical debt by producing a Tech Debt Management Pack (debt register, scoring/prioritization, refactor vs rewrite decision memo, incremental paydown plan, migration/rollback plan, metrics, and stakeholder cadence). Use for tech debt, refactoring, legacy modernization, and migrations."
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."
grey-haven-tdd-python
by greyhaven-ai
"Python Test-Driven Development expertise with pytest, strict red-green-refactor methodology, FastAPI testing patterns, and Pydantic model testing. Use when implementing Python features with TDD, writing pytest tests, testing FastAPI endpoints, developing with test-first approach, or when user mentions 'Python TDD', 'pytest', 'FastAPI testing', 'red-green-refactor', 'Python unit tests', 'test-driven Python', or 'Python test coverage'."
git-safety-hooks
by helderberto
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations or add git safety guardrails.
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.
testing-tdd
by jasonraimondi
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 integration tests, or asks for test-first development.
meta-optimize-skill-md
by jasonraimondi
Reviews and improves existing skills by auditing clarity, trigger quality, workflow completeness, and instruction density, then rewriting SKILL.md with minimal-drift improvements. Use when user asks to improve a skill, review SKILL.md, optimize skill prompts, tighten skill descriptions, or refactor skill documentation.
improve-prompt
by cuipengfei
优化提示词 - 结构化改写后立即执行，禁止扩展范围
decision-framework
by majesticlabs-dev
Walk through decisions using a 3-part framework (first-principles, cost/benefit, second-order effects). Use when choosing between options, evaluating trade-offs, or making high-stakes decisions.
code-simplifier
by ArjenSchwarz
Review and simplify code to reduce complexity and improve maintainability
git-ops
by rube-de
Git hygiene: clean up merged branches, prune stale remotes, and verify repository state.
commits-auto
by Takazudo
Enable automatic committing mode. From now on, commit changes automatically without asking for permission during development. Use when: (1) User says 'commits auto', 'auto commit', 'commit automatically', (2) User wants hands-off development where commits happen as work progresses.
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)