mirror of
https://github.com/nexu-io/open-design.git
synced 2026-10-27 09:51:12 +01:00
a2809ea336
* design-systems: backfill 2.0 package batch 09 * fix: repair design token source references * fix: update latest design token source references * fix: tighten design token source validation --------- Co-authored-by: chaoxiaoche <chaoxiaoche@chaoxiaochedeMacBook-Pro.local>
1.6 KiB
1.6 KiB
Superhuman Usage
Design System 2.0 package guide for Open Design agents and reviewers.
Read Order
- Read this file first to understand the package contract.
- Read
DESIGN.mdfor visual intent, constraints, and anti-patterns. - Paste
tokens.cssinto the first artifact<style>block before writing component CSS. - Use
components.manifest.jsonfor the compact component inventory; opencomponents.htmlwhen exact selectors or states matter. - Inspect
preview/pages when a visual sanity check is useful.
Design Highlights
- Deep purple gradient hero (
#1b1938) contrasting against a predominantly white content body - Super Sans VF variable font with non-standard weight stops (460, 540, 600, 700) — sits between conventional weight categories
- Ultra-tight display line-height (0.96) creating compressed, powerful headlines
- Warm Cream (
#e9e5dd) buttons instead of bright/saturated CTAs — understated luxury
Do
- Preserve the schema token names exactly so cross-brand switching stays reliable.
- Use
--accentfor primary actions, links, focus states, and one clear focal element. - Reuse component groups from
components.manifest.jsonbefore inventing new controls. - Treat
source/files as audit evidence for the bundled fixture backfill.
Avoid
- Avoid raw hex values outside the copied
:roottoken block. - Avoid redefining Tailwind or design-token values independently of
tokens.css. - Avoid claiming original upstream source evidence; this package is based on the curated bundled fixture.
- Avoid adding new component recipes that are not represented in
components.htmlorDESIGN.md.