Ghost

Ghost turns implemented UI into a repo-local design-language file agents can use.

Agents can ship UI now. What slips is taste: palette, density, hierarchy, and the small choices that make a product feel like itself. Most repos do not have a clear, local answer to “what should this interface look like?”

Ghost gives the repo that answer. It scans the UI already in the codebase and writes fingerprint.md: a readable design-language file that lives beside the code. Agents read it before generating UI and check against it after they make changes.

The scan earns that file with evidence:

• map.md tells Ghost where to look.
• survey.json records the values, tokens, components, and surfaces it found.
• fingerprint.md explains what those values mean as a design language.

Your agent does the judgment work. Ghost's CLIs handle the repeatable checks: validation, profile verification, diffs, comparisons, and fleet views.

Works with your agent

Every Ghost workflow runs in the host agent you already use: Claude Code, Codex, Cursor, Goose, or another agent. Each tool ships an agentskills.io-compatible recipe bundle for work like scan, review, verify, remediate, or summarize a fleet. The agent reads the files, makes the calls, and writes the outputs. When it needs a reproducible answer, such as schema validation or fingerprint distance, it calls a Ghost CLI.

No API key is required to run any CLI verb. Each tool's emit skill verb installs its bundle into your agent.

Why Ghost?

Ghost gives agents a few practical abilities:

• Generate from a local file: fingerprint.md tells the agent what the design language is before it writes UI.
• Review changes for drift: the review and verify recipes compare generated or changed UI against the fingerprint.
• Compare systems: ghost-drift compare and ghost-fleet view show how fingerprints differ across projects.
• Record intent: ack, track, and diverge record whether drift is accepted, tracked against a new reference, or intentionally different.
• Stay readable: fingerprint.md is Markdown with YAML frontmatter. Humans can review it, agents can use it, and the CLIs can validate and diff it.

Tools around the loop

Ghost is split into focused tools. The common path is simple:

map.md -> survey.json -> fingerprint.md -> design review

Tool	Job	Verbs
ghost-fingerprint	Create and check map.md, survey.json, and fingerprint.md.	inventory, lint, verify-profile, describe, diff, survey <op>, emit
ghost-drift	Compare fingerprints, review UI drift, and record what changed intentionally.	compare, ack, track, diverge, emit skill
ghost-fleet	See how many project fingerprints relate.	members, view, emit skill
ghost-ui	Reference design system Ghost dogfoods — 97 shadcn components + an MCP server.	(no verbs)

Scans describe one subject, but they can read more than one source. For example, an app can read tokens from an upstream design-system package while still producing a fingerprint about the app's actual UI.

@ghost/core underneath is a workspace-only library with embedding math, target resolution, skill-bundle loader, and the ghost.map/v2 + ghost.survey/v2 schemas the three CLIs share.

Repo layout

Ghost is a pnpm monorepo. Four tools, one reference design system, one docs site.

Path	Role	Published?
packages/ghost-core	Workspace-only shared library — embedding math, target resolver, skill loader, ghost.map/v2 + ghost.survey/v2 schemas.	❌ private (@ghost/core)
packages/ghost-fingerprint	The three-stage scan pipeline: map.md → survey.json → fingerprint.md. Authoring, lint, profile verification, describe, diff, survey ops, emit.	✅ intended-public on npm
packages/ghost-drift	Drift detection and stance verbs.	✅ ghost-drift on npm
packages/ghost-fleet	Fleet view across many members.	❌ private
packages/ghost-ui	Reference design system: 97 shadcn components + the ghost-mcp MCP server.	❌ private (distributed via shadcn registry, not npm)
apps/docs	Deployed docs site (ghost-docs).	❌ private

Dependency flow: @ghost/core ← everyone. ghost-fingerprint ← ghost-drift, ghost-fleet. No cycles.

Quick install

If you just want the design-language scan + emit recipes installed into your host agent — no Node, no pnpm, no build:

curl -fsSL https://raw.githubusercontent.com/block/ghost/main/install/install.sh | sh

The installer detects your agent (claude / cursor / codex / opencode), drops the ghost skill bundle into the right skills directory (e.g. ~/.claude/skills/ghost/), and tells you what to do next. Pass --agent claude (or --dest <path>) to override detection. Re-run with --force to upgrade.

After install, in any repo:

> Scan this project with ghost

The agent walks map.md → survey.json → fingerprint.md, then emits a /design-review slash command tuned to your design language. The recipes work without any Ghost CLI on PATH — every CLI-using step has a prose fallback.

If you want the CLI helpers for linting, profile verification, diffing, comparing, and fleet views, install from source instead. See Getting Started below.

Getting Started

Prerequisites

• Node.js 18+
• pnpm 10+

Install

pnpm install
pnpm build

Install the skill bundles into your host agent

Each tool ships its own bundle. Install whichever you need.

ghost-drift emit skill            # → ./.claude/skills/ghost-drift
ghost-fingerprint emit skill       # → ./.claude/skills/ghost-fingerprint
ghost-fleet emit skill            # → ./.claude/skills/ghost-fleet

Once a skill is installed, ask your agent in plain English ("profile this design language", "review this PR for drift", "compute the fleet view") and it'll follow the recipe, calling the relevant CLI whenever it needs a reproducible answer.

Quick start

1. Map the repo (the first checkpoint before survey and profile). Ask your host agent to write map.md, then validate:

ghost-fingerprint inventory      # raw signals as JSON (the agent reads this to author map.md)
ghost-fingerprint lint map.md    # validate ./map.md against ghost.map/v2

2. Survey the design values (the observed evidence stage). Ask your host agent to write survey.json, then validate:

ghost-fingerprint survey fix-ids survey.json -o survey.json
ghost-fingerprint lint survey.json

3. Profile your design system — ask your host agent to write fingerprint.md. It'll follow the profile recipe and validate at the end. You validate manually with:

ghost-fingerprint lint                                   # defaults to ./fingerprint.md
ghost-fingerprint verify-profile fingerprint.md survey.json --root .
ghost-fingerprint lint path/to/fingerprint.md --format json

4. Compare fingerprints:

# Pairwise: per-dimension distance
ghost-drift compare market.fingerprint.md dashboard.fingerprint.md

# Add qualitative interpretation of decisions + palette
ghost-drift compare a.md b.md --semantic

# Add velocity / trajectory (reads .ghost/history.jsonl)
ghost-drift compare before.md after.md --temporal

# Composite (N≥3): pairwise matrix, centroid, clusters — the org fingerprint
ghost-drift compare *.fingerprint.md

5. Track intent toward another fingerprint:

ghost-drift ack --stance aligned --reason "Initial baseline"
ghost-drift track new-tracked.fingerprint.md
ghost-drift diverge typography --reason "Editorial product uses a different type scale"

6. Emit derived outputs (these all live in ghost-fingerprint now — they read your fingerprint.md):

ghost-fingerprint emit review-command     # .claude/commands/design-review.md (per-project slash command)
ghost-fingerprint emit context-bundle     # ghost-context/ (SKILL.md + fingerprint.md + prompt.md + tokens.css)
ghost-fingerprint emit skill              # .claude/skills/ghost-fingerprint (the agentskills.io bundle)

7. View a fleet (when you have ≥2 members each with their own map.md and fingerprint.md):

ghost-fleet members ./fleet     # list registered members + freshness
ghost-fleet view ./fleet         # emit fleet.md + fleet.json with pairwise matrix, centroid, clusters

Run the docs site locally:

just dev
# or: pnpm -F ghost-docs dev

CLI Commands

Commands are grouped by the tool that owns the file. Pure inputs → pure outputs, no API key required.

Tool	Command	Description
ghost-fingerprint	inventory	Emit raw repo signals (manifests, language histogram, registry presence, top-level tree, git remote) as JSON. Feeds the map recipe.
ghost-fingerprint	lint	Validate file shape for fingerprint.md, map.md, or survey.json — auto-detects by extension/content.
ghost-fingerprint	verify-profile	Validate fingerprint-to-survey fidelity after profiling; palette, spacing, typography, radii, and shadow posture must be survey-backed, and promoted checks must be calibrated.
ghost-fingerprint	describe	Print section ranges + token estimates so agents can selectively load.
ghost-fingerprint	diff	Structural prose-level diff between two fingerprints (NOT vector distance — for that, use ghost-drift compare).
ghost-fingerprint	survey <op>	Operate on ghost.survey/v2 files. Ops: merge, fix-ids, summarize, catalog.
ghost-fingerprint	emit	Derive an output from fingerprint.md: review-command, context-bundle, or skill.
ghost-drift	compare	Pairwise (N=2) or composite (N≥3) over runtime fingerprint embeddings. --semantic / --temporal add qualitative enrichment.
ghost-drift	ack	Record stance toward the tracked fingerprint in .ghost-sync.json.
ghost-drift	track	Shift the tracked fingerprint.
ghost-drift	diverge	Declare intentional divergence on a dimension.
ghost-drift	emit skill	Install the ghost-drift agentskills.io bundle.
ghost-fleet	members	List registered fleet members + freshness.
ghost-fleet	view	Compute pairwise distances + group-by tables; emit fleet.md + fleet.json.
ghost-fleet	emit skill	Install the ghost-fleet agentskills.io bundle.

Skill recipes: run by the host agent

The interpretive work is done by recipes the agent runs. Install the relevant bundle once, then ask in plain English. Each tool ships its own recipes.

Recipe	Bundle	Capability	Triggered by
map	ghost-fingerprint	Write the repo map (stage 1)	"map this repo", "write map.md"
survey	ghost-fingerprint	Author the survey of values (stage 2)	"survey design values", "extract design tokens"
profile	ghost-fingerprint	Author the design language (stage 3)	"profile this design language", "write fingerprint.md"
review	ghost-drift	Review PR changes for drift	"review this PR for drift"
verify	ghost-drift	Check generated UI against the fingerprint	"verify generated UI against the fingerprint"
compare	ghost-drift	Compare fingerprints	"why did these two fingerprints drift?"
remediate	ghost-drift	Suggest minimal fixes for drift	"fix this drift"
target	ghost-fleet	Synthesize fleet narrative	"describe this fleet"

These are instructions, not code. The agent executes them using its normal tools (file search, reading, editing) plus the relevant Ghost CLI when it needs a reproducible answer. (discover and generate are intentionally not migrated — see docs/ideas/phase-0-decisions.md.)

Configuration

ghost.config.ts is optional — only ghost-drift ack and ghost-drift diverge consult it (to locate the tracked fingerprint). Everything else is zero-config.

Environment variables

• OPENAI_API_KEY / VOYAGE_API_KEY: optional, consumed by computeSemanticEmbedding (a @ghost/core library function) when a host wants enriched semantic comparison.
• GITHUB_TOKEN: optional, used by resolveTrackedFingerprint when fetching a tracked fingerprint from GitHub (avoids rate limits).

Each CLI auto-loads .env and .env.local from the working directory.

How It Works

The fingerprint

What the agent reads when it writes or reviews UI. The main file is fingerprint.md (owned by ghost-fingerprint): Markdown with YAML frontmatter plus a prose body.

• Frontmatter: references, palette, spacing, typography, surfaces, and promoted checks[].
• # Character: what the design language feels like.
• # Signature: what output should look like when the language comes together.
• # Decisions: the important design choices, with evidence. Runtime comparison computes embeddings from this file; no authored embedding file is needed.

Generate one with the profile recipe (in the ghost-fingerprint skill bundle). See docs/fingerprint-format.md for the full spec.

The map

What Ghost uses during scan and fleet workflows to understand the repo. map.md is stage 1 of a scan. It records languages, build system, package manifests, registry files, design-system paths, observable surfaces, and feature areas. Generation and drift review start from fingerprint.md, not map.md.

Generate one with the map recipe (in the ghost-fingerprint skill bundle). The agent reads ghost-fingerprint inventory (raw repo signals as JSON) and writes the short body.

Author + Review Loop

The loop is simple: the agent writes UI, the review or verify recipe checks it against fingerprint.md, and a human or agent decides what to do next. Fix the drift, accept it, track a new fingerprint, or mark one dimension as intentionally different. See docs/generation-loop.md for details.

Remediation

Three files record what happened:

• fingerprint.md: The design-language contract.
• .ghost-sync.json: Per-dimension stances toward the tracked fingerprint (aligned, accepted, or diverging), each with recorded reasoning. Written by ghost-drift ack / track / diverge.
• .ghost/history.jsonl: Append-only fingerprint history for temporal analysis. Read by ghost-drift compare --temporal.

Org-scale observability

To look across many projects:

• Many fingerprints, no map: run ghost-drift compare with three or more fingerprint.md files. It returns pairwise distances, a centroid, and similarity clusters.
• A registered fleet (members each with map.md + fingerprint.md): run ghost-fleet view. It adds groupings such as platform, build system, and design-system status.

Project Resources

Resource	Description
CODEOWNERS	Project lead(s)
CONTRIBUTING.md	How to contribute
GOVERNANCE.md	Project governance
LICENSE	Apache License, Version 2.0