Connect your design system
Point preset at a repo or a token source so it has a system to govern.
Before preset can govern anything, it needs to read your system. Connecting imports it as structured data: tokens, components, patterns. Your source of truth stays where it lives; preset reads from it and stays in sync.
Choose a source
There are two common ways in:
- From a repository. Connect a Git repo and preset scans it for components, tokens, and usage. Best when your system lives in code.
- From a token source. Import design tokens directly. Best when you lead with tokens and a styling layer.
Start with whichever is most complete today. You can add the other later.
Publish it
Publishing makes the system readable by your tools and checkable by the governance engine. preset records what was configured rather than guessing it, so your tokens and components become the contract your agents read.
What preset reads
Once published, a connected tool can read your tokens, components, and patterns, check generated UI against your rules, and resolve a value the way your system defines it: not the way a generic model would guess. Next, give it rules to defer to: see Turn your system into rules. For source-specific setup, see the full docs.