Design system

Generated interfaces have to look like your product. Taiga supports that two ways, and the difference in quality between them is large.

Link the repository, or describe the standards

Design Standards is a document: your colors, typography, spacing and component patterns, written down. It is seeded during onboarding, so something sensible is always in place.

A linked design-system repository is the real thing. Agents read your actual components and tokens and build against them, rather than against a description of them.

Link the repository if you have one. A description is an approximation, and the approximation is where generated interfaces stop looking like yours. The standards document still applies until you do, and remains the answer if you have no such repository.

Deriving standards from a brand guide

If your brand lives in a document rather than in code, you can upload it. Taiga adapts your design standards to it, applying what the guide specifies and keeping the existing template for anything it does not cover.

Editing is paused while that runs, so the two do not fight over the same document.

How a linked design system reaches a build

Worth knowing because it affects build speed rather than correctness.

If your design system publishes packages to a registry, Taiga installs it like any dependency. That is the fast path, with correct versions and complete type information.

If no registry serves it, Taiga clones the repository and links it from source instead. This produces the same result and every build is slower.

If you are on the slow path and it bothers you, the fix is connecting a package registry, not changing anything about the design system itself.

What this does not do

A linked design system grounds what agents build. It does not enforce it.

Generated interfaces still get reviewed like any other change, and the pull request is where you catch a component used in a way your team would not use it.