workflow-designlisted

Run the full design pipeline for a brand or one-off artifact — design-plan (strategy) → design-system (tokens + showcase) → an artifact skill (linkedin / blog-hero / etc.) → screenshot-html (PNG export). Use when the user says "design a brand", "I need the full design system + assets", "set up a new brand from scratch", "design pipeline for X", or when starting visual work on a brand that has no DESIGN.md yet. Do NOT use when the brand already exists and you just need one artifact — call the artifact skill directly.
slogsdon/skills-workflows · ★ 0 · AI & Automation · score 70

Install: claude install-skill slogsdon/skills-workflows

# Skill: /workflow-design Orchestrates the four-stage design pipeline. Replaces the "which design skill comes first" question with a single invocation. ## When to use - Brand has no `./design/<slug>/DESIGN.md` yet AND user wants one or more artifacts. - User explicitly asks for "the full pipeline" / "set up the brand from scratch". ## When NOT to use - Brand already has a design system; just need one artifact → call the artifact skill directly. - User wants to iterate on existing tokens → call `design-system` directly. ## Steps | Step name | Stage | Invokes | |---------------|--------------------|-------------------------------| | `plan` | Strategic intent | `design-plan` | | `system` | Token system | `design-system` | | `artifacts` | Artifact generation| `design-<artifact>` (varies) | | `screenshots` | PNG export | `screenshot-html` | ### Stage 1: Strategic intent — step `plan` — invokes `design-plan` Asks the brand-strategy questions (audience, voice, hard NOs, mood references) and writes `./design/<slug>/DESIGN-PLAN.md`. Output: `./design/<slug>/DESIGN-PLAN.md` exists. Checkpoint: confirm DESIGN-PLAN.md before generating tokens. ### Stage 2: Token system — step `system` — invokes `design-system` Reads DESIGN-PLAN.md and produces `DESIGN.md` (Google design.md spec format), `tokens.css`, and `showcase.html`. Output: three files in `./design/<slug>/`. C