/nw-command-design-patterns-authoring
The v2.8+ new-command installation contract - which three files to produce and their frontmatter when creating a brand-new command
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-command-design-patterns-authoring -a windsurf -y
SKILL.md
nw-command-design-patterns-authoring.SKILL.mdname: nw-command-design-patterns-authoring
description: The v2.8+ new-command installation contract - which three files to produce and their frontmatter when creating a brand-new command
user-invocable: false
disable-model-invocation: true
New-Command Authoring & Installation Format (KNOWLEDGE)
**Kind**: KNOWLEDGE (reference). Composed by `nw-command-design-patterns` core. Fires when: a brand-NEW command is being created and the question is "which files do I produce, in what format, where" (the v2.8+ install contract). Distinct from classification (sizing an existing command) and reduction (trimming a bloated one). No forced sequence.
Command Installation Format (v2.8+)
Since v2.8.0, commands are installed as **skills**, not as separate command files. The installer reads from `nWave/skills/nw-{command-name}/SKILL.md`, NOT from `nWave/tasks/nw/{command-name}.md`. The legacy `tasks/nw/*.md` path is still supported but is NOT auto-installed.
**When creating a new command, produce THREE files:**
1. **`nWave/skills/nw-{name}/SKILL.md`** — the installable command skill. Frontmatter MUST include:
---
name: nw-{name}
description: "One-line description for slash command menu"
user-invocable: true
argument-hint: "[args] - Example: \"example usage\""
---Body: the full command definition (same content as the declarative template).
2. **`nWave/tasks/nw/{name}.md`** — legacy task file (kept for backward compat + reference). Same content, simpler frontmatter (just `description` + `argument-hint`).
3. **`nWave/skills/nw-{name}-methodology/SKILL.md`** (optional) — deep methodology knowledge for the agent. Frontmatter:
---
name: nw-{name}-methodology
description: "Methodology knowledge for {name}"
user-invocable: false
disable-model-invocation: true
---**The skill file (`nWave/skills/nw-{name}/SKILL.md`) is the PRIMARY deliverable.** Without it, the command won't appear in the `/nw-` menu after installation. The task file is secondary.
Also update `nWave/framework-catalog.yaml` with the command entry under the appropriate wave section.
Read more
name: nw-command-design-patterns-authoring description: The v2.8+ new-command installation contract - which three files to produce and their frontmatter when creating a brand-new command user-invocable: false disable-model-invocation: true
New-Command Authoring & Installation Format (KNOWLEDGE)
**Kind**: KNOWLEDGE (reference). Composed by `nw-command-design-patterns` core. Fires when: a brand-NEW command is being created and the question is "which files do I produce, in what format, where" (the v2.8+ install contract). Distinct from classification (sizing an existing command) and reduction (trimming a bloated one). No forced sequence.
Command Installation Format (v2.8+)
Since v2.8.0, commands are installed as **skills**, not as separate command files. The installer reads from `nWave/skills/nw-{command-name}/SKILL.md`, NOT from `nWave/tasks/nw/{command-name}.md`. The legacy `tasks/nw/*.md` path is still supported but is NOT auto-installed.
**When creating a new command, produce THREE files:**
1. **`nWave/skills/nw-{name}/SKILL.md`** — the installable command skill. Frontmatter MUST include:
---
name: nw-{name}
description: "One-line description for slash command menu"
user-invocable: true
argument-hint: "[args] - Example: \"example usage\""
---Body: the full command definition (same content as the declarative template).
2. **`nWave/tasks/nw/{name}.md`** — legacy task file (kept for backward compat + reference). Same content, simpler frontmatter (just `description` + `argument-hint`).
3. **`nWave/skills/nw-{name}-methodology/SKILL.md`** (optional) — deep methodology knowledge for the agent. Frontmatter:
---
name: nw-{name}-methodology
description: "Methodology knowledge for {name}"
user-invocable: false
disable-model-invocation: true
---**The skill file (`nWave/skills/nw-{name}/SKILL.md`) is the PRIMARY deliverable.** Without it, the command won't appear in the `/nw-` menu after installation. The task file is secondary.
Also update `nWave/framework-catalog.yaml` with the command entry under the appropriate wave section.
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-command-design-patterns-authoring.
- Which coding agents can use nw-command-design-patterns-authoring?
- nw-command-design-patterns-authoring installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

