reference-design-contract

Convert design references and taste signals into a DESIGN.md contract and implementation handoff.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/webdevarif/claude-skills --skill reference-design-contract-webdevarif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reference-design-contract
Source: https://github.com/webdevarif/claude-skills/tree/main/reference-design-contract
Command: npx skills add https://github.com/webdevarif/claude-skills --skill reference-design-contract-webdevarif

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Vague requests like "make it feel like this" or a folder of screenshots give no reusable direction, so every prototype or redesign starts from guesswork. This Skill turns references, URLs, and product notes into an explicit, reusable design contract before any artifact is generated. ## Core Features & Use Cases - Reference decomposition: Splits every reference into Keep, Change, and Do-not-copy boundaries so style is borrowed without cloning brands, layouts, or proprietary UI. - Standardized DESIGN.md output: Generates a nine-section design system document covering visual theme, color, typography, spacing, layout, components, motion, voice, and anti-patterns. - Implementation handoff: Produces a concise handoff file with token, palette, type, and responsive constraints that a coding agent or artifact skill can execute directly. - Use Case: Before redesigning a developer-notes app, feed in three product screenshots and a short brief; receive DESIGN.md, a decision record with evidence confidence levels, and a build-ready handoff. ## Quick Start Create a reference design contract for my app using these screenshots and notes, and produce DESIGN.md plus an implementation handoff.

Frequently Asked Questions about reference-design-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn design references into a reusable design system?

Provide your references, screenshots, or URLs along with a brief describing the goal and audience. The skill decomposes each reference into keep, change, and do-not-copy boundaries, then writes a nine-section DESIGN.md plus an implementation handoff.

What files does a design contract workflow produce?

It produces three files: DESIGN.md with the nine standard design-system sections, design-contract.md recording evidence and decisions, and implementation-handoff.md with build constraints. An optional example.html preview can also be generated.

Can I use reference screenshots without copying the original design?

Yes. The workflow treats references as qualities to borrow, such as density, color temperature, and typography rhythm, while explicitly excluding logos, exact layouts, proprietary UI, and brand marks from the output contract.

When should I create a design contract instead of generating UI directly?

Create a contract first when the direction will be reused across prototypes, decks, or redesigns, or when references are ambiguous. If you only need a single one-off artifact with clear instructions, direct generation may be sufficient.

What happens if I have no reference images or brand documentation?

The skill proceeds from the brief alone and labels every decision as inferred rather than inventing brand facts. The design-contract.md file records evidence confidence as observed, provided, or inferred so gaps stay visible.