turbo-verify
Skill1 starsChanged 12 days agoMITView on GitHub
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. Do not trust a memorized file inventory. Compare the new theme's footprint against a known-complete theme's footprint: Also verify root-level registrations the greps can miss because they do not mention variant ids: Every file present only…
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- which-prSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Verify that a theme implementation is complete and follows all turbo-themes standards.
- Distinctive: line 17
Do not trust a memorized file inventory.
- Very specific: line 37
Every file present only in the reference list is a likely missing touchpoint.
- Distinctive: line 114
Use the section-1 diff to enumerate example files.
- Distinctive: line 135
Visual regression note: if E2E visual tests fail after adding themes to the hero strip, that is expected — snapshots are generated on Linux …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
# 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:syncscript wiring inpackage.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>.ts)
- Exports a
ThemePackagewithid,name,homepage,license(spdx/url/copyright, recommended),source(package/version/repository, recommended for synced), andflavors - Each flavor has
id(lowercase-hyphenated),label(full display name, e.g. "Gruvbox Dark Hard"),vendor(matches family),appearance(light/dark), and completetokens - No
iconUrlin flavor definitions (icons resolve viaVENDOR_ICON_MAP)
Required Token Groups
background— base, surface, overlaytext— primary, secondary, inversebrand— primarystate— info, success, warning, dangerborder— defaultaccent— linktypography— fonts (sans, mono), webFontscontent— heading (h1-h6), body, link, selection, blockquote, codeInline, codeBlock, table
Registry, Tokens, Icons
- Theme imported in
src/themes/registry.ts, flavors spread intoallFlavors - W3C token JSON per variant in
schema/tokens/themes/<variant-id>.tokens.json($value/$typeformat,$schema→../../turbo-themes.schema.json#/$defs/ThemeFile) - PNG icon per variant in
assets/img/<variant-id>.png(typically 24x24)
3. Theme Selector Package
ThemeFamilytype union includes the family (packages/theme-selector/src/types.ts)THEME_FAMILIEShas name + description (packages/theme-selector/src/constants.ts)VENDOR_FAMILY_MAPandVENDOR_ICON_MAPupdated;FLAVOR_DESCRIPTIONShas an entry per variant (packages/theme-selector/src/theme-mapper.ts)
4. Site Integration
apps/site/src/data/theme-meta.ts is the single source of truth for the
site. BaseLayout.astro and ThemeDropdown.astro are data-driven from it —
never hand-edit theme lists in those files.
- Theme group in
themeGroups(id, displayName, flavors) - All variants in
themeNameswith short labels (e.g., "Mocha" — shorter than the tokenlabel) - All variants in
themeIconswith icon filenames validThemeIdsauto-derives — verify the count matches the expected totalThemeDropdown.astroandBaseLayout.astrostill import fromtheme-meta.ts(no hardcoded theme arrays crept back in)- Theme family in the
themes.astrosidebar (header with icon/name/count, button per variant) and in its JSthemeNamesobject - Hero preview strip buttons added in
index.astro
5. Build Pipeline
- If synced: script in
theme:sync(package.json), output path issrc/themes/packs/(NOTpackages/core/...), version read fromnode_modules/<pkg>/package.jsonintosource.version, and the build succeeds from a clean state (delete the.synced.tsfile, runbun run build, confirm it regenerates) vendorMetainscripts/prepare-style-dictionary.mjshas correct name/homepage; generatedtokens.jsonfiles show them- Generated assets rebuilt and committed — discover them with
git statusafterbun run build(theme-selector JS bundles,tokens.jsonin core/python/swift trees)
6. Examples
Use the section-1 diff to enumerate example files. Then confirm, per hit:
- Web examples: new variants in
<select>options andVALID_THEMES/LIGHT_THEMES/THEMESarrays (FOUC and main scripts) - Files that import from
@lgtm-hq/turbo-themes-core/tokenswere NOT hand-edited (they auto-update) - Swift example:
ThemeId.swiftenum cases,ThemeRegistry.swiftThemeDefinitionpalettes,ThemeRegistryTests.swiftcounts, labels, and raw values
7. Build Verification
uv run lintro chk # Expected: 0 issues (run first for fast failure)
bun run build # Expected: "Build complete!" with new theme count
bun run examples:build # Expected: all example projects build
bun run test # Expected: all unit tests pass
bun run examples:test # Expected: all example E2E tests pass
cd apps/site && bun run build # Expected: no errorsVisual regression note: if E2E visual tests fail after adding themes to the
hero strip, that is expected — snapshots are generated on Linux CI. Run the
maintenance-generate-snapshots.yml workflow (Actions → Maintenance: Generate
Playwright Snapshots → Run workflow).
8. Functional Testing
- Theme appears in the header dropdown under the correct family group
- Selecting it updates page styling; header shows the correct icon and short label (not the id or full name)
- Theme persists across refresh and page navigation (no revert to default)
- Explorer page: family in sidebar, all variants selectable, palette and live preview render per variant
- CSS file generated per variant; CSS variables set when applied
Quick Fix Reference
| Issue | Solution |
| Theme reverts on navigation | Add variants to themeGroups in theme-meta.ts |
| Wrong/missing header label | Fix themeNames in theme-meta.ts |
| Missing icon | Fix themeIcons in theme-meta.ts + add PNG |
| Theme in wrong group | Fix VENDOR_FAMILY_MAP in theme-mapper.ts |
| Theme not appearing | Check ThemeFamily type, THEME_FAMILIES constant |
| Tests fail on theme order | Use data-theme-id lookups, not array indices |
| Bundle too large | Review asset diff; raise bundle budget if intentional |
| CI "Cannot find module" | Add sync script to theme:sync in package.json |
| tokens.json wrong metadata | Add to vendorMeta in prepare-style-dictionary.mjs |
| Generated assets outdated | Run bun run build and commit generated files |
| Missing descriptions | Add to FLAVOR_DESCRIPTIONS in theme-mapper.ts |
| Sync writes to wrong path | Change outPath to src/themes/packs/ |
| Visual regression fails | Run maintenance-generate-snapshots.yml workflow |
| Missing from examples/Swift | Re-run the section-1 diff and fill the gaps |
Review Output Format
## Theme Review: <theme_name>
### Status: PASS / FAIL / PARTIAL
### Checklist Summary
- Discovery diff: clean / N missing files
- Core Implementation: X/Y items
- Theme Selector Package: X/Y items
- Site Integration: X/Y items
- Build Pipeline & Examples: X/Y items
- Build Verification: X/Y items
- Functional Testing: X/Y items
### Missing Items
1. [item]
### Recommendations
1. [recommendation]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

