Loading...
Loading...
Found 409 Skills
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Implement a piece of work based on a PRD or set of issues.
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Use when creating new skills, editing existing skills, or verifying if skills are valid before deployment
Use this before touching code when you have a requirement for a specification or multi-step task
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
Implements user stories, writes clean tested code, follows best practices. Trigger keywords implement story, dev story, code, implement, build feature, fix bug, write tests, code review, refactor
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
How to effectively test the application, always use when writing tests
Use when writing, reviewing, or cleaning up RSpec tests for Ruby and Rails codebases. Covers spec type selection, factory design, flaky test fixes, shared examples, deterministic assertions, test-driven development discipline, and choosing the best first failing spec for Rails changes. Also applies when choosing between model, request, system, and job specs.
Use this whenever you encounter any bugs, test failures, or abnormal behavior, and execute it before proposing a fix