wehub-resource-sync
070959e133
landing-page-staging / Deploy landing page to staging (push) Has been skipped
landing-page-ci / Validate landing page (push) Failing after 4s
visual-baseline / Capture visual baselines (push) Has been cancelled
bake-plugin-previews / Bake plugin previews (push) Has been cancelled
1.5 KiB
1.5 KiB
Gradient 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
- Visual style: modern, playful
- Color stance: primary, secondary, neutral, success, warning, danger
- Design intent: Keep outputs recognizable to this style family while preserving usability and readability.
- Primary:
#990FFA— Token from style foundations.
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.