[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASK8VPSMFG23HGGZ22VVBY":3,"skill-same:01M7ASK8VPSMFG23HGGZ22VVBY":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASK8VPSMFG23HGGZ22VVBY","ui-ux-design-systems-platforms-and-accessibility",null,"Use when building or governing a design system, matching platform conventions, or meeting accessibility requirements. Covers what a design system actually is, the three-tier token architecture, component API design, measuring adoption; Apple HIG and Liquid Glass, Material 3 and M3 Expressive, web conventions, desktop (macOS, Windows, GNOME, KDE), consistency vs nativeness; and accessibility — the standards and the law in 2026 (WCAG 2.2\u002F3.0, EN 301 549, the European Accessibility Act, ADA Title II), contrast and the APCA question, the practical checklist, and testing.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-design-systems-platforms-and-accessibility\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-ux-design-systems-platforms-and-accessibility\ndescription: \"Use when building or governing a design system, matching platform conventions, or meeting accessibility requirements. Covers what a design system actually is, the three-tier token architecture, component API design, measuring adoption; Apple HIG and Liquid Glass, Material 3 and M3 Expressive, web conventions, desktop (macOS, Windows, GNOME, KDE), consistency vs nativeness; and accessibility — the standards and the law in 2026 (WCAG 2.2\u002F3.0, EN 301 549, the European Accessibility Act, ADA Title II), contrast and the APCA question, the practical checklist, and testing.\"\n---\n\n# UI\u002FUX Design: Design Systems and Tokens, Platform Conventions, and Accessibility\n\n> **Part 3 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §7–§9. Sibling skills: `ui-ux-cognition-heuristics-and-navigation` (§0–§3), `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-writing-forms-research-and-ethics` (§10–§14), `ui-ux-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `ui-ux-reference` for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §7. Design Systems and Tokens\n\n### 7.1 What a design system actually is\n\nNot a component library. A design system is **a set of shared decisions, encoded so they\ncan't drift** — plus the governance that keeps them shared. It has four layers:\n\n```\nPrinciples        — how we decide (rarely written well, hugely valuable when it is)\nFoundations       — tokens: color, type, space, radius, elevation, motion, breakpoints\nComponents        — buttons, inputs, dialogs; with documented props, states, a11y behaviour\nPatterns          — how components compose into recurring solutions (forms, empty states,\n                    destructive flows, onboarding, data tables)\n```\nPlus: documentation, contribution model, versioning, deprecation policy, and adoption\nmetrics. **A component library without governance decays into a component graveyard.**\n\n### 7.2 Token architecture — the three-tier model\n\n```\nTier 1  PRIMITIVE \u002F global    blue-500 = #3B82F6      spacing-4 = 16px\n          ↓ referenced by\nTier 2  SEMANTIC \u002F alias      color.action.primary → blue-500       (light)\n                              color.action.primary → blue-300       (dark)\n                              space.stack.md → spacing-4\n          ↓ referenced by\nTier 3  COMPONENT-SPECIFIC    button.primary.background → color.action.primary\n```\n**[DURABLE] Components must only ever reference tiers 2 and 3.** The moment a component\nhardcodes `blue-500`, you cannot theme, cannot do dark mode without a rewrite, and cannot\nrebrand. This one rule is most of the value of tokens.\n\n**The DTCG spec is now real.** The **W3C Design Tokens Community Group published its first\nstable specification, version 2025.10, on 28 October 2025** — a vendor-neutral JSON\ninterchange format with `$value`\u002F`$type`, composite types (shadows, gradients, typography\nsets, transitions, borders), references that survive transforms, groups, `$description`,\n`$extensions`, `$deprecated`, multi-file support, and modern color spaces. It was developed\nwith 20+ editors from Adobe, Google, Microsoft, Meta, Salesforce, Figma, Shopify, Sketch,\nPenpot and others.\n\n**⚠️ Precision matters here:** it is a **W3C *Community Group* specification, not a W3C\nRecommendation** — stable and production-ready, but not on the Standards Track. Say\n\"the DTCG specification\" rather than \"the W3C standard\" when accuracy counts.\n\nTooling as of 2026: **Style Dictionary v4** ships first-class DTCG support (full 2025.10\nsupport is landing in v5); Figma Variables can export to the format; Tokens Studio,\nTerrazzo, Penpot, Supernova, Knapsack and zeroheight support or are implementing it. File\nconvention: `.tokens` \u002F `.tokens.json`, media type `application\u002Fdesign-tokens+json`.\n\n```json\n{\n  \"color\": {\n    \"$type\": \"color\",\n    \"blue\": { \"500\": { \"$value\": \"#3b82f6\" }, \"300\": { \"$value\": \"#93c5fd\" } },\n    \"action\": {\n      \"primary\": {\n        \"$value\": \"{color.blue.500}\",\n        \"$description\": \"Primary interactive fill. Light theme.\"\n      }\n    }\n  },\n  \"space\": {\n    \"$type\": \"dimension\",\n    \"4\": { \"$value\": { \"value\": 16, \"unit\": \"px\" } }\n  }\n}\n```\n\n**A token pipeline that works:**\n```\nFigma Variables \u002F Tokens Studio\n   → push branch → GitHub PR\n      → CI: JSON-schema validate against DTCG\n              lint (no orphan tokens, no missing $type, no raw hex in components,\n                    contrast check on every semantic fg\u002Fbg pair)\n              build via Style Dictionary → CSS custom properties, Swift, Kotlin, JSON\n              visual regression on the component library\n      → merge → versioned release → consumed by apps\n```\n**[DURABLE] The hard part was never the format.** It's governance: who can add a token, how\ndeprecation works, how you stop 400 one-off values from accumulating, and how you get teams\nto actually adopt. The DTCG spec closed the interoperability problem; it did not close the\norganizational one.\n\n### 7.3 Component API design\n\nTreat components as an API with a compatibility contract:\n- **Props over variants-by-copy.** One Button with `variant`, `size`, `state` — not five\n  Buttons.\n- **Composition over configuration** for anything open-ended. A `Card` that accepts\n  children beats a `Card` with 22 boolean props.\n- **Accessibility is inside the component, not a documentation note.** If the Dialog\n  component doesn't trap focus, restore focus, and wire `aria-modal`, every consumer will\n  get it wrong.\n- **Every component documents: purpose, when *not* to use it, all states, keyboard\n  behaviour, a11y notes, and do\u002Fdon't examples.** The \"when not to use\" section is the one\n  people skip and the one that prevents misuse.\n- Version with semver; deprecate with a documented migration and a codemod where possible.\n\n### 7.4 Measuring adoption\n\nA design system's only real metric is **adoption**: percentage of UI built from system\ncomponents, number of one-off\u002Fdetached components, token coverage vs. hardcoded values,\ntime-to-ship a standard screen. Design-token adoption is now the norm rather than the\nexception (an industry survey of ~300 professionals reported ~84% team adoption in 2026,\nup from ~56% a year earlier) — so the differentiating question has moved from \"do you use\ntokens\" to \"is the token graph actually the single source of truth.\"\n\n---\n\n## §8. Platform Conventions\n\n**[DURABLE] Jakob's Law applies to platforms.** Users bring expectations from every other\napp on that OS. Violating them is expensive; the only good reason is that the convention is\ngenuinely wrong for your domain, and you should be able to say why.\n\n### 8.1 Apple — HIG, and Liquid Glass\n\nCore Apple principles: **clarity, deference (content over chrome), depth**. Concretely:\n- Navigation is hierarchical (push\u002Fpop), flat (tabs), or content-driven.\n- **44 × 44 pt** touch targets; **Dynamic Type** support; SF Symbols for iconography.\n- Back navigation is top-left plus edge-swipe; there is no system Back button.\n- Modality is a strong statement — use sheets for focused sub-tasks, alerts sparingly.\n- macOS additionally expects a full menu bar, multiple windows, unlimited undo (§8.4).\n\n**macOS 26 \u002F iOS 26 introduced Liquid Glass** — a translucent, light-refracting material\nacross toolbars, sidebars, tab bars, sheets, popovers, controls, the Dock and menu bar.\nWhat matters for design work:\n- **Framework chrome adopts it free on recompile** against the 26 SDK, across SwiftUI,\n  UIKit and AppKit. **Custom components do not** — that's where the work is.\n- Opt-in APIs: `.glassEffect()`, `GlassEffectContainer`, `glassEffectID` for morphing.\n- Navigation now *floats over* content, which changes safe-area assumptions.\n- Icons require rework via **Icon Composer** (layered vector, blur\u002Ftranslucency, specular\n  highlights) — the flat 1024 px PNG workflow is obsolete.\n- **⚠️ Accessibility:** translucency degrades text contrast. Respect **Reduce Transparency**\n  and **Increase Contrast**, and test with both on. Apple's own first-year implementation\n  drew substantial legibility criticism; treat restraint as the default.\n\n### 8.2 Google — Material 3 and M3 Expressive\n\nMaterial 3 brought dynamic color (Material You), a token-based architecture, and adaptive\nlayouts. **Material 3 Expressive** (announced May 2025) is an *enhancement to M3, not \"M4\"*,\nadding a physics-based motion system, an expanded type scale with emphasized styles, a shape\nsystem with morphing, and bolder color.\n\n**It is unusually well-evidenced for a design language.** Google reports **46 research\nstudies with 18,000+ participants over ~3 years**, using eye-tracking, surveys and usability\ntrials. Reported findings: users spotted key UI elements **up to 4× faster** than in prior\nMaterial 3; time-to-tap on key actions decreased significantly; and — the most interesting\nresult — **the usability age gap largely disappeared**, with older participants spotting key\nelements as quickly as younger ones.\n\n**[CONTESTED] How much to generalize from that.** The studies are Google's own, largely\nunpublished in peer-reviewed venues, and measure Google's components in Google's contexts.\nThe mechanism behind the headline result is not mysterious — bigger, bolder, better-placed\nprimary actions are easier to find, which Fitts and von Restorff already predicted. The\nhonest reading: **the direction is well-supported (expressiveness and usability are not\nopposed, and prominence helps older users disproportionately); the specific multipliers\nshould not be quoted as universal.** Google's own team notes the intent isn't to make every\ninteraction playful — \"you might not want a super-playful UI for paying a parking ticket.\"\n\nAndroid specifics that trip up iOS-first designers: the **system Back** (gesture or button)\nwith defined semantics, the **app bar** rather than a centered title, **FAB** for a single\nprimary action, **48 dp** targets, and Material's own navigation components (nav bar, nav\nrail for tablets, nav drawer).\n\n### 8.3 Web\n\nThe web has no HIG — it has conventions, and breaking them is more costly than on any\nnative platform because users arrive with expectations from the entire internet:\n- Logo top-left links home. Nav in the header. Search where search goes.\n- **Links look like links** (underline or unambiguous styling) and behave like links\n  (middle-click, right-click, ⌘-click all work — which requires a real `\u003Ca href>`, not a\n  `\u003Cdiv onClick>`).\n- Browser **Back must work**, including in SPAs.\n- Forms submit on Enter. Autofill works (correct `autocomplete` attributes — this is both\n  a conversion and an accessibility feature).\n- **Never disable zoom** (`user-scalable=no` \u002F `maximum-scale=1`) — WCAG failure and a\n  hostile act toward low-vision users.\n- Respect `prefers-color-scheme`, `prefers-reduced-motion`, `prefers-contrast`.\n\n### 8.4 Desktop (macOS \u002F Windows \u002F GNOME \u002F KDE)\n\n- **Menu bar as complete command index.** Every command should appear in a menu even if\n  it's also a toolbar button — that's how Help search, keyboard discovery, and accessibility\n  find it.\n- **Unlimited, coalescing undo.** Typing 30 characters is one undo step.\n- **Multi-window and window-state restoration** are baseline expectations, not features.\n- **Keyboard-first** operation; show shortcuts in menus.\n- **Density is higher and users want it.** Desktop is where power users live.\n- **[PLATFORM] Linux is not one convention.** GNOME's HIG favours header bars with a\n  hamburger and no menu bar; KDE retains traditional menu bars and far more configurability.\n  Pick per your target desktop and be internally consistent; use libadwaita\u002FKDE components\n  and you inherit the right answer.\n\n### 8.5 Cross-platform: consistency vs. nativeness\n\n**[CONTESTED]** Brand-consistent-everywhere (Flutter, a strong web design system) versus\nnative-idiomatic-per-platform (SwiftUI + Material + platform toolkit).\n- *For consistency*: one design, one implementation, one QA surface; users recognize your\n  product across devices; cheaper by a large factor.\n- *For nativeness*: users' expectations are set by the platform, not by you; native\n  components carry accessibility, localization, dark mode, dynamic type, and platform\n  updates **for free**; the uncanny-valley cost of \"almost native\" is real and is felt as\n  low quality.\n- **The defensible split:** be brand-consistent in *identity* (color, type, tone, iconography,\n  illustration) and platform-native in *interaction* (navigation model, gestures, controls,\n  system integration). Users forgive different-looking; they don't forgive different-behaving.\n\n---\n\n## §9. Accessibility\n\n### 9.1 The frame\n\n**[DURABLE] Accessibility is not a feature for a minority.** Roughly 1.3 billion people\nlive with significant disability; add situational (bright sun, one hand full, noisy room)\nand temporary (broken arm, eye dilation) impairments and the addressable population is\neveryone. It is also now, in most of the markets a product ships to, **the law**.\n\n**POUR** — the four WCAG principles:\n- **Perceivable** — information must be presentable in ways users can perceive (alt text,\n  captions, contrast, not-color-alone).\n- **Operable** — all functionality via keyboard, enough time, no seizure triggers,\n  navigable, adequate targets.\n- **Understandable** — readable, predictable, error-preventing and error-explaining.\n- **Robust** — works with assistive technologies; valid, semantic markup.\n\n### 9.2 The standards and the law (2026)\n\n| Regime | Standard | Status |\n|---|---|---|\n| **WCAG 2.2** | Current W3C Recommendation (Oct 2023, updated Dec 2024) | **Approved as ISO\u002FIEC 40500:2025** — enabling more countries to adopt it formally |\n| **WCAG 2.1 AA** | The level most laws actually cite | The de facto global legal baseline |\n| **WCAG 3.0** | **Working Draft only** (updated March 2026, ~174 requirements; Bronze\u002FSilver\u002FGold outcome-based scoring replacing A\u002FAA\u002FAAA) | **Not a legal requirement anywhere.** Candidate Recommendation anticipated ~late 2027; final Recommendation realistically 2028–2030. **Will not deprecate WCAG 2.** |\n| **EU — European Accessibility Act** | EN 301 549 (currently incorporates WCAG 2.1 AA; **v4.1.1 expected 2026 will move to WCAG 2.2**) | **Enforceable since 28 June 2025** for new products\u002Fservices. Applies to businesses *anywhere* selling to EU consumers. Existing services have until 28 June 2030; contracts concluded pre-June-2025 until June 2027. Microenterprise exemption (\u003C10 employees AND \u003C€2M turnover) applies to services, not products, and not to non-EU firms serving the EU. Enforcement is per-member-state. |\n| **US — ADA Title II** | WCAG 2.1 AA, by DOJ final rule (April 2024) | ⚠️ **Deadlines extended by one year on 20 April 2026** via Interim Final Rule: entities serving **50,000+ → 26 April 2027**; under 50,000 and special districts → **26 April 2028**. The extension changes only the date — the underlying obligation is in force now and people can sue today. |\n| **US — ADA Title III** (private business) | No explicit WCAG mandate | Courts apply WCAG anyway; thousands of suits per year (4,600+ in 2025, up ~14% YoY per UsableNet). |\n| **US — Section 508** | WCAG 2.0 AA (federal) | |\n| **US — Section 504 \u002F HHS** | WCAG 2.1 AA | Deadlines also extended in May 2026: ≥15 employees → 11 May 2027; \u003C15 → 10 May 2028 |\n| **UK** | Equality Act; PSBAR for public sector | WCAG 2.1\u002F2.2 AA |\n\n**[DURABLE, practical] Build to WCAG 2.2 AA.** It is a superset of 2.1 AA, so you exceed\nevery current legal requirement, you're already compliant when EN 301 549 moves to 2.2, and\nyou're positioned for whatever 3.0 becomes. **Do not wait for WCAG 3.0** — Bronze is\nexpected to be roughly equivalent to today's 2.2 AA, so conforming now is the head start.\n\n### 9.3 Contrast, and the APCA question\n\n**Current requirement (WCAG 2.x, and therefore the law):** 4.5:1 body text, 3:1 large text\n(≥18 pt \u002F 14 pt bold), 3:1 for UI components and graphical objects (SC 1.4.11). The\nalgorithm is a relative-luminance ratio, polarity-insensitive.\n\n**[CONTESTED — and this one has legal consequences.] APCA** (Advanced Perceptual Contrast\nAlgorithm) is a perceptual model producing an `Lc` value that accounts for font size,\nweight, and polarity. Its proponents argue — with real evidence — that WCAG 2's math\nsystematically **overstates** contrast when both colors are dark (which is why WCAG-passing\ndark-mode palettes can be functionally unreadable) and **understates** some light-background\npairs that are demonstrably readable.\n\n**But:** APCA is a *candidate* method for WCAG 3, which is a Working Draft. No law anywhere\nreferences it. And accessibility practitioners — notably Adrian Roselli, whose April 2026\nanalysis is the reference on this — warn that advising teams to *replace* WCAG 2 contrast\nwith APCA creates legal risk, and that WCAG 3's contrast approach is far from settled.\n\n**The defensible position for 2026: conform to WCAG 2 contrast (that's what you'll be\naudited against), and optionally *also* check APCA to catch the cases WCAG 2's math misses\n— particularly in dark mode.** Choose colors that satisfy both. Do not present APCA\nconformance as legal compliance.\n\nWorth internalizing: contrast remains the **most common accessibility failure on the web** —\nthe WebAIM Million 2026 report found WCAG 2 contrast failures on **83.9% of the top million\nhome pages**, up from 79.1% the prior year, averaging ~34 low-contrast instances per page.\nThis is the cheapest defect class to fix and the one most consistently shipped.\n\n### 9.4 The practical checklist\n\nBeyond contrast, the failures that appear on the overwhelming majority of sites are: missing\nalt text, unlabeled form inputs, empty links\u002Fbuttons, and missing document language. Those\nfour plus contrast are ~95% of automatically-detectable issues.\n\n- **Semantic structure** — real headings in order (no skipping levels), landmarks, lists as\n  lists, tables with headers. A screen-reader user navigates by headings; a page of styled\n  `\u003Cdiv>`s is a wall.\n- **Every input has a persistent, programmatically associated `\u003Clabel>`.** Placeholder text\n  is not a label — it disappears on focus, fails contrast, and breaks autofill and\n  translation.\n- **Alt text**: describe *purpose*, not appearance. Decorative images get `alt=\"\"`.\n  Complex images (charts) need a longer description elsewhere.\n- **Focus management**: on route change, on modal open\u002Fclose, on dynamic content insertion.\n  Announce with a live region when appropriate; don't overuse `aria-live=\"assertive\"`.\n- **ARIA rule zero: no ARIA is better than bad ARIA.** Use a native `\u003Cbutton>` before you\n  build `role=\"button\"` with keyboard handlers.\n- **Captions and transcripts** for media; audio description where visual info is essential.\n- **Don't rely on hover or precise timing.**\n- **Support 200% zoom and 320 px reflow** without horizontal scrolling (SC 1.4.10).\n\n### 9.5 Testing\n\n- **Automated tools (axe, Lighthouse, WAVE, Pa11y) catch roughly a third of issues.** They\n  are necessary and radically insufficient. Run them in CI as a floor.\n- **Manual keyboard pass**: unplug the mouse, do every task.\n- **Screen reader pass**: VoiceOver (macOS\u002FiOS), NVDA or JAWS (Windows), TalkBack (Android),\n  Orca (Linux). Test with at least one; behaviours differ meaningfully.\n- **Zoom to 200% and 400%**; test with OS-level larger text.\n- **Test with users with disabilities.** This is the only method that finds the issues the\n  other four can't.\n- **⚠️ Accessibility overlay widgets** (one-line JavaScript \"compliance\" products) have\n  repeatedly failed to provide a defense in litigation and drew FTC action; they are widely\n  opposed by the accessibility community and by screen-reader users. They are not a\n  remediation strategy.\n","# UI\u002FUX Design: Design Systems and Tokens, Platform Conventions, and Accessibility\n\n> **Part 3 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §7–§9. Sibling skills: `ui-ux-cognition-heuristics-and-navigation` (§0–§3), `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-writing-forms-research-and-ethics` (§10–§14), `ui-ux-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `ui-ux-reference` for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §7. Design Systems and Tokens\n\n### 7.1 What a design system actually is\n\nNot a component library. A design system is **a set of shared decisions, encoded so they\ncan't drift** — plus the governance that keeps them shared. It has four layers:\n\n```\nPrinciples        — how we decide (rarely written well, hugely valuable when it is)\nFoundations       — tokens: color, type, space, radius, elevation, motion, breakpoints\nComponents        — buttons, inputs, dialogs; with documented props, states, a11y behaviour\nPatterns          — how components compose into recurring solutions (forms, empty states,\n                    destructive flows, onboarding, data tables)\n```\nPlus: documentation, contribution model, versioning, deprecation policy, and adoption\nmetrics. **A component library without governance decays into a component graveyard.**\n\n### 7.2 Token architecture — the three-tier model\n\n```\nTier 1  PRIMITIVE \u002F global    blue-500 = #3B82F6      spacing-4 = 16px\n          ↓ referenced by\nTier 2  SEMANTIC \u002F alias      color.action.primary → blue-500       (light)\n                              color.action.primary → blue-300       (dark)\n                              space.stack.md → spacing-4\n          ↓ referenced by\nTier 3  COMPONENT-SPECIFIC    button.primary.background → color.action.primary\n```\n**[DURABLE] Components must only ever reference tiers 2 and 3.** The moment a component\nhardcodes `blue-500`, you cannot theme, cannot do dark mode without a rewrite, and cannot\nrebrand. This one rule is most of the value of tokens.\n\n**The DTCG spec is now real.** The **W3C Design Tokens Community Group published its first\nstable specification, version 2025.10, on 28 October 2025** — a vendor-neutral JSON\ninterchange format with `$value`\u002F`$type`, composite types (shadows, gradients, typography\nsets, transitions, borders), references that survive transforms, groups, `$description`,\n`$extensions`, `$deprecated`, multi-file support, and modern color spaces. It was developed\nwith 20+ editors from Adobe, Google, Microsoft, Meta, Salesforce, Figma, Shopify, Sketch,\nPenpot and others.\n\n**⚠️ Precision matters here:** it is a **W3C *Community Group* specification, not a W3C\nRecommendation** — stable and production-ready, but not on the Standards Track. Say\n\"the DTCG specification\" rather than \"the W3C standard\" when accuracy counts.\n\nTooling as of 2026: **Style Dictionary v4** ships first-class DTCG support (full 2025.10\nsupport is landing in v5); Figma Variables can export to the format; Tokens Studio,\nTerrazzo, Penpot, Supernova, Knapsack and zeroheight support or are implementing it. File\nconvention: `.tokens` \u002F `.tokens.json`, media type `application\u002Fdesign-tokens+json`.\n\n```json\n{\n  \"color\": {\n    \"$type\": \"color\",\n    \"blue\": { \"500\": { \"$value\": \"#3b82f6\" }, \"300\": { \"$value\": \"#93c5fd\" } },\n    \"action\": {\n      \"primary\": {\n        \"$value\": \"{color.blue.500}\",\n        \"$description\": \"Primary interactive fill. Light theme.\"\n      }\n    }\n  },\n  \"space\": {\n    \"$type\": \"dimension\",\n    \"4\": { \"$value\": { \"value\": 16, \"unit\": \"px\" } }\n  }\n}\n```\n\n**A token pipeline that works:**\n```\nFigma Variables \u002F Tokens Studio\n   → push branch → GitHub PR\n      → CI: JSON-schema validate against DTCG\n              lint (no orphan tokens, no missing $type, no raw hex in components,\n                    contrast check on every semantic fg\u002Fbg pair)\n              build via Style Dictionary → CSS custom properties, Swift, Kotlin, JSON\n              visual regression on the component library\n      → merge → versioned release → consumed by apps\n```\n**[DURABLE] The hard part was never the format.** It's governance: who can add a token, how\ndeprecation works, how you stop 400 one-off values from accumulating, and how you get teams\nto actually adopt. The DTCG spec closed the interoperability problem; it did not close the\norganizational one.\n\n### 7.3 Component API design\n\nTreat components as an API with a compatibility contract:\n- **Props over variants-by-copy.** One Button with `variant`, `size`, `state` — not five\n  Buttons.\n- **Composition over configuration** for anything open-ended. A `Card` that accepts\n  children beats a `Card` with 22 boolean props.\n- **Accessibility is inside the component, not a documentation note.** If the Dialog\n  component doesn't trap focus, restore focus, and wire `aria-modal`, every consumer will\n  get it wrong.\n- **Every component documents: purpose, when *not* to use it, all states, keyboard\n  behaviour, a11y notes, and do\u002Fdon't examples.** The \"when not to use\" section is the one\n  people skip and the one that prevents misuse.\n- Version with semver; deprecate with a documented migration and a codemod where possible.\n\n### 7.4 Measuring adoption\n\nA design system's only real metric is **adoption**: percentage of UI built from system\ncomponents, number of one-off\u002Fdetached components, token coverage vs. hardcoded values,\ntime-to-ship a standard screen. Design-token adoption is now the norm rather than the\nexception (an industry survey of ~300 professionals reported ~84% team adoption in 2026,\nup from ~56% a year earlier) — so the differentiating question has moved from \"do you use\ntokens\" to \"is the token graph actually the single source of truth.\"\n\n---\n\n## §8. Platform Conventions\n\n**[DURABLE] Jakob's Law applies to platforms.** Users bring expectations from every other\napp on that OS. Violating them is expensive; the only good reason is that the convention is\ngenuinely wrong for your domain, and you should be able to say why.\n\n### 8.1 Apple — HIG, and Liquid Glass\n\nCore Apple principles: **clarity, deference (content over chrome), depth**. Concretely:\n- Navigation is hierarchical (push\u002Fpop), flat (tabs), or content-driven.\n- **44 × 44 pt** touch targets; **Dynamic Type** support; SF Symbols for iconography.\n- Back navigation is top-left plus edge-swipe; there is no system Back button.\n- Modality is a strong statement — use sheets for focused sub-tasks, alerts sparingly.\n- macOS additionally expects a full menu bar, multiple windows, unlimited undo (§8.4).\n\n**macOS 26 \u002F iOS 26 introduced Liquid Glass** — a translucent, light-refracting material\nacross toolbars, sidebars, tab bars, sheets, popovers, controls, the Dock and menu bar.\nWhat matters for design work:\n- **Framework chrome adopts it free on recompile** against the 26 SDK, across SwiftUI,\n  UIKit and AppKit. **Custom components do not** — that's where the work is.\n- Opt-in APIs: `.glassEffect()`, `GlassEffectContainer`, `glassEffectID` for morphing.\n- Navigation now *floats over* content, which changes safe-area assumptions.\n- Icons require rework via **Icon Composer** (layered vector, blur\u002Ftranslucency, specular\n  highlights) — the flat 1024 px PNG workflow is obsolete.\n- **⚠️ Accessibility:** translucency degrades text contrast. Respect **Reduce Transparency**\n  and **Increase Contrast**, and test with both on. Apple's own first-year implementation\n  drew substantial legibility criticism; treat restraint as the default.\n\n### 8.2 Google — Material 3 and M3 Expressive\n\nMaterial 3 brought dynamic color (Material You), a token-based architecture, and adaptive\nlayouts. **Material 3 Expressive** (announced May 2025) is an *enhancement to M3, not \"M4\"*,\nadding a physics-based motion system, an expanded type scale with emphasized styles, a shape\nsystem with morphing, and bolder color.\n\n**It is unusually well-evidenced for a design language.** Google reports **46 research\nstudies with 18,000+ participants over ~3 years**, using eye-tracking, surveys and usability\ntrials. Reported findings: users spotted key UI elements **up to 4× faster** than in prior\nMaterial 3; time-to-tap on key actions decreased significantly; and — the most interesting\nresult — **the usability age gap largely disappeared**, with older participants spotting key\nelements as quickly as younger ones.\n\n**[CONTESTED] How much to generalize from that.** The studies are Google's own, largely\nunpublished in peer-reviewed venues, and measure Google's components in Google's contexts.\nThe mechanism behind the headline result is not mysterious — bigger, bolder, better-placed\nprimary actions are easier to find, which Fitts and von Restorff already predicted. The\nhonest reading: **the direction is well-supported (expressiveness and usability are not\nopposed, and prominence helps older users disproportionately); the specific multipliers\nshould not be quoted as universal.** Google's own team notes the intent isn't to make every\ninteraction playful — \"you might not want a super-playful UI for paying a parking ticket.\"\n\nAndroid specifics that trip up iOS-first designers: the **system Back** (gesture or button)\nwith defined semantics, the **app bar** rather than a centered title, **FAB** for a single\nprimary action, **48 dp** targets, and Material's own navigation components (nav bar, nav\nrail for tablets, nav drawer).\n\n### 8.3 Web\n\nThe web has no HIG — it has conventions, and breaking them is more costly than on any\nnative platform because users arrive with expectations from the entire internet:\n- Logo top-left links home. Nav in the header. Search where search goes.\n- **Links look like links** (underline or unambiguous styling) and behave like links\n  (middle-click, right-click, ⌘-click all work — which requires a real `\u003Ca href>`, not a\n  `\u003Cdiv onClick>`).\n- Browser **Back must work**, including in SPAs.\n- Forms submit on Enter. Autofill works (correct `autocomplete` attributes — this is both\n  a conversion and an accessibility feature).\n- **Never disable zoom** (`user-scalable=no` \u002F `maximum-scale=1`) — WCAG failure and a\n  hostile act toward low-vision users.\n- Respect `prefers-color-scheme`, `prefers-reduced-motion`, `prefers-contrast`.\n\n### 8.4 Desktop (macOS \u002F Windows \u002F GNOME \u002F KDE)\n\n- **Menu bar as complete command index.** Every command should appear in a menu even if\n  it's also a toolbar button — that's how Help search, keyboard discovery, and accessibility\n  find it.\n- **Unlimited, coalescing undo.** Typing 30 characters is one undo step.\n- **Multi-window and window-state restoration** are baseline expectations, not features.\n- **Keyboard-first** operation; show shortcuts in menus.\n- **Density is higher and users want it.** Desktop is where power users live.\n- **[PLATFORM] Linux is not one convention.** GNOME's HIG favours header bars with a\n  hamburger and no menu bar; KDE retains traditional menu bars and far more configurability.\n  Pick per your target desktop and be internally consistent; use libadwaita\u002FKDE components\n  and you inherit the right answer.\n\n### 8.5 Cross-platform: consistency vs. nativeness\n\n**[CONTESTED]** Brand-consistent-everywhere (Flutter, a strong web design system) versus\nnative-idiomatic-per-platform (SwiftUI + Material + platform toolkit).\n- *For consistency*: one design, one implementation, one QA surface; users recognize your\n  product across devices; cheaper by a large factor.\n- *For nativeness*: users' expectations are set by the platform, not by you; native\n  components carry accessibility, localization, dark mode, dynamic type, and platform\n  updates **for free**; the uncanny-valley cost of \"almost native\" is real and is felt as\n  low quality.\n- **The defensible split:** be brand-consistent in *identity* (color, type, tone, iconography,\n  illustration) and platform-native in *interaction* (navigation model, gestures, controls,\n  system integration). Users forgive different-looking; they don't forgive different-behaving.\n\n---\n\n## §9. Accessibility\n\n### 9.1 The frame\n\n**[DURABLE] Accessibility is not a feature for a minority.** Roughly 1.3 billion people\nlive with significant disability; add situational (bright sun, one hand full, noisy room)\nand temporary (broken arm, eye dilation) impairments and the addressable population is\neveryone. It is also now, in most of the markets a product ships to, **the law**.\n\n**POUR** — the four WCAG principles:\n- **Perceivable** — information must be presentable in ways users can perceive (alt text,\n  captions, contrast, not-color-alone).\n- **Operable** — all functionality via keyboard, enough time, no seizure triggers,\n  navigable, adequate targets.\n- **Understandable** — readable, predictable, error-preventing and error-explaining.\n- **Robust** — works with assistive technologies; valid, semantic markup.\n\n### 9.2 The standards and the law (2026)\n\n| Regime | Standard | Status |\n|---|---|---|\n| **WCAG 2.2** | Current W3C Recommendation (Oct 2023, updated Dec 2024) | **Approved as ISO\u002FIEC 40500:2025** — enabling more countries to adopt it formally |\n| **WCAG 2.1 AA** | The level most laws actually cite | The de facto global legal baseline |\n| **WCAG 3.0** | **Working Draft only** (updated March 2026, ~174 requirements; Bronze\u002FSilver\u002FGold outcome-based scoring replacing A\u002FAA\u002FAAA) | **Not a legal requirement anywhere.** Candidate Recommendation anticipated ~late 2027; final Recommendation realistically 2028–2030. **Will not deprecate WCAG 2.** |\n| **EU — European Accessibility Act** | EN 301 549 (currently incorporates WCAG 2.1 AA; **v4.1.1 expected 2026 will move to WCAG 2.2**) | **Enforceable since 28 June 2025** for new products\u002Fservices. Applies to businesses *anywhere* selling to EU consumers. Existing services have until 28 June 2030; contracts concluded pre-June-2025 until June 2027. Microenterprise exemption (\u003C10 employees AND \u003C€2M turnover) applies to services, not products, and not to non-EU firms serving the EU. Enforcement is per-member-state. |\n| **US — ADA Title II** | WCAG 2.1 AA, by DOJ final rule (April 2024) | ⚠️ **Deadlines extended by one year on 20 April 2026** via Interim Final Rule: entities serving **50,000+ → 26 April 2027**; under 50,000 and special districts → **26 April 2028**. The extension changes only the date — the underlying obligation is in force now and people can sue today. |\n| **US — ADA Title III** (private business) | No explicit WCAG mandate | Courts apply WCAG anyway; thousands of suits per year (4,600+ in 2025, up ~14% YoY per UsableNet). |\n| **US — Section 508** | WCAG 2.0 AA (federal) | |\n| **US — Section 504 \u002F HHS** | WCAG 2.1 AA | Deadlines also extended in May 2026: ≥15 employees → 11 May 2027; \u003C15 → 10 May 2028 |\n| **UK** | Equality Act; PSBAR for public sector | WCAG 2.1\u002F2.2 AA |\n\n**[DURABLE, practical] Build to WCAG 2.2 AA.** It is a superset of 2.1 AA, so you exceed\nevery current legal requirement, you're already compliant when EN 301 549 moves to 2.2, and\nyou're positioned for whatever 3.0 becomes. **Do not wait for WCAG 3.0** — Bronze is\nexpected to be roughly equivalent to today's 2.2 AA, so conforming now is the head start.\n\n### 9.3 Contrast, and the APCA question\n\n**Current requirement (WCAG 2.x, and therefore the law):** 4.5:1 body text, 3:1 large text\n(≥18 pt \u002F 14 pt bold), 3:1 for UI components and graphical objects (SC 1.4.11). The\nalgorithm is a relative-luminance ratio, polarity-insensitive.\n\n**[CONTESTED — and this one has legal consequences.] APCA** (Advanced Perceptual Contrast\nAlgorithm) is a perceptual model producing an `Lc` value that accounts for font size,\nweight, and polarity. Its proponents argue — with real evidence — that WCAG 2's math\nsystematically **overstates** contrast when both colors are dark (which is why WCAG-passing\ndark-mode palettes can be functionally unreadable) and **understates** some light-background\npairs that are demonstrably readable.\n\n**But:** APCA is a *candidate* method for WCAG 3, which is a Working Draft. No law anywhere\nreferences it. And accessibility practitioners — notably Adrian Roselli, whose April 2026\nanalysis is the reference on this — warn that advising teams to *replace* WCAG 2 contrast\nwith APCA creates legal risk, and that WCAG 3's contrast approach is far from settled.\n\n**The defensible position for 2026: conform to WCAG 2 contrast (that's what you'll be\naudited against), and optionally *also* check APCA to catch the cases WCAG 2's math misses\n— particularly in dark mode.** Choose colors that satisfy both. Do not present APCA\nconformance as legal compliance.\n\nWorth internalizing: contrast remains the **most common accessibility failure on the web** —\nthe WebAIM Million 2026 report found WCAG 2 contrast failures on **83.9% of the top million\nhome pages**, up from 79.1% the prior year, averaging ~34 low-contrast instances per page.\nThis is the cheapest defect class to fix and the one most consistently shipped.\n\n### 9.4 The practical checklist\n\nBeyond contrast, the failures that appear on the overwhelming majority of sites are: missing\nalt text, unlabeled form inputs, empty links\u002Fbuttons, and missing document language. Those\nfour plus contrast are ~95% of automatically-detectable issues.\n\n- **Semantic structure** — real headings in order (no skipping levels), landmarks, lists as\n  lists, tables with headers. A screen-reader user navigates by headings; a page of styled\n  `\u003Cdiv>`s is a wall.\n- **Every input has a persistent, programmatically associated `\u003Clabel>`.** Placeholder text\n  is not a label — it disappears on focus, fails contrast, and breaks autofill and\n  translation.\n- **Alt text**: describe *purpose*, not appearance. Decorative images get `alt=\"\"`.\n  Complex images (charts) need a longer description elsewhere.\n- **Focus management**: on route change, on modal open\u002Fclose, on dynamic content insertion.\n  Announce with a live region when appropriate; don't overuse `aria-live=\"assertive\"`.\n- **ARIA rule zero: no ARIA is better than bad ARIA.** Use a native `\u003Cbutton>` before you\n  build `role=\"button\"` with keyboard handlers.\n- **Captions and transcripts** for media; audio description where visual info is essential.\n- **Don't rely on hover or precise timing.**\n- **Support 200% zoom and 320 px reflow** without horizontal scrolling (SC 1.4.10).\n\n### 9.5 Testing\n\n- **Automated tools (axe, Lighthouse, WAVE, Pa11y) catch roughly a third of issues.** They\n  are necessary and radically insufficient. Run them in CI as a floor.\n- **Manual keyboard pass**: unplug the mouse, do every task.\n- **Screen reader pass**: VoiceOver (macOS\u002FiOS), NVDA or JAWS (Windows), TalkBack (Android),\n  Orca (Linux). Test with at least one; behaviours differ meaningfully.\n- **Zoom to 200% and 400%**; test with OS-level larger text.\n- **Test with users with disabilities.** This is the only method that finds the issues the\n  other four can't.\n- **⚠️ Accessibility overlay widgets** (one-line JavaScript \"compliance\" products) have\n  repeatedly failed to provide a defense in litigation and drew FTC action; they are widely\n  opposed by the accessibility community and by screen-reader users. They are not a\n  remediation strategy.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-design-systems-platforms-and-accessibility",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill ui-ux-design-systems-platforms-and-accessibility",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill ui-ux-design-systems-platforms-and-accessibility",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill ui-ux-design-systems-platforms-and-accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-design-systems-platforms-and-accessibility\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]