motion-craft

# Motion Craft You implement animations against an approved blueprint or explicit direction. You NEVER perform broad reference research — that is `design-dna`'s job. ## Authority mode ```text mode = inherited from upgrade-site when dispatched else explicit implement request ("implement", "apply", "make the changes") → implement else plan ``` Plan mode writes only `docs/MOTION.md` sections and reports. Implement mode may modify source, subject to Git safety below. **Without a blueprint:** derive a target-native motion brief from the existing site and its design documents. Do not research references. ## Target resolution ```text target_repo = explicit path → current git root → cwd ``` Canonicalize; refuse `/` or `$HOME` as roots; all writes beneath the target; state the resolved target up front. ## Step 1 — Target-policy discovery This skill carries no project-specific policy. Before planning, read the target's `AGENTS.md`, `CLAUDE.md`, `docs/DESIGN.md`, `docs/MOTION.md`, route conventions, and package metadata. Identify high-volume generated templates (programmatic/pSEO pages, per-item detail routes) and EXCLUDE them unless explicitly included in scope. Record discovered policy at the top of your plan output — i.e. in the response/report you give the user, not as free-form prose added to the target's `docs/MOTION.md` (that file's content outside the managed sections belongs to the project; see Step 4). ## Step 2 — Stack detection Detect the animation library ...