When to use
- User types
/dym-diagram-design(no arguments → slug table) or/dym-diagram-design <slug>; or/dymroutes here by domain. - The hub only costs the description line; child workflow bodies are only read when invoked.
Steps
-
Read ARGUMENTS →
<slug>. No slug → print the table below then stop, do not read any file.slug purpose install-and-verifyInstall and prove it runs brand-onboarding-and-profilesOnboard brand and manage client profiles authoring-in-chatDraw diagrams via chat (no CLI for this) import-extractors-shellTwo extractors run in the terminal (draw.io and Mermaid) import-export-slash-commandsSlash command: import and export (typed in chat) selfcheck-and-your-ciSelf-check output and lock it with YOUR CI contributor-gatesContributor branch: check gates and release rules
- Find the child file in order, take the FIRST file that exists then read EXACTLY ONE file:
(1)
../dym-diagram-design-<slug>/SKILL.md(next to the hub — installed vianpx skills add rheinmir/dym); (2).overstack/doyourmagic/diagram-design/skills/dym-diagram-design-<slug>/SKILL.md(bundle in the project); (3).claude/skills/dym-diagram-design-<slug>/SKILL.md. Follow that file's Steps/Rules; do not read other child files; if none of the 3 are found → say so clearly, stop.
Rules
- Each sub-skill is self-contained; the hub does not stuff the whole bundle into context.
workflows.mdnext to the bundle is an index + verification table, not a source of commands.