Agent skill · Design & Presentation

reference-design-contract

Turn vague taste, screenshots, URLs, product notes, or "make it feel like this" references into a grounded DESIGN.md plus an implementation handoff. Use it before prototypes, decks, redesigns, or image remix work when the user needs a reusable visual direction rather than a one-off prompt.

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill reference-design-contract --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/reference-design-contract/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Reference Design Contract Use this skill when the user has taste signals, references, or a rough "like this" request and needs a reusable design contract before generation. The goal is not to write a longer prompt. The goal is to make design decisions explicit enough that a later prototype, deck, redesign, or image-remix run can execute without guessing. ## What this skill produces Create three files: 1. `DESIGN.md` — the reusable visual direction, following Open Design's standard nine-section design-system shape. 2. `design-contract.md` — the decision record: evidence used, keep/change boundaries, rationale, risks, and quality gate. 3. `implementation-handoff.md` — concise build instructions for the next artifact-producing skill or coding agent. If a preview is useful, also create `example.html` as a small hand-built contract preview. Do not make it the main deliverable. ## Workflow 1. **Lock the job.** Identify target artifact type, audience, brand/product context, references, and constraints. Ask at most two questions only when a missing answer would change the direction. Otherwise choose a sensible default and label it as inferred. 2. **Read evidence.** Use provided screensho

What's inside
Steps it walks through
  1. What this skill produces
  2. Workflow
  3. Output rules
Ships with 2 files
  • example.html
  • references/checklist.md
More from open-design
All skills →
About this skill
What does the reference-design-contract skill do?

Turn vague taste, screenshots, URLs, product notes, or "make it feel like this" references into a grounded DESIGN.md plus an implementation handoff. Use it before prototypes, decks, redesigns, or image remix work when the user needs a reusable visual direction rather than a one-off prompt.

How do I install it?

Run `npx skills add nexu-io/open-design --skill reference-design-contract --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going