nexu-io/open-design

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.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/nexu-io/open-design --skill reference-design-contract

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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 OpenDesign's

standard nine-section design-system shape.

  1. design-contract.md — the decision record: evidence used, keep/change

boundaries, rationale, risks, and quality gate.

  1. 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.

  1. Read evidence. Use provided screenshots, URLs, existing DESIGN.md,

brand docs, image artifacts, or user notes. If evidence is missing, say so and base the contract on the brief only; do not invent brand facts.

  1. Separate reference semantics. For every reference, split it into:
  • Keep: qualities to preserve, such as density, composition, material,

typography rhythm, color temperature, or motion attitude.

  • Change: subject matter, copy, brand marks, exact layout, protected

assets, and anything the user wants adapted.

  • Do not copy: literal screenshots, logos, claims, pricing, proprietary

UI, or exact prompt wording from examples.

  1. Freeze the direction. Choose one coherent visual stance. Do not provide

five unrelated moodboards. If there are genuinely competing directions, name them briefly, pick the recommended one, and continue.

  1. Write `DESIGN.md`. Use these nine headings exactly:
  • ## 1. Visual Theme & Atmosphere
  • ## 2. Color
  • ## 3. Typography
  • ## 4. Spacing & Grid
  • ## 5. Layout & Composition
  • ## 6. Components
  • ## 7. Motion & Interaction
  • ## 8. Voice & Brand
  • ## 9. Anti-patterns
  1. Write `design-contract.md`. Include:
  • goal and target artifact
  • evidence table with confidence (observed, provided, inferred)
  • keep/change/do-not-copy table
  • final design stance in one paragraph
  • risks and explicit unknowns
  • quality gate checklist
  1. Write `implementation-handoff.md`. Keep it short and operational:
  • files to read
  • token/palette/type/layout constraints
  • asset rules
  • responsive requirements
  • "first artifact should prove..." acceptance notes
  1. Validate. Read references/checklist.md and satisfy every P0 gate

before final handoff.

Output rules

  • Make every claim traceable to user input, observed reference evidence, or an

explicitly labeled inference.

  • Prefer concrete constraints over adjectives: "one warm accent, no purple or

blue glow" beats "premium".

  • Treat "do the same style" as "borrow controllable qualities", not "clone the

original subject or prompt".

  • If the user asks for immediate UI generation too, finish these contract files

first, then hand off to the appropriate artifact skill in the next step.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
nexu-io
Społeczność

redesign-existing-projects

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

Instalacje / 1h
4
GitHub Stars
108,8 tys.
Aktualizacja
21 lis
nexu-io
Społeczność

brandkit

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

Instalacje / 1h
3
GitHub Stars
108,8 tys.
Aktualizacja
21 lis
nexu-io
Społeczność

frame-liquid-bg-hero

WebGL-style fluid displacement background with a quote overlay, suited to video intros, landing heroes, or posters.

Instalacje / 1h
3
GitHub Stars
108,8 tys.
Aktualizacja
21 lis
nexu-io
Społeczność

industrial-brutalist-ui

Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.

Instalacje / 1h
3
GitHub Stars
108,8 tys.
Aktualizacja
21 lis