Specx Tests
maksimzayats/specx
Add or refine tests for specx Python services. An agent skill from maksimzayats/specx.
5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples
Install Nw Hexagonal Testing
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nWave-ai/nWave nw-hexagonal-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .claude/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .claude/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .claude/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nWave-ai/nWave nw-hexagonal-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .agents/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .agents/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .agents/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nWave-ai/nWave nw-hexagonal-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .cursor/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .cursor/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nWave-ai/nWave.git --path nWave/skills/nw-hexagonal-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nWave-ai/nWave nw-hexagonal-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .gemini/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .gemini/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nWave-ai/nWave nw-hexagonal-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .github/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .github/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .github/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nWave-ai/nWave nw-hexagonal-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/nWave/skills/nw-hexagonal-testing .opencode/skills/nw-hexagonal-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nw-hexagonal-testing" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-hexagonal-testing into .opencode/skills/nw-hexagonal-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-hexagonal-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nw-hexagonal-testing- GitHub stars
- 617
- Token cost
- ~1.4k tokens
- SKILL.md length
- 508 words
- Files
- 1
- Skills in repo
- 106
- Repo updated
- First seen
- Licence
- MIT
At a glance
5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples
- Tasks that involve LLM guardrails
- SKILL.md covers 5-Layer Output Validation…, Input/Output Contract, Vertical Slice Development and Testing Boundaries per…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Unit testing
What it does
Nw Hexagonal Testing is an agent skill from nWave-ai/nWave. 5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering LLM guardrails and Unit testing. The repository describes itself as: AI agents that guide you from idea to working code, with you in control at every step. The licence is MIT.
When your agent uses it
- Tasks that involve LLM guardrails
- Tasks that involve Unit testing
Example prompts
- “/nw-hexagonal-testing”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit da401a8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nw Hexagonal Testing loads about 1.4k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 508 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nWave-ai/nWave at commit da401a8, republished under its MIT licence (© nWave-ai). 508 words, ~1,372 tokens.
Download SKILL.mdSave it as
.claude/skills/nw-hexagonal-testing/SKILL.md (or your agent's skills folder).- name
- nw-hexagonal-testing
- description
- 5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples
- user-invocable
- false
- disable-model-invocation
- true
Hexagonal Testing and Output Validation
5-Layer Output Validation Framework
Validates agent OUTPUTS, not TDD testing methodology.
Layer 1: Unit Testing (Output Validation)
Validate individual software-crafter outputs.
structural_checks:
- required_elements_present: true
- format_compliance: true
- quality_standards_met: true
quality_checks:
- completeness: "All required components present"
- clarity: "Unambiguous and understandable"
- testability: "Can be validated"
test_data_quality:
real_data: "Use real API responses as golden masters"
edge_cases: "Test null, empty, malformed, boundary conditions"
assertions: "Assert expected counts, not just 'any results'"Layer 2: Integration Testing (Handoff Validation)
Validate handoffs to next agent. Next agent must consume outputs without clarification.
- Deliverables complete: all expected artifacts present
- Validation status clear: quality gates passed/failed explicit
- Context sufficient: next agent can proceed without re-elicitation
Layer 3: Adversarial Output Validation
Challenge output quality through adversarial scrutiny of generated code:
- SQL injection vulnerabilities? | XSS vulnerabilities? | Null/undefined/empty input handling?
- Integer overflow/underflow? | Graceful failure vs crash? | Exception handling appropriateness?
Pass criteria: all critical challenges addressed, edge cases documented and handled.
For peer review and escalation protocols, load the review-dimensions skill.
Input/Output Contract
Inputs
- Required: user_request (non-empty command string) | context_files (existing readable file paths)
- Optional: configuration (YAML/JSON) | previous_artifacts (outputs from prior wave for handoff)
Outputs
- Primary: code artifacts (src/**/*, strictly necessary only) | documentation (docs/develop/, minimal essential)
- Secondary: validation_results (gate pass/fail status) | handoff_package (deliverables, next_agent, validation_status)
- Policy: any document beyond code/test files requires explicit user approval before creation
Side Effects
- Allowed: file creation (src/, tests/ only) | file modification with audit trail | log entries
- Forbidden: unsolicited documentation | deletion without approval | external API calls | credential access
- Requires permission: documentation beyond code/test files | summary reports | analysis documents
Error Handling
- Invalid input: validate first, clear error, do not proceed with partial inputs
- Processing error: log context, return to safe state, actionable user message
- Validation failure: report failed gates, withhold artifacts, suggest remediation
Vertical Slice Development
Complete business capability per slice: UI -> Application -> Domain -> Infrastructure for a specific feature. Slices developed and deployed independently. Focus on business capability over technical layer.
For test doubles policy and violation examples, load the tdd-methodology skill.
Show full SKILL.md (226 more words)Show less
Testing Boundaries per Architectural Layer
| Layer | Test Strategy | Adapter Selection | Rationale |
|---|---|---|---|
| Domain | Pure unit test, zero I/O | N/A (no adapters) | Domain is pure functions — test with pure inputs |
| Application | InMemory ports for focused scenarios | InMemory doubles | Application orchestrates — test logic, not I/O |
| Adapter | REAL I/O ALWAYS* | Real system (tmp_path, subprocess, DB) | Adapter IS the I/O boundary — testing with InMemory defeats the purpose |
*Exception: costly subprocesses (claude -p, LLM) and paid external APIs use contract smoke tests tagged @requires_external instead of real I/O. See nw-tdd-methodology Mandate 6 for the full adapter type → test type table.
| WS/E2E | Per declared strategy (A/B/C/D) | Real for local, fake for costly | WS proves wiring — InMemory proves nothing about wiring |
Key Insight
A pure function stub at a driven port boundary models the port's CONTRACT, not the external system's BEHAVIOR. For every driven port stub, verify that an adapter integration test with real I/O covers the behavioral gap.
Integration Surface Ratio Heuristic
If the system's primary job is coordinating external processes (orchestrators, ETL, deployment scripts), invest MORE in WS and adapter integration tests than unit tests. If the system's primary job is domain computation (pricing, validation, parsing), the traditional pyramid applies.
Strategy D Fixture Template
# conftest.py
import os
import pytest
@pytest.fixture
def subprocess_runner():
"""Returns real or fake subprocess runner based on E2E mode."""
if os.getenv("NWAVE_E2E_REAL_SUBPROCESS") == "1":
from myapp.adapters.real_subprocess_runner import RealSubprocessRunner
return RealSubprocessRunner()
from tests.doubles.fake_subprocess_runner import FakeSubprocessRunner
return FakeSubprocessRunner(exit_code=0, stdout="OK")Naming convention for multi-port Strategy D: NWAVE_E2E_REAL_{PORT_NAME} per driven port (e.g., NWAVE_E2E_REAL_SUBPROCESS, NWAVE_E2E_REAL_DATABASE). Use NWAVE_E2E_MODE=real as composite flag to enable ALL real adapters at once for full E2E.
© nWave-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in nWave/skills/nw-hexagonal-testing of nWave-ai/nWave.
Open the folder on GitHubat commit da401a8
Compare with similar skills
Nw Hexagonal Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nw Hexagonal Testing this skillnWave-ai/nWave | 617 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Specx Testsmaksimzayats/specx | 202 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Specx Project Toolingmaksimzayats/specx | 202 | — | ~965 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| Testing OpenLogi UIAprilNEA/OpenLogi | 23k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Go Testingcxuu/golang-skills | 170 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Specx Project Tooling
maksimzayats/specx
Add strict Python project tooling for a specx service. An agent skill from maksimzayats/specx.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
More from nWave-ai/nWave
All 106 skills in this repoNw Deliver Orchestration
nWave-ai/nWave
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization.
Nw Diagram
nWave-ai/nWave
Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML.
Nw Diverge
nWave-ai/nWave
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence.
Nw Document
nWave-ai/nWave
Creates evidence-based documentation following DIVIO/Diataxis principles.
Nw Execute
nWave-ai/nWave
A skill your agent uses when a DELIVER roadmap already exists and you need to dispatch exactly one identified step through its TDD cycle.
Nw Refactor
nWave-ai/nWave
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring.
Related
Categories
Questions about Nw Hexagonal Testing
What does Nw Hexagonal Testing do?
5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples. Nw Hexagonal Testing is an agent skill from nWave-ai/nWave.
When should I use Nw Hexagonal Testing?
Nw Hexagonal Testing fits situations like: tasks that involve LLM guardrails; tasks that involve Unit testing.
How do I install Nw Hexagonal Testing in Claude Code?
Run `npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a claude-code`. Or copy the skill folder (nWave/skills/nw-hexagonal-testing in nWave-ai/nWave) into .claude/skills/nw-hexagonal-testing in your project. Claude Code loads it when a task matches its description.
How do I install Nw Hexagonal Testing in Codex?
Run `npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a codex`. Or copy the skill folder (nWave/skills/nw-hexagonal-testing in nWave-ai/nWave) into .agents/skills/nw-hexagonal-testing in your project. Codex loads it when a task matches its description.
Can I use Nw Hexagonal Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nWave-ai/nWave --skill nw-hexagonal-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nw-hexagonal-testing, .gemini/skills/nw-hexagonal-testing, .github/skills/nw-hexagonal-testing and .opencode/skills/nw-hexagonal-testing in your project.
What does Nw Hexagonal Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Nw Hexagonal Testing is instructions for the agent only. Our summary lists: Python 3.
Does Nw Hexagonal Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Nw Hexagonal Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nw Hexagonal Testing use?
Nw Hexagonal Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nw Hexagonal Testing use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Nw Hexagonal Testing?
Skills that share tags, products or a category with Nw Hexagonal Testing: Specx Tests (maksimzayats/specx, 202 stars), Specx Project Tooling (maksimzayats/specx, 202 stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars) and Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nw Hexagonal Testing?
nWave-ai (a GitHub organization) maintains it in nWave-ai/nWave, which has 617 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on September 16, 2026.
Source: nWave-ai/nWave on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.