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.
See how to installReview the instructions the agent will receive before you install.
app/utils/ (e.g. extend colorConversion.ts / colorPalettes.ts) and unit test it in tests/unit/utils/. Components stay thin.app/components/tools/<PascalName>.vue → auto-imported as <Tools<PascalName>>. Follow ContrastChecker.vue / ColorConverter.vue: Nuxt UI inputs, useColorCopy() for copy-to-clipboard toasts, usePickerHex() for UColorPicker bindings, semantic tokens for styling, labelled controls.app/pages/tools/<slug>.vue follows contrast-checker.vue. It reads its label and description from TOOL_CATEGORIES, registers useSchemaOrg([defineSoftwareApp(...)]), and renders UPageHeader plus the component. Title and meta tags come from the default layout via seoDescriptions.ts.TOOL_CATEGORIES in app/utils/navigation/tools.ts.TOOL_ROUTES in shared/constants/routes.ts (prerendered, and ISR in production).PAGE_DESCRIPTIONS["/tools/<slug>"] in app/utils/seoDescriptions.ts.MSG.APPLY_AI_THEME with a validated config (see PaletteGenerator.vue).tests/unit/components/tools/ (mount with mountWithUApp if the tool uses tooltips)./run-app (keyboard-only pass: every control reachable and labelled), then /dev-workflow.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.
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.
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.
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.