nWave-ai/nWave-experimental

nw-design

Establishes durable architecture, reuse, boundaries, cross-layer algebra, residual stress behavior, paradigm, and prefactoring decisions for deterministic minimal handover construction.

nw-algebraic-design-protocol

The METHOD for finding a design — name observations and equality before constructors, then follow any contradiction to the type or observation that causes it. Use when a design decision is contested, a law has exceptions, a census or model keeps producing…

nw-cross-cutting-input-data-contracts

KNOWLEDGE — use when adding data, declaring inputs, or choosing a join key.

nw-solution-architect-formal-verification

PROCEDURE — formally verify every design's algebraic claims with need-selected checkers and explicit host-relayed installation or human waiver.

nw-ab-agent-template

KNOWLEDGE — the canonical agent-spec template (frontmatter + body skeleton). Reference loaded by the create/migrate procedures; no sequence.

nw-ab-anti-patterns

KNOWLEDGE — agent/skill/command anti-pattern catalog with fixes. Reference scanned by validate-spec; no sequence.

nw-ab-create-agent

PROCEDURE — create a NEW agent via the 5-phase workflow (ANALYZE→DESIGN→CREATE→VALIDATE→REFINE). Trigger: build a new AI agent. Composes nw-ab-validate-spec.

nw-ab-critique-dimensions

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

nw-ab-house-style

KNOWLEDGE — caveman-native authoring house style + by-construction guarantees (Reasoning Mandate injection, measured-gain compression). Reference for create/migrate; no sequence.

nw-ab-merge-agents

PROCEDURE — merge agent B into agent A, relocating skills and cleaning up all references. Trigger: two agents must become one. Composes nw-ab-validate-spec.

nw-ab-optimize-command

PROCEDURE — optimize a bloated command file to a lean declarative definition (forge.md pattern). Trigger: a command file over its size target with reducible content.

nw-ab-validate-spec

PROCEDURE — validate an EXISTING agent spec against the nw-ab-validation-checklist. Trigger: checking a spec for compliance (also the shared composition target create/migrate/merge invoke). One job: run the checklist, report pass/fail.

nw-ab-validation-checklist

KNOWLEDGE (data) — the agent-spec validation checklist. The item definitions the validate-spec procedure RUNS against. No sequence of its own.

nw-abr-critique-dimensions

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

nw-ad-critique-dimensions

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking…

nw-agent-creation-workflow

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

nw-agent-testing

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

nw-at-completeness-check

Verify that one minimal oracle falsifies every declared delivery obligation without checklist ceremony or duplicate tests.

nw-auto

Evaluates and revises Request S/M/L and delivery choices from evidence, then uses DES steps to deliver it.

nw-bdd-methodology

BDD patterns for acceptance test design - Given-When-Then as a language-neutral specification style, scenario writing rules, realization in the project's incumbent native scenario syntax (Python pytest-bdd binding labelled), anti-patterns, and living…

nw-buddy-command-catalog

Current public nWave delivery commands.

nw-buddy-ssot-knowledge

Single Source of Truth detection — where truth lives in an nWave repo and how to avoid contradicting it.

nw-bugfix

Routes an observed defect request into the DES steps that deliver the fix.

nw-certainty-by-construction

Turn a stable layer claim (domain, application, adapter, or infrastructure) into a construction boundary so the invalid state cannot be built, and state honestly what remains unguarded. Use when a requirement says an invalid state or transition must not…

nw-code-craftsmanship

Universal OO/FP craftsmanship foundation — domain-language naming, small cohesive units, semantic DRY/SSOT, reuse-before-new, one owner per rule/config/fact, prefactoring before new behavior, ports/adapters for testability. Consult before writing or reviewing…

nw-code-design-fp

FP code-design SSOT — the WHAT-to-design catalog (algebra-driven design, domain modelling with types, railway/error-track isolation) shared by the solution architect (design-time) and the functional crafter (execution-time).

nw-code-design-oo

OO code-design SSOT — the WHAT-to-design anti-smell catalog (Object Calisthenics, RPP smell taxonomy, effect isolation) shared by the solution architect (design-time) and the crafter (execution-time).

nw-command-design-patterns

Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence

nw-command-optimization-workflow

Step-by-step workflow for converting bloated command files to lean declarative definitions

nw-cross-cutting-invariants

Cross-cutting normative invariants — routing core for the software/model boundary doctrine, gate/construction principles and on-demand knowledge lenses. Cite clause ids; never re-declare.

nw-ddd-architect

DDD architect design-time mandates — the Fixture-Fanout Enumeration Mandate for shared-substrate per-caller migration (enumerate production callers plus fixture sites plus atomic bundle scope, mechanically enforced) that both the ddd-architect and its…

nw-deliver

Routes one strict Request into the DES steps that deliver it.

nw-devops

Establishes durable deployment, environment, observability, recovery, and CI constraints when platform risk requires the DEVOPS lens.

nw-discover

Tests whether a product problem and opportunity are real, then updates the durable product evidence authorities without creating delivery state.

nw-discovery-workflow

4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking

nw-discuss

PO-led product conversation, visible feedback increments and a DES-constructed human-readable brief.

nw-distill-port-treatment-policy

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…

nw-distill-red-scaffolding

Prepare declared native oracle/supports and establish failure for the promised business reason without production stubs, invented reports or runner substitution.

nw-distill

Produce an executable public oracle from durable authority.

nw-diverge

Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.