Integration
Kiro builds from the spec. Windcraft makes the spec design-aware.
Kiro turns a spec into an implementation, agentically. A spec captures behavior well; it rarely pins down your exact radii and color ramp. Windcraft gives Kiro a local MCP server so the design values are read from a source, not inferred from the spec.
Why spec-driven builds still drift on design
A Kiro spec is precise about what to build — the flows, the acceptance criteria — but design values live below that altitude. "A settings page with a save button" does not encode your button radius or your surface color, so the agent fills those in from priors. Two specs implemented on two days yield two slightly different looks, because the spec governed behavior and left the visual language to the model.
How Windcraft plugs into Kiro
Kiro reads MCP servers from its settings. Add Windcraft and the agent can fetch your tokens, contracts, and patterns while executing a spec, so the implementation is design-aware without you writing values into every spec.
- Run npx windcraft init in your repo to generate the config.
- Add the Windcraft server to .kiro/settings/mcp.json.
- Kiro calls the design tools as it implements a spec.
- Run npx windcraft check to flag any drift before you commit.
Kiro MCP config (.kiro/settings/mcp.json)
{
"mcpServers": {
"windcraft": {
"command": "npx",
"args": ["windcraft", "mcp"]
}
}
}FAQ
- Should design values go in the spec or in Windcraft?
- In Windcraft. Keep specs about behavior and acceptance criteria; let Windcraft own the measurable design language. The agent reads tokens and contracts over MCP while implementing, so you do not repeat hex values across every spec.
- Does it work with Kiro’s hooks and steering?
- Yes. Steering files stay prose for conventions; Windcraft supplies the machine-readable values alongside them. They are complementary — one shapes intent, the other supplies exact design data.
- Does my source code leave my machine?
- No. The MCP server and analyzer run locally. Only metadata — tokens, contracts, rule violations — is synced to the cloud.