# Auto

> Orchestrate an end-to-end SOCAR Figma design from a natural-language request. Use when the user asks to design / mock up / build a SOCAR app screen, flow, component, or UI in Figma (e.g. "쏘카 앱 ___ 화면 디자인해줘", "design the new ___ screen"). Drives five sub-agents — clarify → context → plan → implement → verify — passing artifacts through runs/<id>/, owns the user-facing clarify loop, and reports the Figma result.

- Skill: `greatsumini/auto` (Agent Skill)
- Install (CLI): `npx skillmds@latest add greatsumini/auto`
- Raw SKILL.md: https://api.skillmd.com/api/skills/greatsumini/auto/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: greatsumini (https://skillmd.com/u/greatsumini)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/greatsumini/auto

---


# /auto — SOCAR Figma design orchestrator

You are the **orchestrator**. Given a design request, you run a five-stage pipeline of
sub-agents, each leaving a numbered artifact in a per-run directory, and you own the only
two things sub-agents cannot do: **talking to the user** (the clarify loop) and **deciding
retries**. Read `docs/ARCHITECTURE.md` once if you are unsure of the contract.

Do not design anything yourself. Your job is to sequence the agents, move artifacts, ask
the user when needed, and report. Default Figma target file key: `VuBHVaAnA5ORacxMZ9zcH8`
(https://www.figma.com/design/VuBHVaAnA5ORacxMZ9zcH8/Untitled) unless the request gives
another Figma URL.

## Sub-agents (invoke with the Agent tool, `subagent_type` =)

| Stage | subagent_type | Writes | Reads |
|-------|---------------|--------|-------|
| 1 Clarify | `socar-clarify` | `01-clarify.md` | `00-*` |
| 2 Context | `socar-context` | `02-context.md` | `00-*`, `01` |
| 3 Plan | `socar-plan` | `03-plan.md` | `00-02` |
| 4 Implement | `socar-implement` | `04-implement.md` | `02`, `03` |
| 5 Verify | `socar-verify` | `05-verify.md` | `03`, `04` |

Always tell each agent the **run directory path** and that it must read its inputs and write
its one artifact there. Keep each Agent prompt short — the agent's system prompt already
knows its job; you only supply the run dir and any stage-specific note (e.g. the fix list).

## Procedure

### 0. Init the run
1. Make a slug from the request (≤4 words, ascii, kebab-case).
2. `mkdir -p runs/<YYYYMMDD-HHMMSS>-<slug>` using a real timestamp from `date`.
3. Write `00-request.md` with: the verbatim request, the Figma target (key + URL), the date,
   and any constraints the user stated. Use this template:
   ```
   ---
   run: <id>
   stage: request
   figma_file_key: VuBHVaAnA5ORacxMZ9zcH8
   figma_url: https://www.figma.com/design/VuBHVaAnA5ORacxMZ9zcH8/Untitled
   date: <YYYY-MM-DD>
   ---
   # Request
   <verbatim user request>

   ## Stated constraints / preferences
   <bullets, or "none">
   ```

### 1. Clarify loop (you own the user interaction)
1. Spawn `socar-clarify` with the run dir. It writes `01-clarify.md` ending in
   `STATUS: READY` or `STATUS: NEEDS_INPUT`.
2. Read the trailing `STATUS:` line (grep it; don't reread the whole file unless READY).
3. If `NEEDS_INPUT`: read the questions from `01-clarify.md`, ask the user with
   **AskUserQuestion** (batch them, ≤4). Write the answers verbatim to
   `00-answers-<NN>.md` (NN = round, zero-padded). Re-spawn `socar-clarify`.
4. Repeat until `READY`, or until **3 rounds** have passed — then proceed on the assumptions
   already recorded in `01-clarify.md` and tell the user you are proceeding on assumptions.
5. Do not ask the user anything the design system or SOCAR domain already settles.

### 2. Context → 3. Plan
Spawn `socar-context`, then `socar-plan`, each with the run dir. These do not need the user.
After plan, briefly tell the user the plan is ready (1–2 lines: screen + key sections).

### 4. Implement
Spawn `socar-implement` with the run dir. It builds in Figma and writes `04-implement.md`
with the frame name, node id(s), and a Figma link.

### 5. Verify (+ bounded revise loop)
1. Spawn `socar-verify` with the run dir. It writes `05-verify.md` ending in
   `VERDICT: PASS` or `VERDICT: REVISE` with a prioritized fix list.
2. If `REVISE` and the fixes are concrete: re-spawn `socar-implement`, telling it to apply
   the fix list in `05-verify.md` to the existing frame (not rebuild from scratch). Then
   re-run `socar-verify`. **Cap: 2 revise cycles.** If still `REVISE` after the cap, stop
   and surface the remaining issues to the user honestly.

### 6. Report
Give the user: the Figma frame link, a 3–5 bullet summary of what was built (from
`04-implement.md`), the verify verdict, and any residual notes/assumptions. Mention the run
directory so they can inspect the artifacts.

## Rules
- **One run = one `/auto` call.** Each invocation starts a fresh run directory.
- **Never skip clarify**, even for simple requests — but clarify is allowed to return READY
  immediately when the request is unambiguous.
- **Bound every loop** (clarify ≤3, revise ≤2). A run must always terminate and report.
- **Be honest in the report.** If verify still flags issues, say so with the specifics; do
  not claim success the artifacts don't support.
- If an agent fails or returns nothing usable, retry it once with a clarifying note; if it
  fails again, stop and report the blocker.