Implement features using TDD and specific Yuzu validation protocols.
Install
mkdir -p .claude/skills/tdd-tr3kkr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13469" && unzip -o skill.zip -d .claude/skills/tdd-tr3kkr && rm skill.zipInstalls to .claude/skills/tdd-tr3kkr
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Apply Yuzu-specific test-driven development using tracer-bullet red-green-refactor cycles and the repo's Meson, gateway, proto, and ABI validation rules. Use when the user says `/tdd`, asks for TDD, red-green-refactor, or wants a feature/fix built test-first in Yuzu.Key capabilities
- →Add a single failing test for one observable behavior
- →Implement minimal code to pass the failing test
- →Verify test execution using `meson test` or gateway commands
- →Repeat the red-green cycle for subsequent behaviors
- →Refactor code only when all tests are green
- →Use Yuzu-specific test hygiene practices for temporary files and isolation
How it works
The skill guides through a test-driven development cycle, focusing on public interfaces and Yuzu-specific build and validation tools.
Inputs & outputs
When to use tdd
- →Implementing new features
- →Fixing bugs via TDD
- →Running Yuzu integration tests
About this skill
TDD
Use behavior-first tests through public interfaces. Prefer integration-style seams that exercise real stores, REST handlers, gateway paths, plugin boundaries, or command dispatch contracts. Avoid tests coupled to private implementation.
Before Red
- Read
CONTEXT.mdand relevant ADRs indocs/adr/. - Identify the public interface and the project term for the behavior.
- List the smallest vertical behavior slice that proves value.
- Choose the narrowest validation path through
$yuzu-build. - Invoke
$yuzu-proto,$yuzu-plugin-abi,$yuzu-meson, or$yuzu-windows-msvcif the slice crosses those boundaries.
Cycle
- Red: add one failing test for one observable behavior.
- Green: implement only enough code to pass that test.
- Verify: run the targeted suite with
meson test -C <builddir> --suite <suite> --print-errorlogsor the relevant gateway command. - Repeat for the next behavior.
- Refactor only while green.
Do not write all tests first. Use tracer bullets: one behavior, one test, one implementation.
Yuzu Test Hygiene
- Use
yuzu::test::unique_temp_path(prefix)orTempDbFilefor C++ test temp files and SQLite DBs. - Avoid hardcoded shared paths and clock/thread-hash uniqueness.
- For gateway EUnit, pass
--dir apps/yuzu_gw/test. - For direct Erlang isolation, remove the relevant
_build/testtree or run in a fresh BEAM. - For proto changes, include
buf lint protoandbuf breaking proto --against '.git#subdir=proto,ref=origin/main'when available. - For plugin ABI changes, add descriptor/loader coverage and preserve stable C ABI compatibility.
Done
Finish with the tests added, implementation green, targeted validation output summarized, and any broader /test --quick or governance follow-up called out.
When not to use it
- →The user wants to write all tests before any implementation
- →The project is not Yuzu-specific or does not use Meson, gateway, proto, or ABI validation rules
Limitations
- →It is specific to Yuzu projects
- →It requires familiarity with Meson, gateway, proto, and ABI validation rules
- →It emphasizes integration-style seams over unit tests
How it compares
This workflow enforces a strict red-green-refactor cycle with Yuzu-specific tools and hygiene, ensuring behavior-first development and integration seam testing.
Compared to similar skills
tdd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tdd (this skill) | 0 | 2mo | No flags | Advanced |
| code-coverage-with-gcov | 15 | 4mo | Review | Intermediate |
| unity-mcp-orchestrator | 17 | 4mo | No flags | Intermediate |
| add-uint-support | 18 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Tr3kkR
View all by Tr3kkR →You might also like
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects
unity-mcp-orchestrator
CoplayDev
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
add-uint-support
pytorch
Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.
3d-games
davila7
3D game development principles. Rendering, shaders, physics, cameras.
cpp-pro
sickn33
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.