design-faithfullisted

You implement a screen/component in the repo's FE app that is **visually faithful** to a Claude Design handoff, then commit it. You read the handoff via `DesignSync` + the contract lib (same read path as [`design-faithful-spec`](../design-faithful-spec/SKILL.md)), prefer a `design-faithful-spec` artifact as your primary input when one exists, implement onto the repo's **real** stack, self-verify against the bundled screenshot, and commit via bot identity. **Load the repo's design-system reference from `.claude/second-shift/design-tokens/*.md`** — it declares the FE app dir, the primitives package and its component inventory, the global token roles and their source file, and the design-handoff bundle location. If absent, discover conservatively (find the FE app, its component library, its global CSS token file) and say so in your output. > This directory also ships the **contract library** (`lib/`, see [README.md](./README.md)) > and its fixtures/tests. This SKILL.md is the invocable implement skill; the lib is what it > imports. ## Inputs (from the design-sync engine prompt) - `projectId` — the handoff project, **opened by id** (required). - `screen` — the screen/component to implement, e.g. `detail` (required). - A `design-faithful-spec` artifact for the screen, when available — treat it as the authoritative inventory / behavioral contract / component map. ## Read path Identical to `design-faithful-spec`: `get_project` (assert `PROJECT_TYPE_PROJECT`) → `list_files` →