nw-tdd-methodology-walking-skeleton
From the author
Building and validating a walking skeleton - the WS protocol scoped to the FEATURE (one skeleton, extended by every slice), Mandate 5 adapter port-class real-I/O treatment (resource table), and Mandate 6 adapter-integration real-I/O requirement
Install
npx skills add nWave-ai/nWave --skill nw-tdd-methodology-walking-skeleton -a claude-code
Installs to .claude/skills/nw-tdd-methodology-walking-skeleton/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 87
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- nw-tdd-methodologynWave-ai/nWaveDeep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policyTesting★ 631
- nw-distill-port-treatment-policynWave-ai/nWavePort-to-port acceptance criteria + the Architecture of Reference (port-class → test treatment) + the Project Infrastructure Policy (concrete mechanism per port) + the walking-skeleton canonical definition and not-applicable exemptions. Consult while classifying a port's test treatment and the concrete mechanism for this codebase.Testing★ 631
- run-protocolTserenTserenov/FMT-exocortex-templateStep-by-step execution of the OWC protocol with mandatory checkpoint at each step. Prevents skipping steps (including verification).Other★ 63
- nw-tdd-methodology-port-to-portnWave-ai/nWaveWhat a test asserts on and where it enters - port-to-port discipline at all test levels, the layer-specific Universe, refactoring-resilience, and the hexagonal per-layer testing strategyTesting★ 631
- nw-test-design-mandatesnWave-ai/nWaveDesign mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths). Lean recomposing core - routes to three narrow mandate modules.Testing★ 631
- integration-e2e-testingshinpr/claude-code-workflowsDefines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.Testing★ 709
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in