[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P1APCV2A19Q25GJ9X4NTPE":3,"skill-same:01M6P1APCV2A19Q25GJ9X4NTPE":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":43,"commitSha":60,"skillDirectory":61,"forksCount":13,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6P1APCV2A19Q25GJ9X4NTPE","design-system",null,"Mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdesign-system\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,5,46,47,48,49],"design","design system","system","hierarchy","frontend","building components","invariants","loading","critical","mechanical","token","wed","main","community","typography","design systems","architecture","components","frontend design","2026-11-10 10:12:30",false,"---\nname: design-system\ndescription: \"Mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Ftree\u002Fmain\u002Fdesign-system\nsource_repo: connerkward\u002Fckw-design-skill\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002FLICENSE\nauthor: Conner K Ward\n---\n\n# Design system\n## When to Use\n\nUse this skill when you need mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems. (Aesthetic direction lives in...\n\n\nApply with **design** when implementing UI: components, pages, or design systems. Every color, type, and motion choice should trace back to these rules.\n\n## Token architecture\n\nAll colors map to a small set of primitives. No random hex values.\n\n- **Foreground**: Text hierarchy (primary, secondary, muted).\n- **Background**: Surface elevation (base, raised, overlay).\n- **Border**: Separation hierarchy (subtle, default, emphasis).\n- **Brand**: Identity and primary accent.\n- **Semantic**: Destructive, warning, success (and optional info).\n\nUse tokens in code (CSS variables, theme objects); never hardcode hex for UI.\n\n## Typography\n\n- **Hierarchy**: Headlines — heavier weight, tighter letter-spacing for presence. Body — comfortable weight for readability. Labels\u002FUI — medium weight, works at smaller sizes. Data — monospace, `tabular-nums` for alignment.\n- Combine size, weight, and letter-spacing so hierarchy is clear at a glance. If you squint and can't tell headline from body, hierarchy is too weak.\n- **Fonts**: pair a display font with a body font; keep hierarchy legible at a glance. *Which* fonts is direction, not mechanics — pick from the domain and push off your first\u002Fdefault instinct (the mean); see design-spatial §2.\n- **Data (functional only)**: real aligned numbers, IDs, timestamps in monospace with `tabular-nums` — mono earns its place when values line up in a column. Do NOT sprinkle mono on decorative eyebrow\u002Fmetadata microtext (\"35MM · DEVELOP · SCAN\", fake spec captions) for a \"technical\" look — that's the current trend-slop, not data. See design-spatial §2.\n\n## Loading order — first seen, first loaded\n\nThe first viewport must paint complete and correct, fast. Order every resource by whether the user sees it first; the rest waits.\n\n- **Prioritize only the above-the-fold set** (hero text, hero image\u002Fvideo, brand mark). Preloading everything is the same as preloading nothing — the true criticals lose the bandwidth race. Pick the few things in the first screenful and prioritize *those*.\n- **Fonts: self-host WOFF2.** Convert OTF\u002FTTF → WOFF2 (Brotli; ~half the bytes, identical glyphs) and `\u003Clink rel=\"preload\" as=\"font\" type=\"font\u002Fwoff2\" crossorigin>` the weights used in the first viewport. Never a render-blocking third-party font stylesheet — a Google Fonts `\u003Clink>` adds a CSS round-trip plus extra DNS\u002FTLS before the font even starts downloading; self-host instead.\n- **LCP image\u002Fvideo:** `fetchpriority=\"high\"` on the hero image (or the video poster); `\u003Clink rel=\"preload\" as=\"image\">` it when it's CSS-referenced (the parser can't see CSS `url()`s early). The hero box must never be empty — ship a poster\u002Flow-res placeholder so there's no blank frame.\n- **Below the fold:** `loading=\"lazy\" decoding=\"async\"` on images; `preload=\"none\"` (or `\"metadata\"`) on video; `defer` non-critical JS. Always reserve space (`aspect-ratio`, or `width`+`height`) so deferred media can't shift layout (CLS).\n- Keep the render-blocking head minimal: inline critical CSS, defer the rest.\n\n## Never let fonts pop in (no FOUT) — ever\n\n`font-display: swap` **is** the pop — it paints a fallback face, then swaps to the webfont and reflows. Do not use it for any text the user watches load (titles, wordmarks, hero copy). The rule is absolute: title\u002Fdisplay text must never flash a fallback or reflow.\n\n- **Gate visibility on the real font.** Synchronously in `\u003Chead>`, add a `fonts-pending` class to `\u003Chtml>` that holds the display-font text at `opacity: 0`. On `document.fonts.ready` — kick it with `document.fonts.load('\u003Cweight> 1em \"Family\"')` for each critical face — swap to `fonts-ready` and fade the text in (~0.5s). Always include a safety timeout (~2.5s) that reveals regardless, so a font failure can never leave text permanently hidden.\n- Pair this with preload + WOFF2 (above) so the hidden window is a few hundred ms, not seconds — the fade reads as intentional, not as a stall.\n- For body text where a sub-perceptual swap is tolerable, at minimum kill the reflow: define a fallback `@font-face` (or `font-family` fallback) tuned with `size-adjust` \u002F `ascent-override` \u002F `descent-override` so the fallback occupies the same metrics as the webfont and the swap shifts nothing.\n\nWorked example — an AR product-research page: a head script toggles `fonts-pending → fonts-ready` (titles fade in on `fonts.ready`, 2.5s fallback), preloads the four above-the-fold WOFF2 weights, and self-hosts the brand face so there's no Google round-trip.\n\n## Slow-loading content — never show the ugly intermediate state\n\nAnything that *could* take a noticeable moment to be ready — fonts (above), large images, video, `\u003Ccanvas>` scenes, Three.js \u002F WebGL, lazy-loaded React islands, anything that fetches over the network or runs heavy main-thread setup — must either **arrive fast** or **load gracefully**. The default browser behavior (blank box → partial paint → reflow → final state) is the ugly intermediate state. Catch it.\n\nTwo levers; use both:\n\n- **Arrive faster.** Compress (WOFF2 for fonts, Draco for glTF, WebP\u002FAVIF for images, h264\u002Fh265 for video with `preload=\"metadata\"`). Preload the *few* assets the first viewport actually needs (`\u003Clink rel=\"preload\">`). Lazy-load below-the-fold so the LCP set isn't competing. Reserve the box (`aspect-ratio`, `width`+`height`) so deferred content can't trigger CLS.\n- **Load gracefully.** Hide the in-flight state behind a styled placeholder, then fade the real thing in. Skeleton boxes, low-res blurred posters, a single ASCII glyph, even just the container's bg color — anything coherent with the design beats the default partial-paint.\n\nWhat \"ugly\" looks like, concretely, and the fix:\n\n| Symptom | Fix |\n|---|---|\n| Annotation labels stack at `translate(0,0)` (top-left of container) until JS positions them | Start labels at `opacity: 0` with a `transition: opacity ~0.35s`; first projection sets inline opacity → CSS fades them up. |\n| Canvas\u002FWebGL paints empty\u002Fblack for a frame on first render | Show a placeholder (CSS art, low-res poster image, or paper\u002Fskeleton fill) in the same box; remove it once the first real frame has rendered. |\n| Lazy image fetches and snaps in with a layout-jump | `aspect-ratio` + `\u003Clink rel=\"preload\">` (above-the-fold) or `loading=\"lazy\" decoding=\"async\"` (below); fade from `opacity:0` on the `load` event for the first paint. |\n| Video poster pops to first frame on play | `poster` matches a still you control; once `playing` event fires, you've already had a clean handoff. |\n| 3D model \"appears\" mid-screen with no transition | Keep the canvas visible but at `opacity: 0`; toggle a `.viewer-ready` class (or set inline opacity) inside the GLTFLoader success callback, after the first `tick()`. |\n| Lazy React island flashes a fallback that looks worse than no UI | Replace `Suspense` fallback with a skeleton that traces the final layout, not a spinner. |\n\nRule of thumb: if a user could screenshot the page mid-load and you'd be embarrassed, you owe it a graceful state. The placeholder doesn't have to be fancy — it has to be *intentional*, sized correctly, and in the design language of what's coming.\n\n## Chrome stays still — status text never resizes layout\n\nPersistent chrome (headers, nav, toolbars, search bars, status regions) must hold a **constant height** no matter what text lands in it. Transient status \u002F loading \u002F explanatory copy — \"loading model…\", \"N matching · M indexed\", empty-state hints — must not wrap to a second line and shove adjacent controls down. A status region that grows and shrinks as its message changes is a layout-jank bug, not dynamic content.\n\n- **Constrain to one line:** `white-space: nowrap; overflow: hidden; text-overflow: ellipsis` so the longest message truncates instead of wrapping.\n- **Reserve the space up front:** give the container a fixed `height` (or `min-height`) sized for the message, so the shortest and longest states — and the empty state — occupy the same footprint.\n\nOnly the content area should move while chrome stays fixed; layout shift from transient text reads as broken polish. (Concrete failure this prevents: in a search app, a model-loading message wrapping to two lines and pushing the search bar downward.)\n\n## Motion\n\n- Keep timing consistent and purposeful; one well-orchestrated moment (staggered page load with `animation-delay`) beats scattered micro-interactions. Prefer CSS-only for HTML; Motion library for React. (Honor `prefers-reduced-motion` for public\u002Fmulti-user projects.)\n- **Defaults for restrained\u002Fprofessional UIs** (a starting point, not law): micro-interactions ~150ms, larger transitions 200–250ms, ease-out. A playful\u002Ftoy-like tone (design-thinking) may want spring\u002Fbounce and longer beats — match motion feel to the chosen direction rather than defaulting to these numbers.\n- **Choreography** — for anything beyond a single micro-interaction (route\u002Fpage transitions, list reorder, reveals, shared elements), load [references\u002Fmotion-choreography.md](references\u002Fmotion-choreography.md): when a transition earns its keep (it must *communicate* something or get cut), which kinds to implement and in what order, **style by navigation type** (directional slide only for hierarchical\u002Fordered — a slide between peers lies about depth; laterals fade), a duration table, and craft (compositor-only props, motion-blur on morphs, never raster-scale text, persistent-chrome isolation). Framework-agnostic.\n\n### Scroll-driven narrative (scrollytelling)\n\nFor **explanatory \u002F editorial \u002F data-walkthrough** content, prefer **scroll-driven graphics over click-interactive widgets**. A reader scrolls by default; making them hunt for and click a toggle to advance an explanation adds friction and gets skipped. Use the NYT\u002FPudding pattern: pin one graphic (`position: sticky`) while short text \"steps\" scroll past it, and let each step drive the graphic's state.\n\n- **Mechanics:** one `IntersectionObserver` with `rootMargin: '-48% 0px -48% 0px'` (threshold 0) so a step goes \"active\" exactly as it crosses the viewport mid-line; the active index re-renders the pinned graphic. ~30 lines — this *is* scrollama minus the dependency; don't add a scroll library.\n- **Layout:** two columns — steps scroll in one, the graphic `sticky top-0 h-screen` in the other; stack on mobile with the graphic sticky on top. Give each step ~85vh so exactly one is centered at a time; dim the inactive step cards (`opacity:.3`) so the live one reads.\n- **Graphic is a pure function of the active step** (`graphic(active)`), holding no click state of its own — so it also screenshots\u002Fexports deterministically and degrades to a static figure. Animate *between* states (color \u002F width \u002F opacity, 300–700ms) so scrolling feels continuous, not steppy.\n- **When NOT to:** dashboards, tools, forms — anything the user *operates* rather than *reads* — stay interactive. Scrollytelling is for **narration**, where you own the order. (Public\u002Fmulti-user builds: honor `prefers-reduced-motion` per the Motion note above; keep the state changes but drop the tweens.)\n\n## Spatial composition & layout\n\nGrid systems, the 8-point spacing scale, visual-weight balance, alignment, and the render-then-critique loop live in **design-spatial** ([..\u002Fdesign-spatial\u002FSKILL.md](..\u002Fdesign-spatial\u002FSKILL.md)) — the mechanical counterpart to this file's tokens\u002Ftype\u002Fcolor. Load it whenever composing pages, dashboards, or components. (Direction nugget that belongs here: match composition ambition to the vision — maximalist earns elaborate\u002Flayered code; minimal\u002Frefined demands restraint and precise spacing.)\n\n## Nested radii (only when one rounded element sits inside another)\n\nNot a push to round things — this governs the case where a rounded element is nested in\nanother (a button in a card, an inset panel in a container). When nested:\n\n- **Child radius ≤ parent radius**, never larger (a child corner rounder than its parent looks\n  like it's bulging out).\n- **Concentric** is the ideal: `child_radius = parent_radius − gap` (the padding between them),\n  so the two curves run parallel and the inner corner echoes the outer. Flat\u002Funrounded children\n  in a rounded parent are fine; what reads as broken is mismatched, non-concentric curves.\n\n## Color\n\n- **Palette from domain**: colors should feel like they came *from* the product's world, not applied on top.\n- **Beyond temperature**: quiet vs loud, dense vs spacious, serious vs playful, geometric vs organic — not just warm\u002Fcool.\n- **Color carries meaning**: gray builds structure; color communicates status, action, emphasis, identity. Unmotivated color is noise. (Restraint — one accent, not five — is a direction principle; see design-thinking → *reserve impact for punctuation*.)\n- **Contrast — APCA for decisions, WCAG for the gate.** For *perceptual* contrast judgments (is this text comfortably readable on this surface?) prefer **APCA** ([apcacontrast.com](https:\u002F\u002Fapcacontrast.com\u002F)) — it models lightness perception far better than the WCAG 2 ratio, which mis-rates light-on-dark and mid-tones. Keep **WCAG 2 (4.5 \u002F 3:1) as the compliance floor** — it's what `design-spatial`'s `layout-audit.js` gates on and what accessibility standards require. Use APCA to design, WCAG to certify.\n- **Interactive states gain contrast.** `:hover`, `:active`, `:focus` must read as *more* prominent than rest — more contrast, not less. A hover that lowers contrast (e.g. lightens text toward the bg) reads as disabled.\n\nAvoiding the generic\u002Ftrend look (Inter, purple-on-white, the same dark-glass card) and varying across generations is **design-spatial §2** — not restated here.\n\n## Backgrounds & detail\n\nAtmosphere over flat fills — but matched to the chosen aesthetic, not a default. The reflexive gradient-mesh \u002F noise \u002F grain \"premium\" treatment is itself the designer-trend mean (design-spatial §2); reach for it only when the direction genuinely calls for it, never as decoration for its own sake.\n\n## Example\n\n**User request:**\n\n> Review this interface with @design-system, identify the highest-impact design problems, and propose an implementation-ready improvement.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Design system\n## When to Use\n\nUse this skill when you need mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems. (Aesthetic direction lives in...\n\n\nApply with **design** when implementing UI: components, pages, or design systems. Every color, type, and motion choice should trace back to these rules.\n\n## Token architecture\n\nAll colors map to a small set of primitives. No random hex values.\n\n- **Foreground**: Text hierarchy (primary, secondary, muted).\n- **Background**: Surface elevation (base, raised, overlay).\n- **Border**: Separation hierarchy (subtle, default, emphasis).\n- **Brand**: Identity and primary accent.\n- **Semantic**: Destructive, warning, success (and optional info).\n\nUse tokens in code (CSS variables, theme objects); never hardcode hex for UI.\n\n## Typography\n\n- **Hierarchy**: Headlines — heavier weight, tighter letter-spacing for presence. Body — comfortable weight for readability. Labels\u002FUI — medium weight, works at smaller sizes. Data — monospace, `tabular-nums` for alignment.\n- Combine size, weight, and letter-spacing so hierarchy is clear at a glance. If you squint and can't tell headline from body, hierarchy is too weak.\n- **Fonts**: pair a display font with a body font; keep hierarchy legible at a glance. *Which* fonts is direction, not mechanics — pick from the domain and push off your first\u002Fdefault instinct (the mean); see design-spatial §2.\n- **Data (functional only)**: real aligned numbers, IDs, timestamps in monospace with `tabular-nums` — mono earns its place when values line up in a column. Do NOT sprinkle mono on decorative eyebrow\u002Fmetadata microtext (\"35MM · DEVELOP · SCAN\", fake spec captions) for a \"technical\" look — that's the current trend-slop, not data. See design-spatial §2.\n\n## Loading order — first seen, first loaded\n\nThe first viewport must paint complete and correct, fast. Order every resource by whether the user sees it first; the rest waits.\n\n- **Prioritize only the above-the-fold set** (hero text, hero image\u002Fvideo, brand mark). Preloading everything is the same as preloading nothing — the true criticals lose the bandwidth race. Pick the few things in the first screenful and prioritize *those*.\n- **Fonts: self-host WOFF2.** Convert OTF\u002FTTF → WOFF2 (Brotli; ~half the bytes, identical glyphs) and `\u003Clink rel=\"preload\" as=\"font\" type=\"font\u002Fwoff2\" crossorigin>` the weights used in the first viewport. Never a render-blocking third-party font stylesheet — a Google Fonts `\u003Clink>` adds a CSS round-trip plus extra DNS\u002FTLS before the font even starts downloading; self-host instead.\n- **LCP image\u002Fvideo:** `fetchpriority=\"high\"` on the hero image (or the video poster); `\u003Clink rel=\"preload\" as=\"image\">` it when it's CSS-referenced (the parser can't see CSS `url()`s early). The hero box must never be empty — ship a poster\u002Flow-res placeholder so there's no blank frame.\n- **Below the fold:** `loading=\"lazy\" decoding=\"async\"` on images; `preload=\"none\"` (or `\"metadata\"`) on video; `defer` non-critical JS. Always reserve space (`aspect-ratio`, or `width`+`height`) so deferred media can't shift layout (CLS).\n- Keep the render-blocking head minimal: inline critical CSS, defer the rest.\n\n## Never let fonts pop in (no FOUT) — ever\n\n`font-display: swap` **is** the pop — it paints a fallback face, then swaps to the webfont and reflows. Do not use it for any text the user watches load (titles, wordmarks, hero copy). The rule is absolute: title\u002Fdisplay text must never flash a fallback or reflow.\n\n- **Gate visibility on the real font.** Synchronously in `\u003Chead>`, add a `fonts-pending` class to `\u003Chtml>` that holds the display-font text at `opacity: 0`. On `document.fonts.ready` — kick it with `document.fonts.load('\u003Cweight> 1em \"Family\"')` for each critical face — swap to `fonts-ready` and fade the text in (~0.5s). Always include a safety timeout (~2.5s) that reveals regardless, so a font failure can never leave text permanently hidden.\n- Pair this with preload + WOFF2 (above) so the hidden window is a few hundred ms, not seconds — the fade reads as intentional, not as a stall.\n- For body text where a sub-perceptual swap is tolerable, at minimum kill the reflow: define a fallback `@font-face` (or `font-family` fallback) tuned with `size-adjust` \u002F `ascent-override` \u002F `descent-override` so the fallback occupies the same metrics as the webfont and the swap shifts nothing.\n\nWorked example — an AR product-research page: a head script toggles `fonts-pending → fonts-ready` (titles fade in on `fonts.ready`, 2.5s fallback), preloads the four above-the-fold WOFF2 weights, and self-hosts the brand face so there's no Google round-trip.\n\n## Slow-loading content — never show the ugly intermediate state\n\nAnything that *could* take a noticeable moment to be ready — fonts (above), large images, video, `\u003Ccanvas>` scenes, Three.js \u002F WebGL, lazy-loaded React islands, anything that fetches over the network or runs heavy main-thread setup — must either **arrive fast** or **load gracefully**. The default browser behavior (blank box → partial paint → reflow → final state) is the ugly intermediate state. Catch it.\n\nTwo levers; use both:\n\n- **Arrive faster.** Compress (WOFF2 for fonts, Draco for glTF, WebP\u002FAVIF for images, h264\u002Fh265 for video with `preload=\"metadata\"`). Preload the *few* assets the first viewport actually needs (`\u003Clink rel=\"preload\">`). Lazy-load below-the-fold so the LCP set isn't competing. Reserve the box (`aspect-ratio`, `width`+`height`) so deferred content can't trigger CLS.\n- **Load gracefully.** Hide the in-flight state behind a styled placeholder, then fade the real thing in. Skeleton boxes, low-res blurred posters, a single ASCII glyph, even just the container's bg color — anything coherent with the design beats the default partial-paint.\n\nWhat \"ugly\" looks like, concretely, and the fix:\n\n| Symptom | Fix |\n|---|---|\n| Annotation labels stack at `translate(0,0)` (top-left of container) until JS positions them | Start labels at `opacity: 0` with a `transition: opacity ~0.35s`; first projection sets inline opacity → CSS fades them up. |\n| Canvas\u002FWebGL paints empty\u002Fblack for a frame on first render | Show a placeholder (CSS art, low-res poster image, or paper\u002Fskeleton fill) in the same box; remove it once the first real frame has rendered. |\n| Lazy image fetches and snaps in with a layout-jump | `aspect-ratio` + `\u003Clink rel=\"preload\">` (above-the-fold) or `loading=\"lazy\" decoding=\"async\"` (below); fade from `opacity:0` on the `load` event for the first paint. |\n| Video poster pops to first frame on play | `poster` matches a still you control; once `playing` event fires, you've already had a clean handoff. |\n| 3D model \"appears\" mid-screen with no transition | Keep the canvas visible but at `opacity: 0`; toggle a `.viewer-ready` class (or set inline opacity) inside the GLTFLoader success callback, after the first `tick()`. |\n| Lazy React island flashes a fallback that looks worse than no UI | Replace `Suspense` fallback with a skeleton that traces the final layout, not a spinner. |\n\nRule of thumb: if a user could screenshot the page mid-load and you'd be embarrassed, you owe it a graceful state. The placeholder doesn't have to be fancy — it has to be *intentional*, sized correctly, and in the design language of what's coming.\n\n## Chrome stays still — status text never resizes layout\n\nPersistent chrome (headers, nav, toolbars, search bars, status regions) must hold a **constant height** no matter what text lands in it. Transient status \u002F loading \u002F explanatory copy — \"loading model…\", \"N matching · M indexed\", empty-state hints — must not wrap to a second line and shove adjacent controls down. A status region that grows and shrinks as its message changes is a layout-jank bug, not dynamic content.\n\n- **Constrain to one line:** `white-space: nowrap; overflow: hidden; text-overflow: ellipsis` so the longest message truncates instead of wrapping.\n- **Reserve the space up front:** give the container a fixed `height` (or `min-height`) sized for the message, so the shortest and longest states — and the empty state — occupy the same footprint.\n\nOnly the content area should move while chrome stays fixed; layout shift from transient text reads as broken polish. (Concrete failure this prevents: in a search app, a model-loading message wrapping to two lines and pushing the search bar downward.)\n\n## Motion\n\n- Keep timing consistent and purposeful; one well-orchestrated moment (staggered page load with `animation-delay`) beats scattered micro-interactions. Prefer CSS-only for HTML; Motion library for React. (Honor `prefers-reduced-motion` for public\u002Fmulti-user projects.)\n- **Defaults for restrained\u002Fprofessional UIs** (a starting point, not law): micro-interactions ~150ms, larger transitions 200–250ms, ease-out. A playful\u002Ftoy-like tone (design-thinking) may want spring\u002Fbounce and longer beats — match motion feel to the chosen direction rather than defaulting to these numbers.\n- **Choreography** — for anything beyond a single micro-interaction (route\u002Fpage transitions, list reorder, reveals, shared elements), load [references\u002Fmotion-choreography.md](references\u002Fmotion-choreography.md): when a transition earns its keep (it must *communicate* something or get cut), which kinds to implement and in what order, **style by navigation type** (directional slide only for hierarchical\u002Fordered — a slide between peers lies about depth; laterals fade), a duration table, and craft (compositor-only props, motion-blur on morphs, never raster-scale text, persistent-chrome isolation). Framework-agnostic.\n\n### Scroll-driven narrative (scrollytelling)\n\nFor **explanatory \u002F editorial \u002F data-walkthrough** content, prefer **scroll-driven graphics over click-interactive widgets**. A reader scrolls by default; making them hunt for and click a toggle to advance an explanation adds friction and gets skipped. Use the NYT\u002FPudding pattern: pin one graphic (`position: sticky`) while short text \"steps\" scroll past it, and let each step drive the graphic's state.\n\n- **Mechanics:** one `IntersectionObserver` with `rootMargin: '-48% 0px -48% 0px'` (threshold 0) so a step goes \"active\" exactly as it crosses the viewport mid-line; the active index re-renders the pinned graphic. ~30 lines — this *is* scrollama minus the dependency; don't add a scroll library.\n- **Layout:** two columns — steps scroll in one, the graphic `sticky top-0 h-screen` in the other; stack on mobile with the graphic sticky on top. Give each step ~85vh so exactly one is centered at a time; dim the inactive step cards (`opacity:.3`) so the live one reads.\n- **Graphic is a pure function of the active step** (`graphic(active)`), holding no click state of its own — so it also screenshots\u002Fexports deterministically and degrades to a static figure. Animate *between* states (color \u002F width \u002F opacity, 300–700ms) so scrolling feels continuous, not steppy.\n- **When NOT to:** dashboards, tools, forms — anything the user *operates* rather than *reads* — stay interactive. Scrollytelling is for **narration**, where you own the order. (Public\u002Fmulti-user builds: honor `prefers-reduced-motion` per the Motion note above; keep the state changes but drop the tweens.)\n\n## Spatial composition & layout\n\nGrid systems, the 8-point spacing scale, visual-weight balance, alignment, and the render-then-critique loop live in **design-spatial** ([..\u002Fdesign-spatial\u002FSKILL.md](..\u002Fdesign-spatial\u002FSKILL.md)) — the mechanical counterpart to this file's tokens\u002Ftype\u002Fcolor. Load it whenever composing pages, dashboards, or components. (Direction nugget that belongs here: match composition ambition to the vision — maximalist earns elaborate\u002Flayered code; minimal\u002Frefined demands restraint and precise spacing.)\n\n## Nested radii (only when one rounded element sits inside another)\n\nNot a push to round things — this governs the case where a rounded element is nested in\nanother (a button in a card, an inset panel in a container). When nested:\n\n- **Child radius ≤ parent radius**, never larger (a child corner rounder than its parent looks\n  like it's bulging out).\n- **Concentric** is the ideal: `child_radius = parent_radius − gap` (the padding between them),\n  so the two curves run parallel and the inner corner echoes the outer. Flat\u002Funrounded children\n  in a rounded parent are fine; what reads as broken is mismatched, non-concentric curves.\n\n## Color\n\n- **Palette from domain**: colors should feel like they came *from* the product's world, not applied on top.\n- **Beyond temperature**: quiet vs loud, dense vs spacious, serious vs playful, geometric vs organic — not just warm\u002Fcool.\n- **Color carries meaning**: gray builds structure; color communicates status, action, emphasis, identity. Unmotivated color is noise. (Restraint — one accent, not five — is a direction principle; see design-thinking → *reserve impact for punctuation*.)\n- **Contrast — APCA for decisions, WCAG for the gate.** For *perceptual* contrast judgments (is this text comfortably readable on this surface?) prefer **APCA** ([apcacontrast.com](https:\u002F\u002Fapcacontrast.com\u002F)) — it models lightness perception far better than the WCAG 2 ratio, which mis-rates light-on-dark and mid-tones. Keep **WCAG 2 (4.5 \u002F 3:1) as the compliance floor** — it's what `design-spatial`'s `layout-audit.js` gates on and what accessibility standards require. Use APCA to design, WCAG to certify.\n- **Interactive states gain contrast.** `:hover`, `:active`, `:focus` must read as *more* prominent than rest — more contrast, not less. A hover that lowers contrast (e.g. lightens text toward the bg) reads as disabled.\n\nAvoiding the generic\u002Ftrend look (Inter, purple-on-white, the same dark-glass card) and varying across generations is **design-spatial §2** — not restated here.\n\n## Backgrounds & detail\n\nAtmosphere over flat fills — but matched to the chosen aesthetic, not a default. The reflexive gradient-mesh \u002F noise \u002F grain \"premium\" treatment is itself the designer-trend mean (design-spatial §2); reach for it only when the direction genuinely calls for it, never as decoration for its own sake.\n\n## Example\n\n**User request:**\n\n> Review this interface with @design-system, identify the highest-impact design problems, and propose an implementation-ready improvement.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":39,"author":55,"source":56,"license":14,"date_added":57,"description":7,"source_repo":58,"source_type":44,"license_source":59},"Conner K Ward","https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Ftree\u002Fmain\u002Fdesign-system",1782864000000,"connerkward\u002Fckw-design-skill","https:\u002F\u002Fgithub.com\u002Fconnerkward\u002Fckw-design-skill\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fdesign-system","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill design-system",{"tool":71,"command":72},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill design-system",{"tool":74,"command":75},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdesign-system\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fmotion-choreography.md","REFERENCE","参考文档",6541,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdesign-system\u002Freferences\u002Fmotion-choreography.md",[86,111,135,160,186,210],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":50},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[96,97,98,47,99,100,88,101,102,103,104,105,44,43,106,39,107,108,109,110],"ZeRO","trust","zero trust","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":50},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[118,119,120,121,122,123,124,125,126,127,128,129,130,105,131,44,132,133,39,134],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":50},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[142,143,144,145,146,147,148,149,150,151,152,153,154,44,43,155,156,157,158,159],"transcript","youtube transcript","youtube","safe","github","codex","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":175,"publishedAt":50},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[166,169,172],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":173,"categoryName":174,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师",[142,143,144,176,145,177,146,147,149,178,179,180,181,152,182,44,43,183,184,185],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":50},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},[144,197,198,122,145,199,200,201,202,149,180,203,204,205,206,43,207,155,208,209],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":50},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[216],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},[218,144,219,220,145,177,178,221,222,179,180,181,152,223,182,44,43,183,224,158],"youtube full","full","google","server","dlp","credits","automatic"]