msd-core/docs/features/ui-design-contract.md at next

Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

1.7 KiB

Raw Permalink Blame History

id, title, group

id	title	group
3	UI Design Contract	Core Features

Command: /msd-ui-phase [N]

Purpose: Lock design decisions before planning so that all components in a phase share consistent visual standards.

Requirements:

REQ-UI-01: System MUST detect existing design system state (shadcn components.json, Tailwind config, tokens)
REQ-UI-02: System MUST ask only unanswered design contract questions
REQ-UI-03: System MUST validate against 7 dimensions (Copywriting, Visuals, Color, Typography, Spacing, Registry Safety, Inventory Provenance)
REQ-UI-04: System MUST enter revision loop if validation returns BLOCKED (max 2 iterations)
REQ-UI-05: System MUST offer shadcn initialization for React/Next.js/Vite projects without components.json
REQ-UI-06: System MUST enforce registry safety gate for third-party shadcn registries

Produces: {padded_phase}-UI-SPEC.md — Design contract consumed by executors

7 Validation Dimensions:

Copywriting — CTA labels, empty states, error messages
Visuals — Focal points, visual hierarchy, icon accessibility
Color — Accent usage discipline, 60/30/10 compliance
Typography — Font size/weight constraint adherence
Spacing — Grid alignment, token consistency
Registry Safety — Third-party component inspection requirements
Inventory Provenance — Component inventory enumerated from the installed design system, not recalled

shadcn Integration:

Detects missing components.json in React/Next.js/Vite projects
Guides user through ui.shadcn.com/create preset configuration
Preset string becomes a planning artifact reproducible across phases
Safety gate requires npx shadcn view and npx shadcn diff before third-party components

1.7 KiB Raw Permalink Blame History

1.7 KiB

Raw Permalink Blame History