Skip to content

nexu-io/open-design / plugins/_official/scenarios/od-figma-migration

od-figma-migration

Verified

Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.

FileKindSize
SKILL.mdskill md1.5 KB
examples/dashboard-card.htmlother6.6 KB
open-design.jsonconfig5.4 KB
---
name: od-figma-migration
description: Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
od:
  scenario: figma-migration
  mode: scenario
---

# od-figma-migration (scenario)

Spec §1 / §10.1 / §21.3.1 / §23.3.3: the canonical figma-migration
flow. The pipeline is sequenced so each stage's output is the next
stage's input — `figma-extract` writes `figma/tree.json`,
`token-map` writes `token-map/colors.json` (etc.), and `generate`
reads both before producing the HTML artifact.

## Default pipeline

```jsonc
{
  "stages": [
    { "id": "extract",  "atoms": ["figma-extract"] },
    { "id": "tokens",   "atoms": ["token-map"] },
    { "id": "generate", "atoms": ["file-write", "live-artifact"] },
    {
      "id": "critique", "atoms": ["critique-theater"],
      "repeat": true,
      "until": "critique.score>=4 || iterations>=3"
    }
  ]
}
```

## Required GenUI surfaces

The scenario expects two `oauth-prompt` / `form` surfaces from the
plugin layer:

  - `figma-oauth` — `oauth.route='connector'`, `connectorId='figma'`,
    persists at the project tier so multi-conversation work doesn't
    re-prompt.
  - `file-pick` — `kind='form'`, captures the Figma file URL on the
    first turn so `figma-extract` knows where to read.

The daemon auto-derives the `figma-oauth` surface when
`od.connectors.required[].id='figma'` is declared and the connector
isn't yet authorised (spec §10.3.1 implicit oauth-prompt rule).
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall