Shippp

List a Shippp file's screens and master components (id + name). Call this FIRST to discover the ids for shippp_get_component.

Get ONE component's deterministic Chakra UI code + a reproducibility receipt. `unitType` is 'master' (a design-system component) or 'screen' (a depth-0 artboard). Get ids from shippp_list_units.

Get the design system's tokens as a Chakra theme (createSystem) + receipt.

Get the whole design system as a publishable package (tokens + theme + recipes + every component + stories + package.json).

Get the whole file as a runnable Next.js project (screens as pages + the design system).

Diff your CURRENT code against a fresh deterministic generation of a unit — shows exactly what a designer changed. Pass the same unit params as the get tools, plus `baseline` (the files you currently have for that unit).

Preview the repository's Shippp sync as a deterministic plan — NO writes. The repo root comes from the developer's own configuration (SHIPPP_REPO_ROOT env, or the server's working directory), never from tool input. Requires a committed shippp.target.json binding (created via shippp_bind_repository on the remote MCP). Returns the create/update/delete entries, hand-modified-file conflicts and any pending compiler/IR/adapter delta that shippp_sync_apply would need explicit approval for.

無需輸入參數。

Run the full repository sync with the bundled deterministic runner: fetch the bound unit's artifact, plan against the real on-disk state, apply atomically with rollback, run the repo's checks (SHIPPP_SYNC_CHECKS env), and write the receipt ONLY on full success. Writes are confined to the generated root of the repo's own binding; hand-modified generated files are structured conflicts and are never overwritten. If the plan or a refusal reports a compilerDelta, present it to the user and re-call with approvedCompilerDelta set to EXACTLY those lines ONLY after their explicit approval. After an approved re-bind, pass acceptReboundBaseline to adopt the previous binding's receipt as baseline.