turbo-verifylisted

# Verify Theme Implementation Verify that a theme implementation is complete and follows all turbo-themes standards. When asked to verify a theme (e.g., `/turbo-verify rose-pine`), run through the sections below. The `turbo-add` skill holds the full add-time file map and discovery approach — this skill checks the result. ## 1. Discover Touchpoints (do this first) Do not trust a memorized file inventory. Compare the new theme's footprint against a known-complete theme's footprint: ```bash # Pick a known-good variant id from src/themes/registry.ts (e.g. rose-pine-moon) rg -l 'rose-pine-moon' --hidden -g '!node_modules' -g '!dist' | sort > /tmp/ref.txt rg -l '<new-variant-id>' --hidden -g '!node_modules' -g '!dist' | sort > /tmp/new.txt diff /tmp/ref.txt /tmp/new.txt # Family-level touchpoints (type unions, family maps, vendor metadata) diff <(rg -l 'rose-pine' src/ packages/ apps/ scripts/ | sort) \ <(rg -l '<theme>' src/ packages/ apps/ scripts/ | sort) ``` Also verify root-level registrations the greps can miss because they do not mention variant ids: - [ ] `theme:sync` script wiring in `package.json` - [ ] Size limits in `test/integration/bundle-size.test.ts` Every file present only in the reference list is a likely missing touchpoint. Exclude files that auto-derive from core (imports from `@lgtm-hq/turbo-themes-core/tokens`) and generated artifacts (rebuild instead). ## 2. Core Implementation ### Theme Pack (`src/themes/packs/<theme>.synced.ts` or `<theme>