nw-distill-port-treatment-policy
From the author
Port-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.
Install
npx skills add nWave-ai/nWave --skill nw-distill-port-treatment-policy -a claude-code
Installs to .claude/skills/nw-distill-port-treatment-policy/ · 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-methodology-walking-skeletonnWave-ai/nWaveBuilding 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 requirementTesting★ 631
- 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-organization-conventionsnWave-ai/nWaveTest directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.Testing★ 631
- 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
- code-standardstamdogood/builder-essential-skillsApply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).Engineering★ 227
- nw-test-design-mandates-layered-mechanicsnWave-ai/nWaveLayered acceptance-test mechanics: public state preservation, native generative laws, real-boundary journeys and explicit failure observations.Testing★ 631
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in