Loading...
Loading...
Found 64 Skills
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Use when you have specs or requirements for a multi-step task to break it down into detailed tasks, before executing it
Generates detailed implementation plans with milestones and tasks from business and technical requirements. Embeds best practices including task sizing (30m-2.5h), style anchors, TDD requirements, and quality constraints. Outputs milestones.yaml and milestone-m*.tasks.yaml files ready for development.
Expert TypeScript developer specializing in type-safe application development, advanced type systems, strict mode configuration, and modern TypeScript patterns. Use when building type-safe applications, refactoring JavaScript to TypeScript, or implementing complex type definitions.
Internal skill. Use cc10x-router for all development tasks.
Non-negotiable code quality standards for testing, structure, naming, error handling, and documentation
Test planning and coverage strategy workflow. Use when designing test suites, establishing coverage targets, planning TDD approaches, or assessing testing gaps in existing codebases.
Test-driven development using the RED-GREEN-refactor cycle. Suitable for users who want to build new features or fix bugs with TDD, mention "red-green-refactor", want to use integration testing, or ask about "test-first development".
Use this when you have specifications or requirements for multi-step tasks, before starting to write code
Spec-driven development framework for ecommerce features. Orchestrates from intent to implementation via structured specs and task breakdown. Triggers on "/spec.plan", "/spec.refine", "/spec.clarify", "/spec.tasks", "/spec.run", "I want to build", "I want to add", "create spec", "feature spec", "new feature", "implement feature".
Implement features and write code based on tasks in Plans.md. Use this when the user mentions implementation, adding features, writing code, or creating new functions. Do not use for review or build verification.
Use when you need to move a feature from a vague concept to an executable development plan, and complete requirement analysis, task breakdown, and status tracking within the same plan document.