Stop asking agents to write DOM.

Agents emit IntentBundle JSON. Start with viewspec prove --out .viewspec-proof and read .viewspec-proof/PROOF.md; keep .viewspec-proof/support_bundle.json for redacted failure triage. Or scaffold with viewspec init-intent when useful, then run viewspec validate-intent, viewspec compile, and viewspec check locally so ViewSpec owns renderer output, DESIGN.md theming, and deterministic provenance before hosted API work enters the picture.

See the proof
Hosted compiler preview initializing
Compile live ms
Runtime LLM zero
IR nodes —
Tokens —
IntentBundle JSON input 
Loading intent bundle...
HTML / Tailwind
pre-baked

pre-baked

Other surfaces 
Loading source...

The hosted compiler proof remains available for IntentBundle and cross-platform emitter workflows.

Provenance hover anything

Every element traces back to its source data binding. Hover anything. See the chain.

Style derivation idle

Same structure. Different feel. The compiler treats visual style as a function of intent — toggle a preset, the IR doesn't change.

Clean, neutral, the reference compiler baseline.

Same data, different intent idle

Same KPI bindings. One field changes. The compiler picks the structure: cards, rows, or a side-by-side comparison.

Dashboard cards. Focal value gets the largest scale, badge sits beneath, focal card lifted.

Agent writes intent viewspec.intent.json validate + compile local manifest + artifact no autofetch Check hashes Diagnostics → regenerate IntentBundle or edit DESIGN.md → recompile locally

Start with the agent-native contract: run viewspec prove --out .viewspec-proof, read .viewspec-proof/PROOF.md, keep .viewspec-proof/support_bundle.json for redacted failure triage, then run viewspec validate-intent, viewspec compile, and viewspec check. Raw HTML tools stay available for importing existing HTML.

ViewSpec prove is not pixel-perfect visual regression, accessibility certification, arbitrary host-app certification, or hosted compiler publish automation.

IntentBundle workflow Claude Code local instructions IntentBundle schema Proof bundle guide OpenAPI

Free $0/mo

Build on it before you pay for it.

  • Offline Python SDK with compile, lift, diff, and check
  • Local DESIGN.md theming for governed HTML
  • 500 hosted compile calls/day
  • No signup required
Install SDK
Pro $149/mo

Your brand. Four surfaces. Ship cross-platform.

  • All four surfaces (+ SwiftUI, Flutter)
  • DESIGN.md theming (bring your brand)
  • 5 custom motif instances per compile
  • 10,000 hosted compile calls/day
  • Interactive compose (inputs, rules, actions)
Get Pro
Enterprise Custom

Your motif library. Your governance.

  • Unlimited custom motifs
  • Org-wide motif sharing
  • Volume pricing
  • Support + roadmap alignment
Talk to us

Builds with

  • DESIGN.md — Google's open-source design-markdown convention. ViewSpec parses it as the brand input format.
  • Optional reference grounding — agents must not call remote reference libraries by default; user-approved or repo-configured sources may inform IntentBundle structure without changing the local no-network compiler contract.
  • Pretext — Chenglou's text-layout engine. Renders the headline typography you're reading.

Three different roles. Three different relationships. Each acknowledged where it actually plays.