fix(skill): all file paths use capture/ subfolder prefix (#345)

* fix(skill): all file paths use capture/ subfolder prefix

Step-1 was updated to capture into <project-dir>/capture/ but all
file-read instructions across steps 1-6 still used bare paths
(extracted/tokens.json, assets/hero.png). Agents following the skill
looked for files in wrong locations, producing broken compositions
with 404'd images and fonts.

- step-1: all 12+ file-read paths prefixed with capture/
- step-2: tokens.json and asset-descriptions.md paths fixed
- step-3: visible-text.txt path fixed
- step-4: asset-descriptions.md, asset examples, directory tree expanded
  to show capture/ children (screenshots/, assets/, extracted/)
- step-5: minor cleanup
- step-6: asset-descriptions.md path fixed, composition examples already
  correct (../capture/assets/)
- techniques.md: Lottie, video, font paths all prefixed

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(skill): address Copilot review — font comment path, add videos/ to tree

- techniques.md: comment says ../capture/assets/fonts/ (matches composition context)
- step-4 file tree: add videos/ under capture/assets/

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ular Kimsanov
2026-04-20 05:01:25 +02:00
committed by GitHub
co-authored by Claude Opus 4.7
parent 479e6c3f81
commit a78ec5ec76
7 changed files with 49 additions and 34 deletions
@@ -12,7 +12,7 @@ DESIGN.md is NOT the creative plan. The STORYBOARD (Step 4) drives creative dire
### `## Colors`
5-10 key colors with HEX values from tokens.json and their roles:
5-10 key colors with HEX values from `capture/extracted/tokens.json` and their roles:
```
- **Primary Surface**: `#020204` — deep black background
@@ -65,11 +65,11 @@ For each, note the distinctive visual treatment (border-radius, spacing, hover b
## Rules
- Use **exact HEX values** from tokens.json. Do not approximate.
- Use **exact HEX values** from `capture/extracted/tokens.json`. Do not approximate.
- Name components by what you see in the screenshot, not generic terms.
- Keep it under 100 lines. This is a cheat sheet, not a design system document.
- No "Style Prompt" section — the storyboard handles creative direction.
- No "Assets" section — `asset-descriptions.md` already covers this.
- No "Assets" section — `capture/extracted/asset-descriptions.md` already covers this.
- No "Motion" section — the storyboard specifies motion per-beat.
## Example