create-style

Read ${CLAUDE_PLUGIN_ROOT}/skills/design-references/SKILL.md and ${CLAUDE_PLUGIN_ROOT}/skills/ui-style-format/SKILL.md before the first step; they hold the reference this command follows.

<user_request> $ARGUMENTS </user_request>

  **You MUST:**
  - Use AskUserQuestion for all user input gates
  - Use Write to create .claude/design-style.md
  - Use Read to check for existing style file
  - Use Bash for file operations in `.claude/` directory

  **You MUST NOT:**
  - Use Agent tool (this is not an orchestrator)
  - Modify any source code files outside `.claude/` directory
  - Make assumptions about user preferences

  **You MAY:**
  - Create and modify files in `.claude/` directory (design-style.md, design-references/)
  - Copy user-provided images to `.claude/design-references/`
  - Delete reference images when user confirms removal
</implementer_role>

<phase_reporting>
  There are no task-list tools. Announce each phase in one line of text
  (`**Phase N — starting.**` / `**Phase N — complete.**`, naming its artifacts). The
  style file and `.claude/design-references/` are the record.
</phase_reporting>

</critical_constraints>

  `update`, with or without a section, needs an existing `.claude/design-style.md`. If
  the file is missing, reply "No style yet. Run `/designer:create-style create`." and stop.
</action_routing>

<phase number="1" name="Initialization">
  <objective>Check for existing style and initialize wizard</objective>

  <steps>
    <step>Use Read tool to check if .claude/design-style.md exists</step>
    <step>If the action was `create` and the file exists, ask: replace the existing style or cancel?</step>
    <step>If no action was given and the file exists, ask: Update existing or create new?</step>
    <step>If the action was `update`, do not ask; it is already decided</step>
    <step>If updating, read existing file as base</step>
  </steps>

  <quality_gate>Action settled (new/update), from the argument or the user</quality_gate>
</phase>

<phase number="2" name="Base Reference">
  <objective>Select predefined design system as starting point</objective>

  <steps>
    <step>Present available design references using AskUserQuestion with options:
      1. Material Design 3 - Google's design system
      2. Apple Human Interface Guidelines - iOS/macOS patterns
      3. Tailwind UI - Utility-first CSS patterns
      4. Ant Design - Enterprise-level design system
      5. Shadcn/ui - Modern React component patterns
      6. Start from scratch (no base reference)
    </step>
    <step>Store selected base reference</step>
  </steps>