Default pipeline
Review the “Default pipeline” section in the pinned source before continuing.
Review and apply the “Default pipeline” source section.
nexu-io/open-design
od-figma-migration
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
58Collecting
See source evidenceView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-figma-migration"Source profileDesignCatalog only
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Limited to facts supported by the pinned source
What the pinned source establishes about od-figma-migration
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…
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-figma-migration"The pinned source contains about 153 English words and 2 usable sections. That evidence supports a source profile, not a complete guide.
153 source words · 2 usable sections
What the source actually contains
2 verifiable source sections for od-figma-migration
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
SKILL.md · Default pipeline
Required GenUI surfaces
The scenario expects two oauth-prompt / form surfaces from the plugin layer:
figma-oauth — oauth.route='connector', connectorId='figma',file-pick — kind='form', captures the Figma file URL on theThe scenario expects two oauth-prompt / form surfaces from the plugin layer:
Choose a different workflow
When another Skill is the better fit
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailchurn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detaildesign-intelligence
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
How do I install od-figma-migration?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-figma-migration". Inspect the command and pinned source before running it.
Repository stars
82,073
Repository forks
9,485
Quality
58/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation14/30
Specificity12/25
Maintenance20/20
Trust signals12/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
design-system-capture by event4u-app
Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.
existing-ui-audit by event4u-app
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
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
{
"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 sofigma-extractknows 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).
- Source repo
- nexu-io/open-design
- Skill path
- plugins/_official/scenarios/od-figma-migration/SKILL.md
- Commit SHA
- 89d6d4ef21ba
- Repository license
- Apache-2.0
- Data collected