Windcraft

Concepts

How tokens, contracts, and rules fit together.

Windcraft is a design coherence layer between your AI coding tool and your project. Three building blocks.

Tokens

W3C Design Tokens stored in cloud, synced to your repo. Edit in the dashboard, run windcraft sync, and your tailwind.config.ts, CSS variables, and React Native theme update together. Every save creates a new version you can restore or diff. Token aliases like {color.brand.primary} resolve at sync time.

Component contracts

Per-component rules describing variants, sizes, slots, and good/bad examples. 77 default contracts across six categories — forms, display, navigation, layout, data, media (Button, Input, Card, Dialog, …). AI tools read them via MCP before generating UI code. Edit any contract from the project's Contracts tab — variants, sizes, slots, rules, code examples.

Page patterns

Whole-page blueprints. 60 default patterns across nine categories — auth, onboarding, billing, dashboard, ecommerce, blog, marketing, errors, realtime. Each carries layout regions, required states, microcopy, and motion specs, seeded per project and editable/toggleable. AI tools query them via the MCP get_page_pattern tool when scaffolding a new page.

Rules

Static checks the analyzer runs on your code. 9 V1 rules (no-hardcoded-color, require-empty-state, accessible-touch-target, pattern-conformance, …). Each rule has a severity you can change per project; exceptions are glob-matched. The CLI persists results to .windcraft/cache.json so unchanged files skip re-parse.


Where things live

In the cloud: tokens, contracts, rules, subscription metadata. Never: your source code.

In your repo:

  • .windcraft/config.json — project bindings, exception list, output paths
  • .windcraft/cache.json — analyzer cache (auto-generated)
  • tailwind.config.ts, app/globals.css, theme.ts, windcraft.types.d.ts — generated outputs
  • .claude/skills/windcraft.md — auto-generated MCP skill bundle

Where API keys go

~/.windcraft/credentials (chmod 600). One project per machine in V1. The CLI reads it for sync, check, and mcp.

2FA

Authenticator-based two-factor auth is available in Settings → Security. Backup codes are single-use and re-generatable.

On this page