Checklist for adding or changing a field on ThemeConfig (a new design token, per-mode setting, or export option) end to end — schema, defaults, store + history, CSS apply, export, editor UI, AI, and tests. Use whenever ThemeConfig's shape changes.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
ThemeConfig is persisted in users' cookies, stored in saved presets, exported as JSON, generated by AI, and synced into the preview iframe. A change must work for all of them, including old data that lacks the new field.
Work through every step. Say explicitly when a step doesn't apply.
shared/constants/theme.ts so app, server, and AI prompt share it.app/types/theme.ts): add the field to ThemeConfig. In rawThemeSchema, make it .optional() and fill it in ThemeConfigSchema.transform() (usually mirroring the light-mode value for dark* fields). Existing cookies and presets must still parse.app/utils/defaults.ts): add the value to DEFAULT_THEME (and to the light/dark override defaults if it's a token override).app/utils/presets.ts): built-in presets are full configs, so either add the field to each preset or rely on the schema transform, and make sure loadPreset still validates.app/stores/theme.ts): add a setXForMode(mode, value) setter that mutates config.value then calls _pushHistory(). Continuous inputs (sliders, drags) also get a visual setter without history, committed once at the end. Add it to the returned API.app/composables/useThemeApply.ts → app/utils/cssGenerator.ts): semantic palette names go to appConfig.ui.colors; everything else is a CSS variable in :root / .dark. Output must still pass isCleanCSS; sanitize free-form values with sanitizeCSSValue.app/composables/useThemeExport.ts, generateExportCSS): include the property in the CSS and app-config output where relevant (JSON export is automatic).app/components/editor/): a leaf control taking modelValue and emitting updates, wired in EditorPanel via useThemeModeAccessors so it edits the current color mode.aiThemeSchema in server/api/ai/generate.post.ts, buildThemeConfig in server/utils/aiResponseBuilder.ts, and describe it in server/utils/aiSystemPrompt.ts (value lists come from shared constants).app/data/help.md and any learn article describing the editor's controls.tests/unit/types/theme.test.ts: the schema accepts old configs without the field and fills the default.tests/unit/stores/theme.test.ts: the setter updates the right mode, pushes history, and undo/redo work.tests/unit/utils/cssGenerator.test.ts / useThemeExport.test.ts: the variable/export output./dev-workflow full, then check the preview updates live and survives a reload (/run-app).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add, update, or retire an AI provider model option for the BYOK theme generator (OpenAI, Anthropic, Google) and verify the provider requests native structured output for it. Use when model lists go stale or a new provider/model is requested.
The English summary is being prepared. Showing the original description.
Add a new interactive design tool under /tools (like the color converter or contrast checker) — component, page, navigation, route lists, SEO, and tests. Use when building a new utility tool.
The English summary is being prepared. Showing the original description.
Write and register a new Learning Hub article (Nuxt Content markdown under content/learn) with valid frontmatter, navigation entry, route list entry, and accurate product details. Use when adding or substantially rewriting a learn guide, reference, or tip.
The English summary is being prepared. Showing the original description.
Add a new component showcase, block, or template preview page and register it everywhere it must appear (navigation, command palette, route lists, SEO, source view). Use when adding anything under /components, /blocks, or /templates.
The English summary is being prepared. Showing the original description.
Run the project's validation pipeline (lint → format → typecheck → unit tests) with auto-fixes, then optionally stage and write a Conventional Commit. Use before committing, when asked to "check", "validate", "run the workflow", or "get this commit-ready".
The English summary is being prepared. Showing the original description.
Audit the project's documentation (CLAUDE.md, .claude/rules, skills, README, CONTRIBUTING, SECURITY, .env.example, app/data/*.md, learn articles) against the actual code and config, and fix drift. Use after refactors, dependency or workflow changes, or on a schedule.
The English summary is being prepared. Showing the original description.