Loading...
Loading...
Found 42 Skills
Software development based on Extreme Programming (XP). Use it when implementing software features of any kind. Coordinates planning, TDD, refactoring, and commits.
Full-process specification for software development, covering requirements analysis, design, pre-development, development, testing, and delivery, including review mechanisms, coding specifications and Git workflow
End-to-end project engineering — from understanding user intent to architecture design, incremental build with verification, and systematic debugging. Covers scheduled tasks (cron jobs), dashboards, web apps, APIs, scripts, and any software the user wants built. Replaces coder + preview-dev with a unified methodology.
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.
Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Orchestrates end-to-end software development using the addyosmani/agent-skills framework. Guides the user through define → plan → build → verify → review → ship phases, spawns subagents for each step, tracks state persistently, and never loses focus on workflow completion. Use when the user says "let's build X", "help me implement X", "walk me through X", or wants structured multi-phase dev guidance. Also triggers when a task is clearly non-trivial and would benefit from phased execution.
Use when solution space exploration is complete and you're ready to create an implementation plan. Enforces "simple over easy" - the fundamentally right solution, not the path of least resistance. Triggers after /design-solution, when a solution has been chosen, or when asked to "make a plan" or "create a plan".
General software development best practices covering code quality, testing, security, performance, and maintainability across technology stacks
[Implementation] ⚡⚡⚡ Implement a feature [step by step]
Builds multi-layer features as vertical end-to-end slices instead of horizontal layers. Each slice is verified before the next begins. Use when: starting any task that spans 2+ layers (DB, API, UI, tests), building CRUD features, implementing multi-step flows, decomposing features into subtasks, or planning implementation order.
Clarify the user’s intent for vague, incomplete, or ambiguous clauses, statements, and requirements before modifying the code.