Run this workflow at the start of a design or UI implementation task so generated components match the repository's actual stack, tokens, and conventions.
Steps
- Check local handoff state: Run
relay_list(or check/exonui:resume) to see if an active.exonui/relay/packet already defines decisions,designRefs, andnextStep. - Read project config & design intent: · Read
exonui.json(or inspect viagrid_status) for the activeprofile, enabledpacks,exposure, andpolicy. · ReadDESIGN.mdat the project root if present for typography, colour, spacing, motion, and principle constraints. - Inspect framework & design tokens in code: · Check
package.jsonfor React/Next.js/Vite/Tailwind versions and installed animation/UI libraries (motion,gsap,lenis,lucide-react). · Locate global CSS tokens (globals.css,theme.css, Tailwind@themeblocks, ortokens.jsonDTCG files) so new UI uses semantic tokens rather than hardcoded hex values or raw spacing guesses. - Pull pack notes before adding dependencies: · If the stack uses libraries covered by ExonUI Grid Notes (
shadcn,motion,gsap,lenis,react-bits,magic-ui, etc.), calllibrary_docsfirst to follow project-specific integration pitfalls and compatibility notes.
Guardrails
- Never invent token names, CSS utilities, or component props without reading the target codebase first.
- Keep
library_docsandgrid_searchtargeted so context stays small for implementation.
Done when
- Active Relay decisions,
DESIGN.mdrules, token definitions, and installed packages are confirmed before writing code.