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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Audit websites for SEO, performance, security, technical, content, and 15 other issue cateories with 230+ rules using the squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use to discover and asses website or webapp issues and health.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。