Loading...
Loading...
Found 318 Skills
Agent development workflow and discipline skills. Use when developing features, debugging issues, managing code branches, writing plans, or ensuring code quality through TDD and systematic processes. Triggers on any software development task that benefits from structured workflows.
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).
Autonomous skill creation agent that analyzes requests, automatically selects the best creation method (documentation scraping via Skill_Seekers, manual TDD construction, or hybrid), ensures quality compliance with Anthropic best practices, and delivers production-ready skills without requiring user decision-making or navigation
Expert guidance for writing fast, maintainable Minitest tests in Rails applications. Use when writing tests, converting from RSpec, debugging test failures, improving test performance, or following testing best practices. Covers model tests, policy tests, request tests, system tests, fixtures, and TDD workflows.
Ping-pong TDD 세션의 첫 번째 단계. TrackerBoot MCP에서 스토리를 가져오거나 직접 붙여넣은 스토리 내용을 받아들이고, 프로젝트 스택과 컨벤션을 감지하며, 협력하여 태스크 분해를 계획하고, /tdd-task와 /tdd-commit이 사용할 .tdd-session.md 파일을 작성합니다.
This skill should be used when a developer is ready to implement a GitHub Task issue and needs to read the full spec hierarchy (Task + Feature + Epic), explore the codebase, produce a concrete Technical Approach with real file paths, and drive TDD implementation against Gherkin scenarios. Triggers on phrases like "implement task
Transform design documents into TDD-based implementation plans with parallelizable tasks. Triggers: 'plan implementation', 'create tasks from design', or /plan. Enforces the Iron Law: no production code without a failing test first. Requires an existing design document — use /ideate first if none exists. Do NOT use for brainstorming, debugging, or code review.
Transform approved Intent into executable phased plan with strict TDD. Each step requires tests first (happy/bad/edge/security cases), then implementation. Use after /intent-review when ready to start development.
Test-Driven Development workflow with session integration. Use when implementing features/bugfixes to enforce RED-GREEN-REFACTOR discipline. Integrates with session-management for enhanced TDD session tracking, checkpoints, and metrics.
Use GitHub Spec Kit (https://github.com/github/spec-kit) to create new requirement definitions and specifications (including specification formulation, specification document creation, and specification design) or append to existing specifications, and generate/update spec.md/plan.md/tasks.md. It is used when requirement definition, requirement addition/modification, requirement organization based on TDD, specification documentation, and execution of Spec Kit's specify/clarify/plan/tasks workflow are required.
Execute all tasks from the task breakdown to build the feature. Use after task generation to systematically implement the planned solution following TDD approach where applicable.
Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes. Use when the user says "write an RFC", "create a proposal", "I need to propose a change", "draft an RFC", "document a decision", or needs stakeholder alignment before making a major technical or process decision. Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation.