nw-command-design-patterns-classification
How to size and categorize a command, the declarative command template, and the WHAT-vs-HOW logic-placement rule
Install / Use
npx skills add nWave-ai/nWave --skill nw-command-design-patterns-classificationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-command-design-patterns-classification
nw-command-design-patterns-classification scores 81/100 on our quality scale, 3526th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 2.9 KB long, well organised into 14 sections with 1 code example: a solid amount of guidance for an agent.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-command-design-patterns-classification is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-command-design-patterns-classification compared with similar skills
All 4 of these similar skills score higher than nw-command-design-patterns-classification; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-command-design-patterns-classification (this skill)by nWave-ai | 81 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install nw-command-design-patterns-classification?
- Run
npx skills add nWave-ai/nWave --skill nw-command-design-patterns-classification. The install tabs above show the steps for each supported agent. - Which AI agents does nw-command-design-patterns-classification work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-command-design-patterns-classification safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-command-design-patterns-classification still maintained?
- The repository was last updated about 2 months ago, so nw-command-design-patterns-classification is actively maintained.
Skill content
View source on GitHubname: nw-command-design-patterns-classification description: How to size and categorize a command, the declarative command template, and the WHAT-vs-HOW logic-placement rule user-invocable: false disable-model-invocation: true
Command Classification, Sizing, and Declarative Template (KNOWLEDGE)
Kind: KNOWLEDGE (reference). Composed by nw-command-design-patterns core. Fires when: a command must be classified, sized, or restructured against the declarative template (the "what category / what size / what shape" question). No forced sequence.
The Forge Model (Gold Standard)
forge.md at 40 lines is the reference dispatcher. Contains: header (wave, agent, overview) | Agent invocation (name + command + config) | Success criteria (checklist) | Next wave handoff | Expected outputs. Every dispatcher should aspire to this pattern.
Command Categories
| Category | Description | Size Target | Examples | |----------|-------------|-------------|----------| | Simple | Direct action, minimal delegation | 40-80 lines | forge, start, version, git | | Dispatcher | Delegates to one agent with context | 40-150 lines | research, review, execute | | Orchestrator | Coordinates multiple agents/phases | 100-300 lines | develop, document |
Declarative Command Template
Commands declare WHAT, not HOW. The agent knows how to do its job.
# DW-{NAME}: {Title}
**Wave**: {WAVE_NAME}
**Agent**: {persona} ({agent-id})
## Overview
One paragraph: what this command does and when to use it.
## Context Files Required
- {path} - {why needed}
## Agent Invocation
@{agent-id}
Execute \*{command} for {parameters}.
**Context Files:**
- {files the orchestrator reads and passes}
**Configuration:**
- {key}: {value} # {comment}
## Success Criteria
- [ ] {measurable outcome}
- [ ] {quality gate}
## Next Wave
**Handoff To**: {next wave or workflow step}
**Deliverables**: {what this command produces}
# Expected outputs:
# - {file paths}
Size Targets and Evidence
Research (Chroma Research, Anthropic context engineering): focused prompts (~300 tokens) outperform full prompts (~113k tokens) | Claude shows most pronounced performance gap | Information buried mid-prompt gets deprioritized ("Lost in the Middle") | Opus 4.6 is proactive/self-directing; verbose instructions cause overtriggering
Targets: Dispatchers 40-150 lines | Orchestrators 100-300 lines | Current average 437 lines; target under 150
When Commands Should Contain Logic vs Delegate
Contain in command (declarative):
- Which agent to invoke
- What context files to read/pass
- Success criteria and quality gates
- Next wave handoff
Delegate to agent:
- Methodology (TDD phases, review criteria, refactoring levels)
- Domain-specific templates/schemas
- Tool-specific config (cosmic-ray, pytest)
- Quality assessment rubrics
Rule: if content describes HOW the agent does its work, it belongs in agent definition or skill, not command.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
