Verified:GitHub

nw-command-design-patterns

Standardize NW command definitions with YAML frontmatter and canonical templates.

Updated Apr 15, 2026

Search Tags:#anti-patterns #orchestrator #design-patterns #skill-loading #dispatcher #command-definition #canonical-examples

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-command-design-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-command-design-patterns
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-command-design-patterns
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-command-design-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies best practices for command definition files, including size targets, declarative templates, anti-patterns, and canonical examples to guide scalable, reliable command design.

Core Features & Use Cases

Declarative command templates that separate WHAT from HOW
Size targets, evidence-based guidelines, and canonical examples to reduce duplication
Anti-patterns and compression guidelines to improve efficiency and safety
Clear guidance for loading and integrating sub-skills and orchestration patterns

Quick Start

Review this skill to design or audit a new command using the NW pattern and ensure it adheres to the canonical structure and loading requirements.

Frequently Asked Questions about nw-command-design-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are command design patterns for orchestrator and dispatcher workflows?▼

Command design patterns standardize robust command definitions by separating declarative templates into what a command does and how it executes. This reduces duplication and ensures reliable orchestrator and dispatcher workflows across NW skills.

How do I standardize command definitions using YAML frontmatter?▼

Standardize command definitions by enforcing YAML frontmatter with name and description fields, applying declarative templates, and following canonical examples. This ensures consistent command structure and reliable integration across NW skills.

What anti-patterns should I avoid when creating orchestrator commands?▼

Avoid anti-patterns in orchestrator commands by following compression guidelines, size targets, and evidence-based guidelines provided by canonical command templates. These patterns prevent unsafe command definitions and improve execution efficiency.

How do I load sub-skills into a dispatcher command template?▼

Load sub-skills into dispatcher command templates by following structured sub-skill loading rules and orchestration patterns. These rules define how to safely integrate additional skills and manage workflow execution dependencies.

What's the best way to audit command definitions against canonical examples?▼

Audit command definitions by reviewing them against canonical examples and declarative templates that enforce size targets and YAML frontmatter. This verifies the command adheres to NW pattern structure and loading requirements.

Why do my command definitions cause workflow duplication and errors?▼

Command definitions cause workflow duplication and errors when they lack declarative templates, anti-pattern guidance, and size targets. Applying canonical examples and structured sub-skill loading rules resolves these scaling and reliability issues.