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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Preview pages render inside the editor's iframe (?preview, preview layout) and must respond to the theme being edited. Use Nuxt UI components and semantic tokens (bg-(--ui-bg-elevated), text-(--ui-text-muted), color="primary"), never raw palette classes like bg-blue-500.
Component showcase (/components/<slug>, data-driven via app/pages/components/[slug].vue):
app/components/showcase/components/<PascalSlug>.vue. It's resolved by import.meta.glob from the kebab-case slug. Reuse ShowcaseSpecimen / ShowcaseSpecimenGrid like the existing showcases.COMPONENT_CATEGORIES in app/utils/navigation/components.ts (label, icon, description, to: "/components/<slug>").Block (/blocks/<slug>, data-driven via app/pages/blocks/[slug].vue):
app/components/blocks/components/<Name>.vue. Each block page is app/components/blocks/content/<PascalSlug>.vue, fed by app/data/blocks/<slug>.ts, which imports every variant and its ?raw source (shown in the block's code view) plus an AI prompt.BLOCK_CATEGORIES in app/utils/navigation/blocks.ts.Template (/templates/<slug>):
app/pages/templates/<slug>.vue as a full, self-contained page (users copy this file from the source view, so keep it clean and idiomatic). Don't use definePageMeta({ layout }); app.vue picks layouts.TEMPLATE_CATEGORIES in app/utils/navigation/templates.ts.modules/source-code-embed.ts. Restart pnpm dev to refresh the embedded map.shared/constants/routes.ts: add the path to COMPONENT_ROUTES / BLOCK_ROUTES / TEMPLATE_ROUTES. These drive the sitemap, prerendering, and noindex. tests/unit/shared/routes.test.ts fails if nav and route lists disagree.app/utils/seoDescriptions.ts: add a PAGE_DESCRIPTIONS entry (and PAGE_TITLES if the generic "<Label> Component/Block/Template" title isn't right).pnpm vitest run tests/unit/shared/routes.test.ts tests/unit/utils/navigation.test.ts tests/unit/utils/seoDescriptions.test.ts/run-app: open the route in the editor, change the primary color and radius and confirm the preview reacts, toggle dark mode, use the command palette to find it, and for templates check the source view./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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。