Integration
Bolt scaffolds fast. Windcraft keeps the design from scattering.
Bolt is great at standing up a whole project in the browser from a single prompt. The speed hides a cost: every generated view picks its own spacing and color. Windcraft reconciles that code with your design system after you pull it down.
Why Bolt-generated UI scatters
Bolt runs in an in-browser environment and generates from prompts, with no connection to your repo’s tokens. Each view it scaffolds is internally clean but externally inconsistent — a button here is rounded-lg, there it is rounded-md; one card pads 16px, the next 20px. Nothing reads a shared source, so the design scatters as the project fills out.
How Windcraft aligns Bolt output
Bolt has no local MCP server to integrate with, so Windcraft works on the output. Pull the Bolt project into your repo and the CLI checks the generated UI against your tokens and contracts, auto-fixes the safe drift, and keeps your generated theme files canonical.
- Download or push the Bolt project into your repo.
- Run npx windcraft check to list off-token colors, radii, and spacing.
- Run npx windcraft check --fix to snap the easy ones to your tokens.
- Run npx windcraft sync to keep tailwind.config.ts and tokens.css as the source of truth.
Align a Bolt project to your tokens
# with the Bolt project pulled into your repo
npx windcraft check
npx windcraft check --fixFAQ
- Does Windcraft run inside Bolt?
- No. Bolt generates in its own in-browser environment and does not run a local MCP server. Windcraft runs against the code once it is in your repo, so there is nothing to install on the Bolt side.
- What does Windcraft add on top of Bolt?
- Consistency the prompt cannot guarantee. Bolt gives you a working scaffold; Windcraft makes every view in it read the same tokens and respect the same component contracts.
- Is my source uploaded anywhere?
- No. Analysis is local. Only tokens, contracts, and rule violations — metadata, never your source — are synced to the cloud.