nexu-io/open-design
Guided scenario for creating an Open Design plugin folder that can be installed into My plugins.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-plugin-authoring"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Use this scenario when the user wants to create their own Open Design plugin.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-plugin-authoring"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
220 source words · 3 usable sections
Design process
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
Produce a folder named generated-plugin/ in the active project workspace. At minimum, the folder must contain:
Follow docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.
Design checklist
The source section “Required outcome” has been checked.
The source section “Authoring rules” has been checked.
The source section “Suggested folder shape” has been checked.
Choose a different workflow
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 detailWhen 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 detailGrounded 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
Use this scenario when the user wants to create their own Open Design plugin.
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-plugin-authoring". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
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
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
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.
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.
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.
Use this scenario when the user wants to create their own Open Design plugin.
Produce a folder named generated-plugin/ in the active project workspace.
At minimum, the folder must contain:
SKILL.md with frontmatter and clear agent instructions.open-design.json with valid plugin metadata, od.kind, mode, task kind, capabilities, and inputs when needed.Add examples/, assets/, or other supporting files only when they help the plugin be used or reviewed.
docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.SKILL.md as the canonical behavior description. open-design.json should describe how Open Design installs, applies, and presents that behavior.generated-plugin/
SKILL.md
open-design.json
examples/
assets/
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.