Command reference

Complete reference for the open-source CLI — init, compile, run, lint, score, repair, doctor, MCP, and gallery QA.

Core commands

Command	Description
init --target <host>	Install DZINE skill for cursor, codex, claude, or hermes
doctor	Check Node, Python, npm, and skill path
run <brief> --write-build-pack	Compile brief + write ./build-pack/ in cwd
compile <brief> --json	Compile route recommendation as JSON
qa --url <url>	Browser health check for a preview URL
gallery-qa	QA the preview gallery (port 3002)

Most common

npx dzine-skill run "premium marketplace for independent artists" --write-build-pack

Contract tools

Compile contract

npx dzine-skill compile "enterprise trust center" --contract --out dzine-pack

Validate

npx dzine-skill validate dzine-pack/design-contract.json

Lint

npx dzine-skill lint dzine-pack/design-contract.json

Render pack views

npx dzine-skill render dzine-pack/design-contract.json --out-dir dzine-pack/rendered

QA

Score URL (structural v0)

npx dzine-skill score --contract dzine-pack/design-contract.json --url http://localhost:3003 --out dzine-pack/score-report.json

Score URL (strict + browser preflight)

npx dzine-skill score --contract dzine-pack/design-contract.json --url http://localhost:3003 --strict --out dzine-pack/score-report.json

Repair prompt

npx dzine-skill repair --contract dzine-pack/design-contract.json --scorecard dzine-pack/score-report.json --out dzine-pack/repair-prompt.md

Score compares implementation HTML against contract clause paths. Repair generates instructions only for failed rows.

All commands

npx dzine-skill help

init [--target cursor|codex|claude|hermes]
doctor
compile <brief> [--contract] [--out dir|file.json] [--json]
render <contract> [--out-dir dir]
validate <contract>
lint <contract>
score --contract <file> --url <url> [--out file]
repair --contract <file> --scorecard <file> [--out file]
run <brief> [--url http://localhost:3003] [--write-build-pack] [--skip-url]
qa --url <url>
gallery-qa [--url http://localhost:3002]
mcp
api

Tips

Run from your app directory so --write-build-pack writes beside your code.
Use concrete briefs — product type, audience, proof, primary action.
Regenerate when strategy changes; patch implementation for spacing and copy tweaks.
Commit packs with your repo so CI and agents share the same contract version.