nWave-ai/nWave-experimental

nw-auto

Thin prompt-level router for explicitly authorized Auto M/L work: reuse the acceptance-designer, paradigm crafter, independent examiner, and Git evidence without creating another controller.

nw-cross-cutting-invariants

Cross-cutting normative invariants — lean public routing core for global gate/construction doctrine and on-demand knowledge lenses. Cite clause ids; never re-declare.

nw-design

Establishes durable architecture, reuse, boundaries, cross-layer algebra, residual stress behavior, paradigm, and prefactoring decisions for later DeliveryContract compilation.

nw-discuss

Clarifies jobs, journeys, outcomes, and human-visible value in the durable product SSOT without creating a delivery workspace or executable contract.

nw-distill

Compile value and architecture authority into a minimal executable oracle and one DeliveryContract. Human and Auto share the same route algebra and quality floor.

nw-fp-erlang-elixir

Erlang/Elixir language-specific patterns, OTP as the effect model, and runtime-enforced immutability

nw-fp-fsharp

F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions

nw-fp-haskell

Haskell language-specific patterns, GADTs, type classes, and effect systems

nw-fp-kotlin

Kotlin language-specific patterns with Arrow, Raise DSL, and coroutine-based effects

nw-fp-rust

Rust language-specific patterns, compiler-verified exhaustive ADTs, and Result/Option as railway-oriented programming

nw-fp-scala

Scala 3 language-specific patterns with ZIO, Cats Effect, and opaque types

nw-fp-typescript

TypeScript language-specific patterns with fp-ts/Effect, discriminated unions, and railway-oriented error handling

nw-post-mortem-framework

Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning

nw-ab-migrate-monolith

PROCEDURE — migrate one legacy monolithic agent to a lean core plus routed skills. Trigger: an existing agent has measured size, embedded-configuration, duplication, aggressive-language, or multi-responsibility debt. Composes agent validation and requested…

nw-ab-optimize-skill

PROCEDURE — optimize one requested existing skill. Measures multi-trigger, duplication, and resident-context debt before editing; preserves its name as the lean core and behavioral projections.

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-buddy-wave-knowledge

Current wave authority and handoff map for answering where product, design, delivery, and feedback facts belong.

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-analysis-port

KNOWLEDGE — resolve code facts (who-calls-X / where-defined-or-read / call-graph / change-scope / file-atoms) through the vendor-neutral CLI `des code-fact`, degrading LOUD through bundled adapters (AST, TextSearch). Trigger: any time an agent designs,…

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-crafter-discipline-delivery-contract

Crafter discipline for implementing one immutable DeliveryContract with minimal production change, reuse, boundary integrity, and terminal evidence.

nw-cross-cutting-context-residency

KNOWLEDGE — use when choosing resident, map-only, or on-demand context.

nw-cross-cutting-evidence-instrumentation

KNOWLEDGE — use when evaluating a claim, check, measurement, or shared-log count.

nw-cross-cutting-input-data-contracts

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

nw-deliver

Use for DELIVER wave orchestration from one validated DeliveryContract to one examined candidate and one whole-delivery finalization.

nw-finalize

Finalize one whole delivery by joining terminal evidence and returning one verified final commit F.

nw-forge

Backward-compatible router for creating agents, validating existing agents, migrating existing agent monoliths, or optimizing one existing skill.

nw-fp-algebra-driven-design

Algebra-driven API design with monoids, semigroups, and interpreters via algebraic equations

nw-mode-select

Choose human-on-the-loop vs auto mode for a piece of work, classify it S/M/L, and pick the matching path before starting. Load at the START of any nWave-adjacent task, before dispatch, when the mode/size has not already been declared by the user in this…

nw-new

Routes a new request to the earliest authority that lacks evidence, without creating a feature workspace.

nw-property-based-testing

Property-based testing strategies (PBT — ACTIVE, authored by the acceptance-designer during DISTILL), shrinking, PBT+TDD integration.

nw-review

Dispatches an independent reviewer for a durable authority, immutable oracle, candidate diff, charter set, or operational artifact.

nw-solution-architect-auto-consult

PROCEDURE — close bounded architecture consult in durable authority. Trigger: exact AUTO-ARCHITECTURE-CONSULT envelope.

nw-solution-architect-formal-verification

PROCEDURE — verify one separately selected formal DESIGN obligation and state its runtime refinement boundary.

nw-solution-architect-full-design

PROCEDURE — author or amend one durable application DESIGN authority. Trigger: a non-Auto DESIGN mandate.

nw-throughput

Evidence-led orchestration for maximizing delivery throughput with causal fan-out, associative boundary composition, one heavy local box, and concise terminal evidence.

nw-formal-verification-tlaplus

TLA+ and PlusCal for specifying distributed system invariants. Decision heuristics for when formal verification adds value, key patterns, state explosion management, and alternatives comparison.

nw-stress-analysis

Advanced architecture stress analysis methodology for designing systems that survive unknown stresses. Load on its semantic trigger — external/nondeterministic dependency, recovery/retry/compensation/degradation, contagion, infrastructure/substrate…

nw-ab-anti-patterns

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

nw-ab-critique-dimensions

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