Agent handoff

Portable files any agent can read. Patterns for Claude Code, Codex, Cursor, Windsurf, v0, Lovable, and Gemini CLI.

Workflow

Generate ./build-pack/ in your project directory.
Attach pack to agent context (commit, rules, or task paste).
Agent implements from contract — no new visual system.
Run score; agent fixes failed scorecard rows.

Generate pack

npx dzine-skill run "premium product dashboard for creative teams" --write-build-pack

Agent integrations

Agent	Handoff	Reads	Review
Claude Code	Commit pack to repo	DESIGN.md, route.json, tokens	score after first pass
Codex	Task + file context	contract JSON + DESIGN.md	repair from scorecard
Cursor	Project rules / .cursor/skills	build-pack/	lint + score in CI
Windsurf	Rules file	build-pack/	manual score review
v0 / Lovable / Bolt	Paste route + tokens	partial pack	manual scorecard
Gemini CLI	File attachments	Markdown + JSON	browser QA notes

Prompt pattern

Use ./build-pack as the design source of truth.
Read contract/DESIGN.md and contract/route.json first.
Follow forbidden patterns and token constraints.
Implement the page, then run:
  node packages/dzine-skill/bin/dzine-skill.mjs score --contract build-pack/contract/design-contract.json --url <your-dev-url>
Patch every failed scorecard row before final delivery.

What agents must verify

First viewport: product, audience, proof, single primary CTA.
Mobile: intentional layout, not compressed desktop.
States: focus, loading, empty, error where applicable.
Copy: no internal design notes or placeholder SaaS voice.
Scorecard: evidence for each PASS row.

CI integration

Commit build-pack/contract/design-contract.json and run validation in GitHub Actions (see .github/workflows/design-contract.yml). Mirror locally with ./scripts/ci-local.sh.

Optional MCP bridge: MCP docs. Fundamentals: What is DZINE?