TDD Layer Registry — Productivity skill for Claude Code
This file maps architecture layers to their skills and provides project-level configuration for the outside-in-tdd workflow.
How to install TDD Layer Registry
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open JoeGaebel/outside-in-tdd-starter and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What TDD Layer Registry does
This file maps architecture layers to their skills and provides project-level configuration for the outside-in-tdd workflow. Generic agents read this file instead of hardcoding layer definitions.
Alternatives in Productivity
- Reviews Plans — Review all active architecture plans relevant to the current task 15.6k ★
- C-level Advisor — Executive advisory skills for C-level decisions 5.3k ★
- 🤝 Contributing To Agent Skills — First of all, thank you for taking the time to contribute 1.7k ★
README
TDD Layer Registry
This file maps architecture layers to their skills and provides project-level configuration for the outside-in-tdd workflow. Generic agents read this file instead of hardcoding layer definitions.
Layers
| Layer | Testing Skill | Implementation Skill | Description |
|---|---|---|---|
| e2e | cypress-end-to-end-testing | — | Cross-layer E2E verification of business processes |
| frontend | jest-frontend-testing | frontend-implementation | React components, hooks, pages |
| backend | jest-backend-testing | backend-implementation | API route handlers, lib utilities |
Layer Dependencies
None.
E2E Test Directories
| Classification | Path |
|---|---|
| Business process | cypress/e2e/business-process/ |
| Infrastructure | cypress/e2e/infrastructure/ |
E2E Failure → Layer Routing
When the E2E test fails, use these indicators to determine which inner layer to target:
| E2E Failure Type | Target Layer |
|---|---|
| UI element missing/wrong | frontend |
| UI interaction not working | frontend |
| Page doesn't exist (Next.js 404) | frontend |
| Data not displaying correctly | frontend (if rendering) or backend (if API) |
| API returns wrong data | backend |
| API route doesn't exist (404/405) | backend |
| Business logic incorrect | backend |
| Database state wrong | backend |
Commands
| Purpose | Command |
|---|---|
| Specific test | npm run test:unit:spec |
| Full verification | ./t |
| Lint | npm run lint |
| Typecheck | npm run typecheck |
| Mutation testing | npm run test:mutate:uncommitted |
Mutation Testing
- Threshold: 60%
- Surviving mutants report:
reports/mutation/surviving-mutants.txt
Design Constraint Checks
When the TDD planner validates a design approach against the runtime environment, check for these conflicts:
| Check | Conflict |
|---|---|
| Browser-only APIs during render? | Next.js SSR hydration mismatch |
| State initializes differently server vs client? | React hydration mismatch |
| Borrowing pattern from e |
Related Skills
Plan Workflow
Generate a skill chain plan for a high-level goal by analyzing the skills registry for input/output compatibil
Axiom Planning
TDD-validated implementation planning with a four-reviewer plan-review quality gate - atomic-task plans with e
Logs
Read production logs from Loki (via Grafana) — by service, level, request/trace id, time window
Create Sprint
Create a new sprint with complete task definitions and directory structure
Plan Build Improve
Generic plan-build-improve workflow for any expert domain
Clojurescript Skills
ClojureScript skills: JavaScript interop, externs inference, macro stage separation, host-typed exceptions, JS
Related Agents
Architecture Mapper
Maps all files and architectural layers that will be affected by a proposed change. Use when exploring the cod
Genesis Codebase Mapper
Maps project structure, identifies patterns and conventions, traces architecture layers, and documents depende
Task Explorer
Deeply analyzes existing code, configuration, or systems relevant to a task by tracing execution paths, mappin
