test-driven-development

To generate tests that match existing project conventions, this skill performs split semantic searches on your test files to identify local mocking helpers, assertion idioms, and fixture locations before drafting new tests. It requires integrating TeaRAGs-MCP to retrieve battle-tested code chunks for context-aware generation.

Test-driven development with project-aware patterns is an approach that grounds new test generation in existing project conventions. It uses DSL-specific semantic search with chunk-type filtering to isolate test setup and scenario logic from implementation noise, ensuring consistency across the codebase.

Yes, this TDD approach works with Vitest and RSpec test files by analyzing existing setup files to ensure new tests use correct mock helpers and assertion styles. It performs split semantic searches for test setup and assertion idioms to maintain consistency across frameworks.

To write failing tests that follow established mocking patterns, invoke the skill to analyze existing test files for project-specific mocking helpers and naming idioms. It retrieves proven, battle-tested test code chunks via TeaRAGs-MCP to ensure context-aware generation before invoking the primary TDD implementation cycle.

Yes, you need TeaRAGs-MCP to run test-driven development workflows because the skill requires it to retrieve proven, battle-tested test code chunks for context-aware generation. This integration enables the semantic search needed to ground new tests in existing project-specific patterns.

AI-generated testing often ignores local fixture conventions because it lacks local project context, creating tests that bypass established mocking, assertion, and fixture conventions. This skill solves that issue by performing split semantic searches before invoking the primary TDD implementation cycle.