Loading...
Loading...
Found 318 Skills
Use this skill whenever you are implementing a feature using TDD.
Write tests following TDD principles. Use when implementing features, fixing bugs, or adding test coverage. Covers e2e, integration, and unit testing patterns.
AI-native software development lifecycle that replaces traditional SDLC. Triggers on "plan and build", "break this into tasks", "build this feature end-to-end", "sprint plan this", "superhuman this", or any multi-step development task. Decomposes work into dependency-graphed sub-tasks, executes in parallel waves with TDD verification, and tracks progress on a persistent board. Handles features, refactors, greenfield projects, and migrations.
Create an actionable Laravel implementation plan—bite-sized tasks with TDD-first steps, migrations, services, jobs, and validation points
Use when you have an approved implementation plan document and need to execute it step by step. Triggers on /execute command, when transitioning from planning with an approved plan, or when resuming execution of a partially completed plan. Provides batch-based execution with TDD, checkpoint reviews, and verification gates.
Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only.
アイデアをPlans.mdに落とし込む。夢を計画に変える魔法使い。Use when user mentions '/plan-with-agent', create a plan, organize tasks, feature planning, or TDD planning. Do NOT load for: implementation, reviews, or setup.
Complete unit testing skill for TypeScript/NestJS projects using Jest, @golevelup/ts-jest, and in-memory databases. ALWAYS use this skill when user needs to: **SETUP** - Initialize or configure unit testing: - Set up Jest for a new project - Configure test infrastructure (jest.config.ts) - Install testing dependencies (@nestjs/testing, @golevelup/ts-jest) - Create mock helpers or test utilities - Set up coverage configuration **WRITE** - Create or add unit tests: - Write, create, add, or generate unit tests - Test a service, usecase, controller, guard, interceptor, pipe, or filter - Add tests for new code or features - Improve test coverage or add missing tests - Mock dependencies or set up test fixtures - Working on any file ending in .spec.ts **REVIEW** - Audit or evaluate unit tests: - Review existing tests for quality - Check test coverage and gaps - Audit testing patterns and conventions - Evaluate assertion quality **RUN** - Execute or analyze test results: - Run unit tests - Analyze test results or coverage reports - Understand test failures or successes - Check which tests are passing/failing **DEBUG** - Fix failing or broken tests: - Fix failing unit tests - Debug test errors or exceptions - Resolve mock issues or setup problems - Troubleshoot test timeouts or flaky tests - Diagnose "undefined" or unexpected results **OPTIMIZE** - Improve test performance and maintainability: - Speed up slow tests - Fix open handles preventing clean exit - Improve test organization - Reduce test execution time - Clean up test code Keywords: unit test, spec, jest, typescript, nestjs, mock, DeepMocked, createMock, AAA, test coverage, TDD, .spec.ts, testing, write test, add test, create test, fix test, debug test, run test, review test, optimize test, test setup, jest config
React component and hook testing patterns with Testing Library and Vitest. Use when writing tests for React components, custom hooks, or data fetching logic. Covers component rendering tests, user interaction simulation, async state testing, MSW for API mocking, hook testing with renderHook, accessibility assertions, and snapshot testing guidelines. Does NOT cover E2E tests (use e2e-testing) or TDD workflow enforcement (use tdd-workflow).
Use when writing, reviewing, or refactoring vitest tests. Load when you see *.test.ts or *.spec.ts files, nested describe blocks, loose assertions (toBeTruthy), over-mocking, slow tests, or async testing needs. Covers AAA pattern, parameterized tests, test doubles hierarchy, mock cleanup, test isolation, and performance optimization. Keywords include vitest, testing, TDD, assertions, mocks, stubs, fakes, spies, beforeEach, describe, it, expect, vi.mock, it.each.
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Test-driven development via red-green-refactor with an auditable commit protocol. Use when implementing any feature, bugfix, refactor, or behavior change before writing implementation code, or when the user mentions TDD, red-green-refactor, or test-first development.