Loading...
Loading...
Found 294 Skills
Frontend Store 전문 생성 스킬. "스토어 만들어줘", "Store 생성", "프론트 상태관리" 키워드로 트리거. Backend API 기반 생성, TDD 검증 필수.
Use when the user wants a full feature-development chain: clarify a rough feature idea into a prompt, review it with the user, then hand it to grill-with-docs, to-prd, to-issues, and tdd.
Generate structured product and technical documents through guided discovery. 8 document types: PRD, Brief, Issue, Task, User Story, RFC, ADR, TDD. Use when: defining products, reporting bugs, planning sprints, writing stories, proposing changes, recording decisions, designing systems. Triggers on "create PRD", "create issue", "report bug", "feature request", "create task", "create user story", "create RFC", "create ADR", "create TDD", "create document", "write doc".
Auto-generate project workflow config (docs/workflow.md) from existing PRD and CLAUDE.md with zero questions. Use when user says "set up workflow", "configure TDD", "wire up dev workflow", or after running /scaffold before /plan. Do NOT use for founder setup (use /init) or project scaffolding (use /scaffold).
Create comprehensive unit tests, integration tests, and end-to-end tests using pytest for Python projects. Specializes in FastAPI testing with TestClient, async testing with pytest-asyncio, SQLModel/SQLAlchemy database testing, fixture generation, and test configuration setup. Use when you need test coverage, want to implement TDD/BDD, create test suites for functions or API endpoints, add edge case testing, or improve code quality with automated testing. Triggers include requests like "write tests for this module", "create pytest fixtures", "test this FastAPI endpoint", "setup pytest configuration", or "generate test file".
LOAD THIS SKILL when: implementing new features with TDD, user mentions 'TDD', 'test-first', 'red-green-refactor', 'failing test', or when building Effect services that need thorough testing. Covers TDD methodology, Red-Green-Refactor cycle, Effect service testing with mock layers, and test-first development workflow.
Generate complete automated TDD development pipelines from a todolist.md file. Creates a self-contained directory with autodev.sh, system_prompt.md, gate_check.sh, and task cards that drive Claude Code through spec-anchored, gate-guarded, card-by-card development — fully automated with no human in the loop. Features: TDD 5-step closure, 3-level AI decision protocol, independent acceptance verification, auto-repair on test failure, Bug Hunt phase for post-development P0/P1/P2 bug scanning and fixing. Use when user says "帮我生成 autodev", "create autodev for", "generate autodev pipeline", or needs to turn a todolist.md into an automated gated TDD development pipeline.
Use this skill when deciding what to test, choosing between test types, designing a testing strategy, or balancing test coverage. Triggers on test pyramid, unit vs integration vs e2e, contract testing, test coverage strategy, TDD, BDD, testing ROI, and any task requiring testing architecture decisions.
Automatically discover testing skills when working with unit testing, integration testing, e2e testing, TDD, test coverage, mocking, pytest, Jest, or test automation. Activates for testing development tasks.
Expert knowledge of testing Node.js and Express applications including Jest configuration, Supertest for API testing, unit vs integration vs e2e testing, mocking external APIs, test organization, code coverage, CI/CD integration, and TDD practices. Use when writing tests, setting up testing framework, debugging test failures, or adding test coverage.
Write, review, or debug end-to-end tests using Playwright. Use when asked to 'write e2e tests', 'add Playwright tests', 'test this user flow', 'fix flaky tests', 'create a test suite', or 'debug this e2e failure'. Invoke with /playwright-e2e or when user mentions e2e tests, Playwright, or test automation. Do NOT use for live browser interaction via MCP tools — use playwright-mcp for that. Do NOT use for unit/integration tests — use tdd-guide agent instead.
Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization. Use when writing, reviewing, or refactoring vitest tests, or when user mentions vitest, testing, TDD, test coverage, mocking, assertions, or test files (*.test.ts, *.spec.ts).