Loading...
Loading...
Found 321 Skills
Use when checking code quality, running security audits, testing coverage, finding violations, or setting up quality tools - supports Drupal (PHPStan, PHPMD, PHPCPD, Psalm, Semgrep, Trivy, Gitleaks via DDEV) and Next.js (ESLint, Jest, jscpd, madge, Semgrep, Trivy, Gitleaks) projects with TDD, SOLID, DRY, and OWASP security checks
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context.
Use red-green-refactor to implement features and bug fixes with tests first. Only use if requested explicitely, for general tdd use mattpocock/skills/tdd
iOS Test-Driven Development standards. Enforces Red-Green-Refactor cycle, test pyramid (70/20/10), layer-specific testing strategies with XCTest and Swift Testing, and CI integration. Use when building or reviewing iOS apps with TDD methodology.
Disciplined spec-driven test-driven development workflow for building software with AI coding agents. Transforms ambiguous requests into verified implementations through structured specification, test derivation, and strict TDD. Handles greenfield projects, brownfield enhancements (with or without existing tests), refactors, and complex bug fixes with workflow-specific guidance for each. Use when the user requests a new feature, module, enhancement, refactor, API, data pipeline, CLI tool, or system with multiple requirements, edge cases, or unclear specifications. Also use for complex bug fixes requiring root cause analysis. Triggers on phrases like "add a feature", "implement", "build a new module", "build an API", "build a CLI", "build a data pipeline", "refactor", "fix this bug", "write tests for", "TDD", "test-first", "the requirements are unclear", "characterization tests", or "spec this out". Triggers when modifying code with adjacent test files (`tests/`, `*_test.py`, `*.test.ts`, `*.spec.ts`, `spec/`, `__tests__/`) or test framework config (pytest.ini, jest.config.*, go.mod with testing imports, Cargo.toml with [dev-dependencies], package.json with a test script). Triggers when the user mentions edge cases, invariants, acceptance criteria, EARS notation, or red-green-refactor. Do NOT use for simple one-line fixes, cosmetic changes, formatting, renames, dependency bumps, or tasks where requirements are already fully specified with tests provided.
Educational guide on best practices for creating implementation plans that prevent drift. Covers style anchors, task sizing, TDD requirements, affirmative instructions, drift handling, and quality gates. Use when creating or improving implementation plans to ensure they follow proven patterns.
Ralph Wiggum loops - self-referential TDD iteration until tests pass
Start implementation from Intent. Validates Intent completeness, then either delegates to TaskSwarm (if available) or executes TDD phases directly. Use when you have an Intent ready and want to start building.
Execute tasks from a track's implementation plan following TDD workflow
Goose-native software delivery command suite for product validation, scope challenge, planning, TDD implementation, debugging, review, QA, and release handoff
Evaluates test quality using Dave Farley's 8 properties. Use when reviewing tests, assessing test suite quality, or analyzing test effectiveness against TDD best practices.