Creates minimal boilerplate structure for new Web Components in Sando Design System following COMPONENT_ARCHITECTURE.md 7-file pattern. Generates only what developer requests - no assumptions, no dead code. Ask first, then scaffold component files, tests, stories based on requirements. <example> User: "Create a new Card component" Assistant: "I'll use the component-creator skill to scaffold the sando-card component with the 7-file pattern." </example> <example> User: "I need a new Accordion component with expand/collapse functionality" Assistant: "I'll use component-creator to scaffold sando-accordion with the specified behavior." </example> <example> User: "Scaffold a new input field component" Assistant: "Using component-creator to generate sando-input with the standard 7-file structure." </example>
Compact guidelines digest for Sando Design System agents. Replaces the full `## 📚 MANDATORY: Read Guidelines Before ANY Work` block that is duplicated across every specialist agent. Provides pre-digested, token- efficient rules organized by agent type. Trigger: inject into sub-agent prompts before task-specific instructions to avoid each agent re-reading full .toon guideline files (saves ~2000-5000 tokens per workflow).
PR creation workflow for Sando Design System. Ensures conventional commits, correct branch naming, CI-passing PRs, and well-structured PR bodies. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Issue creation workflow for Sando Design System. Creates well-structured GitHub issues for bug reports and feature requests following project conventions. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Routing table, classification protocol, and ask protocol for the Sando Orchestrator. Extracted from the orchestrator to reduce its context size. Contains the keyword → agent mapping, multi-agent workflow definitions, skill injection reference, and the SDD architectural gate. Trigger: loaded once per session by the orchestrator before any delegation.
Canonical verification protocol for Sando Design System agents. Provides the exact commands, decision trees, and thresholds each specialist agent must run after completing work. Replaces per-agent `<verification>` blocks that are duplicated with slight variations across agents. Trigger: inject into sub-agent prompts so each agent knows exactly what to run and what "done" means.
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.
Create technical design document with architecture decisions and approach. Trigger: When the orchestrator launches you to write or update the technical design for a change.