Loading...
Loading...
Found 318 Skills
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.
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.
Testing principles, strategies, and patterns. Covers the testing pyramid, test design, TDD, test doubles, and common testing antipatterns. Stack-agnostic.
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.
Resolve GitHub issues using isolated worktrees and TDD
pytest-django testing patterns, Factory Boy, fixtures, and TDD workflow. Use when writing tests, creating test factories, or following TDD red-green-refactor cycle.
Comprehensive RSpec testing for Ruby and Rails applications. Covers model specs, request specs, system specs, factories, mocks, and TDD workflow. Automatically triggers on RSpec-related keywords and testing scenarios.
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.
Domain modeling principles: parse-don't-validate, make invalid states unrepresentable, primitive obsession detection, semantic types, and domain veto authority. Activate when designing types, reviewing code for domain integrity, or when domain review is needed in a TDD cycle.
RED-GREEN-REFACTOR cycle with strict phase gates. Write failing test first, implement minimum code to pass, then refactor while keeping tests green. Use when implementing new features, fixing bugs with test-first approach, improving test coverage, or when user mentions TDD. Use for "TDD", "test first", "red green refactor", "write tests", or "implement with tests". Do NOT use for debugging existing failures (use systematic-debugging) or for refactoring without new tests (use systematic-refactoring).
Test-driven development using the RED-GREEN-refactor cycle. Suitable for users who want to build new features or fix bugs with TDD, mention "red-green-refactor", want to use integration testing, or ask about "test-first development".
Use when choosing the best first failing RSpec spec or vertical slice for a Ruby on Rails change. Covers request vs model vs service vs job vs engine spec selection, system spec escalation, smallest safe slice planning, and Rails-first TDD sequencing. Trigger words: where to start testing, what test to write first, RSpec, test-driven development, TDD, first failing test.