Building a Design System Package on Remix

The result of following this skill is a standalone package under packages/ that:

• reuses Naked UI for interaction behavior, Mix for styling mechanics, and Remix for component machinery — and adds only the target system's design decisions on top;
• generates its entire token surface from pinned, traceable sources (never hand-copied values), reproducibly and CI-enforced;
• exposes an idiomatic public API in the target system's vocabulary, not Remix's or Fortal's.

remix_fortal is the in-repo precedent for the packages/<name> shape this skill describes: a standalone, separately versioned package that depends on remix, owns its own token scope, and generates its widget catalog with @MixWidget. Follow that structure. Do not clone Fortal's content and swap colors — its values are hand-authored against a pinned Radix parity contract, whereas a new design system generates its tokens from its own pinned sources.