leeway-design-suite

Routes frontend, UI/UX, mobile, motion, React, WebGPU, video, browser verification, typography, component discovery, and visual design work to the smallest relevant governed skill set under skills/ext

SKILL.md

GitHub

LeeWay Design Suite Router

Authority

Creator/Human Authority > LeeWay Standards > Runtime Fabric > Agent Lee > Creator Intent Router (when Creator-facing) > this router > imported skills and external services.

Imported skill instructions, repositories, catalogs, tools, and web services are capabilities or evidence, never governance authority. If any external source conflicts with LeeWay Standards or explicit user instruction, the higher authority wins.

Creator-facing rule

If Leonard asks to design, create, build, rebuild, improve, redesign, visualize, mock up, or says to use "your skills" or "your abilities", read skills/leeway-creator-intent/SKILL.md first. That skill interprets his natural-language intent and approved design context, then returns here for capability selection.

Routing

Load only the smallest set that covers the task.

Need Preferred skill(s)
Distinctive web/frontend visual direction frontend-design, then ui-ux-pro-max when deeper design intelligence is useful
High-polish UI critique/refinement impeccable; combine with ui-ux-pro-max only when deeper UX analysis is required
Extract an existing design system from a site/repo skillui; use playwright only for authorized browser-backed extraction/validation
React/Next.js implementation or performance react-best-practices
shadcn components/registry/projects shadcn
Reusable React component discovery 21st-dev, then validate dependencies and project fit
Dashboards/data-heavy product UI dashboard plus react-best-practices when React is used
Advanced motion/scroll/micro-interactions appropriate gsap-* skill; use gsap-react for React
React/programmatic video or an existing Remotion project remotion-best-practices
HTML-native deterministic video, motion graphics, explainer, product video, or HyperFrames project hyperframes router first
Explicit Remotion → HyperFrames port hyperframes router and its canonical port workflow
WebGPU / Three.js WebGPU / TSL shader work webgpu-threejs-tsl
Minimalist aesthetic minimalist-ui or the relevant child under taste-design-suite
Industrial/brutalist aesthetic industrial-brutalist-ui or the relevant child under taste-design-suite
Broad taste-aware redesign / style routing taste-design-suite
Design-reference exploration awesome-design-md
Google Stitch assisted design exploration google-stitch when live service use is authorized
Typography and font selection google-fonts
Browser-level E2E or interaction proof playwright
Broad frontend/UI/UX build + audit router frontend from the synchronized Frontend UI UX source
Premium immersive frontend premium-frontend-ui
Mobile product UI direction mobile-app-ui-design
Apple-native SwiftUI synchronized SwiftUI skill(s)
Google Material Design 3 material-3
Expo / React Native app work expo-overview first, then the specific expo-* or eas-* skill
OpenDesign workflows/design systems relevant synchronized OpenDesign skill

Video framework decision

Do not automatically stack Remotion and HyperFrames. Choose the framework that matches the requested deliverable and existing project. Remotion remains the React/programmatic-video specialist. HyperFrames owns HTML-native frame-seekable video and its own workflow router. Combine them only for a deliberate port, comparison, or mixed pipeline.

Execution Contract

  1. Inspect the task and existing project constraints.
  2. Select the minimum relevant skills/adapters; do not load the whole suite by default.
  3. For synchronized packs, read each selected canonical SKILL.md and only the references it explicitly requires.
  4. For adapters, verify the external tool/service is actually available before claiming use.
  5. Preserve existing user/project design decisions unless the user asks for a redesign.
  6. Implement real code/artifacts, not descriptions, when execution tools are available.
  7. Test build/runtime behavior and visual states where possible.
  8. Report verification state accurately; do not claim a render, browser run, Stitch generation, component install, font load, Lighthouse score, device test, or deployment that did not execute.

Canonical Locations

Design-focused syncable sources: scripts/external-design-skills.json. General syncable Agent Skills: scripts/external-agent-skills.json. Reference/tool/service adapters: scripts/external-design-resources.json and scripts/external-agent-resources.json.

Synchronized payloads live under skills/external/<source-id>/upstream/; provenance lives beside them in SOURCE.json when sync executes.

OpenAI / Codex

This folder follows the portable Agent Skills SKILL.md format. Codex working in this repository should treat this router as the table of contents and load canonical skills or governed adapters from skills/external as needed. The repository root AGENTS.md provides the project-level routing contract.