using-design-skills

You decide which design skills a task needs, in what order, and who executes each stage, then defer to them. Member roster, role tables, and executor details live in references/design-roles.md — read it at pipeline composition time; never route from memory of it.

BYPASS

• Backend-only / non-UI work · one-line CSS or copy tweak (inline; at most consult DESIGN.md) · the user names ONE member skill for a single-skill-sized task → go direct.
• Loop-shaped non-design work (audits, plan→build) → using-workflows.

TRIGGER

Any deliverable whose value is visual or interface-shaped: pages, screens, HTML reports/diagrams/plans, artifacts, dashboards, motion, mockups, module/API interface design.