Refactoring
Code restructuring and optimization
unity-code-optimize
by cuozg
Simplify and optimize Unity C# code for clarity, consistency, and performance without changing behavior. Triggers — 'optimize code', 'simplify this', 'clean up code', 'improve readability', 'reduce allocations', 'code optimization'.
solution-space
by open-horizon-labs
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
ask-questions-if-underspecified
by alemar11
Clarify requirements before implementing when a request is underspecified or the user asks for clarification.
ask-refactoring-readability
by NavanithanS
Refactor code for readability using DRY, meaningful names, and modularization.
ask-questions
by ferueda
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
@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"
analyzing-software-tradeoffs
by sumik5
Comprehensive software design trade-off analysis covering code-level decisions (duplication, error handling, flexibility, optimization), API design (usability, versioning), distributed systems (consistency, delivery semantics), and meta-decisions (library selection, trend evaluation, date-time handling). Use when evaluating design alternatives, making architectural decisions, or reviewing trade-offs in existing systems. For specific clean code rules, use writing-clean-code; for microservices patterns, use architecting-microservices; for API endpoint design, use designing-web-apis.
@tank/tdd-workflow
by tankpkg
"Test-Driven Development: RED-GREEN-REFACTOR cycle, three laws of TDD, test-first patterns, and practical workflows. Covers test doubles, testing pyramids, property-based testing, and mutation testing. Triggers: TDD, test-driven development, red green refactor, test first, unit test, failing test, test double, mock, stub, spy, test pyramid, property-based testing, mutation testing, test coverage, testing strategy, write tests."
ask-python-refactor
by NavanithanS
Python refactoring for readability, maintainability, and performance.
ask-flutter-mechanic
by NavanithanS
Flutter maintenance with FVM. Clean builds, iOS/Android fixes, asset generation, release.
moai-lang-rust
by Ven0m0
Rust specialist for async services, safe systems programming, and production tooling with Tokio, Axum, SQLx, and clippy-driven quality checks. Use when building or refactoring Rust code.
ask-conceptual-integrity-sentinel
by NavanithanS
Audit repos for architectural drift, dead code, and abstraction bloat.
developing-python
by sumik5
Modern Python development guide covering project setup, tooling, Pythonic best practices and exercise patterns (file I/O, data manipulation, function design, OOP composition, iterators, comprehension idioms), OOP design principles, GoF design patterns, and software engineering process (SDLC, system modeling, methodologies, project implementation patterns, CI/CD, API design). MUST load when pyproject.toml or requirements.txt is detected. Covers Python 3.13 + uv + ruff + mypy, FastAPI/FastMCP, pytest, Docker, Effective Python items (idioms, data structures, concurrency, testing), software design (encapsulation, Demeter's Law, LSP, Design by Contract, behavioral/creational/structural patterns in Python), and SE practices (SDLC phases, Scrum/Kanban, system architecture, code organization, data persistence, API framework comparison, deployment strategies). For language-agnostic clean code principles, use writing-clean-code. For application logging design and structured logging patterns, use implementing-logging.
ask-effective-llm-coder
by NavanithanS
Best practices for LLM-assisted coding. Declarative workflows, simplicity, tenacity.
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.
spec
by weegigs
Prepare any work for execution planning. Routes to work-type specific workflow.
5d-reflect
by tapania
"Extract learning from completed work to improve future cycles. Use when: (1) After VERIFY phase shows feature complete, (2) End of development iteration, (3) User asks for 'retrospective,' 'lessons learned,' or 'what went well/wrong,' (4) Before starting next major feature. This phase prevents repeating mistakes and compounds learning."
architecture-patterns
by dagba
Choose and implement iOS architecture patterns (MVVM, TCA, Clean Architecture) based on feature complexity. Use when designing architecture for new features or refactoring existing code.
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".
test-driven-development
by HJewkes
Use when implementing any feature or bugfix, before writing implementation code
anthropic-prompt-engineer
by zircote
Master Anthropic's prompt engineering techniques to generate new prompts or improve existing ones using best practices for Claude AI models.
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"