Refactoring
Code restructuring and optimization
tdd
by jh941213
테스트 주도 개발 - 테스트 먼저 작성 후 구현. "TDD", "테스트 먼저", "테스트 주도" 키워드에 활성화.
refactor
by v1-io
Use when refactoring code for simplicity, removing duplication, or applying KISS/DRY/SOLID/YAGNI. Triggers on "refactor", "clean up code", "apply DRY".
deslop
by v1-io
Use when removing AI-generated slop, cleaning up verbose code, or removing unnecessary defensive checks. Triggers on "remove slop", "clean up AI code", "deslop".
engineering-discipline
by duyet
Core engineering principles for sustainable, maintainable code. No shortcuts, no hacks. Quality gates before completion.
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.
review-analyst-agent
by michaelboeding
Use this skill to analyze product reviews, find common issues, and prioritize improvements. Triggers: "analyze reviews", "review analysis", "customer feedback", "what are people saying", "product reviews", "review sentiment", "find complaints", "customer complaints", "improvement recommendations", "voice of customer", "VOC analysis", "feedback analysis" Outputs: Prioritized issues, sentiment analysis, improvement recommendations.
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.
Clean Build Artifacts
by Sounder25
Removes ignored build artifacts (bin, obj, node_modules) to reclaim space and fix ghost build errors. Safely respects .gitignore.
Context Window Pruner
by Sounder25
Optimize information density by filtering workspace files based on relevance to the current task. Excludes high-noise files (lockfiles, assets) and prioritizes source code matching semantic queries.
testing
by sebnow
"Use when implementing automated tests. Enforces empirical testing, test pyramid, TDD practices, concurrent testing. Triggers: writing tests, test planning, implementing test cases, TDD, race conditions."
red-green-refactor
by sebnow
"Domain-agnostic TDD methodology for iterative improvement. Enforces baseline measurement, minimal changes, and rigorous testing through commitment devices. Use when applying red-green-refactor workflow to any domain: prompts, skills, code, tests. Triggers: TDD methodology, baseline measurement, iterative improvement, red-green-refactor."
debugging
by axiomantic
"Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack trace/error output. NOT for: test quality issues (use fixing-tests), adding new behavior (use implementing-features)."
refactor-assistant
by AIDotNet
智能代码重构，提供设计模式建议、代码异味检测和保持行为不变的安全转换策略。
ask-questions-if-underspecified
by runkids
Clarify requirements before implementing. Use when serious doubts arise.
tdd
by acedergren
"Test-driven development workflow — write failing tests first, implement minimum code, run full suite, commit. Use when implementing features, fixing bugs, or adding test coverage. Includes mock bootstrap phase for projects with mockReset:true."
code-simplify
by PaulRBerg
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
python-design-modularity
by ahgraber
Use when designing module boundaries, planning refactors, or reviewing architecture in Python codebases. Also use when facing tangled dependencies, god classes, deep inheritance hierarchies, unclear ownership, or risky structural changes.
code-polish
by PaulRBerg
This skill should be used when the user asks to "polish code", "simplify and review", "clean up and review code", "full code polish", "simplify then review", "refactor and review", "simplify and fix", "clean up and fix", or wants a combined simplification and review workflow on recently changed code.
beautiful-prose
by EricGrill
A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.
reflect
by JochenYang
Review current conversation, analyze tasks, errors, and user feedback, extract learning opportunities for skill improvement
thinking-in-bets
by pmprompt
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
learning-notes-organizer
by z-soulx
整理与重构已有学习笔记：重划边界、归类重组、合并冗余、精简口语化表达；优化排版与可读性；为各部分补充引导与注释；按从基础到高级建立学习路径并打通知识关联；同时尽量保留原文 Markdown/HTML 强调标记（如 ==高亮==、、Setext 标题等），输出结构清晰、可检索、便于长期维护的笔记体系。
section-refactor-with-todo-routing
by z-soulx
基于 learning-notes-organizer 的方法论，对指定文件执行"全标题索引+含义/引导注释 + 指定章节重构 + 越界内容路由到合适标题并按需新增待整理容器"的局部重构工作流；用 planning-with-files 输出抽取→规划→映射→交付，范围外章节默认不改，仅做迁移所需最小改动。