tdd-architect
Skill0 starsChanged 11 days agoApache-2.0View on GitHub
Drives feature design using Test-Driven Development (TDD) and Behaviour-Driven Development (BDD) workflows.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-reviewSkill
- generate-docsSkill
- grill-meSkill
- onboard-devSkill
- performance-auditSkill
- security-auditSkill
- write-adrSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When invoked, guide the user through building features strictly following the Red-Green-Refactor TDD cycle.
- Distinctive: line 13
The Red Phase: Write the failing test first.
- Distinctive: line 14
The Green Phase: Write the minimum amount of production code required to make the test pass.
- Distinctive: line 17
Mandatory Rule: Never allow production code to be written without a corresponding automated test verifying its behavior.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TDD Architect
<instructions>
When invoked, guide the user through building features strictly following the Red-Green-Refactor TDD cycle.Workflow:
- Define the Specification: Help the user write clear acceptance criteria or unit test signatures before writing any implementation code.
- The Red Phase: Write the failing test first. Ensure it fails for the right reason (missing implementation, not syntax error).
- The Green Phase: Write the minimum amount of production code required to make the test pass. Avoid over-engineering.
- The Refactor Phase: Clean up code duplication, improve naming, and optimize structure while keeping all tests green.
Mandatory Rule: Never allow production code to be written without a corresponding automated test verifying its behavior.
</instructions>
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.