implementation-planner
Break down technical implementation tasks into actionable steps with codebase analysis. Use when the user says "breakdown the task", "plan the implementation" or when you need to decompose complex features, ref...
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Break down technical implementation tasks into actionable steps with codebase analysis. Use when the user says "breakdown the task", "plan the implementation" or when you need to decompose complex features, ref...
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
Context packages and learning patterns. Use when managing context packages, error patterns, or strategies.
Unified debugging workflow enforcing root cause protocol. Investigate → Understand → Reason → Fix. Use when debugging bugs, errors, or unexpected behavior.
Chain multiple operations together in pipelines. Use for multi-step workflows, combining research with analysis, and complex automated tasks.
Inter-agent communication for multi-agent workflows. Use when multiple agents need to coordinate, share information, or reserve resources.
Spawn 5 Opus subagents with randomly-generated distinct personas to debate a problem from multiple angles. Use when exploring UX decisions, architecture choices, or any decision that benefits from diverse persp...
Contextual learning system that remembers patterns and rules from past sessions. Use to get relevant context before tasks, record outcomes, and build a personal playbook of coding patterns.
Design system and token management. Use for managing design tokens, colors, typography, and maintaining design consistency.
Apply Bootstrapped AI Methodology Engineering (BAIME) to develop project-specific methodologies through systematic Observe-Codify-Automate cycles with dual-layer value functions (instance quality + methodology...
Comprehensive error handling methodology with 13-category taxonomy, diagnostic workflows, recovery patterns, and prevention guidelines. Use when error rate >5%, MTTD/MTTR too high, errors recurring, need system...
Systematic API design methodology with 6 validated patterns covering parameter categorization, safe refactoring, audit-first approach, automated validation, quality gates, and example-driven documentation. Use...
Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
Interactive planning skill for Amp. Generates specs, implementation plans, and loop infrastructure through clarifying questions.
Review and simplify code to reduce complexity and improve maintainability
Language-agnostic rulebook for producing, reviewing, and improving elegant code. Use when writing new code, refactoring existing code, reviewing code quality, or when user asks for "elegant", "clean", "maintain...
Migrate Rust code from sacp v1.x to v2.0 role-based API. Use when upgrading sacp dependencies, fixing Builder errors, or when code references MessageAndCx or old connection patterns.
Go >= 1.18 项目中希望用 samber/lo(Lodash 风格泛型库)简化集合/映射/字符串、错误处理、重试/节流/防抖、通道并发或指针空值场景时使用。
Coding standards, modular architecture, and common execution patterns for the PolyFlup Python backend.
Core patterns for data fetching, state management, and user preferences. Use when implementing new features that require getting data from Our APIs, Morpho API, on-chain states or managing shared state.
Architecture patterns for organizing feature modules in the codebase. Use when creating new files, brand new features or pages.
Transform nebulous ideas into sharp, testable frameworks through multi-perspective dialectical interrogation. Use when developing vague intuitions, pressure-testing concepts, structuring half-formed frameworks,...
Intermediate scope for inheritance — like OpenLaszlo's
Rooms as pipeline nodes, exits as edges, objects as messages
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.