Use this skill for internal i18n work in this repository. Covers locale ownership, provider wiring, lazy schema text contracts, and the maintenance surfaces that must stay in sync when package or playground translations change.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill for internal repository work involving:
src/runtime/i18n/*Read first:
AGENTS.md.agents/skills/nuxt-ui-tools-maintainer/SKILL.mdThen inspect:
src/runtime/i18n/types.tssrc/runtime/i18n/locales/*.tssrc/runtime/i18n/use-locale.tsThere are two different translation paths in this repository.
This is the built-in chrome owned by ui-tools, for example:
This copy belongs in:
src/runtime/i18n/types.tssrc/runtime/i18n/locales/en.tssrc/runtime/i18n/locales/fr.tsResolve this copy through useUiToolsLocale().
Do not leave hardcoded English strings inside runtime components when the package owns the wording.
This is consumer-provided text such as:
This copy must stay translation-friendly by contract.
Preferred public surface:
stringnumber() => string | numberOnly widen further when a surface genuinely needs rendered content.
If a schema text surface is raw-string-only and blocks consumer i18n, fix the owning type and owning resolver.
Do not:
computed(() => defineSchema(...))Keep locale messages grouped by feature and sub-feature.
Preferred shape:
table.header.*table.footer.*table.filters.panel.*spreadsheet.steps.review.*Do not dump unrelated labels into flat objects.
When adding a new package-owned text surface:
src/runtime/i18n/types.tst('...')en and frWhen refactoring or removing an i18n surface:
Do not keep stale locale entries around after UI changes.
Unused translation keys are misleading maintenance debt and should be cleaned up in the same task that made them obsolete.
When widening a schema surface for i18n:
() => t('...')The playground is part of the validation surface.
If a demo route includes visible scenario text, workbook headers, example labels, or schema-owned UI copy, keep it translatable with real translation keys.
Do not treat the playground as exempt from i18n just because it is demo content.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use this skill when working with the nuxt-ui-tools package as a consumer or integrator. It provides the current package overview and routes to table, form, dashboard, file preview, query-state, shared responsive helpers, remote option loaders, and i18n usage.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for internal architecture work around config-driven, registry-driven, and pattern-driven feature design in the nuxt-ui-tools repository. Covers how to organize variant-heavy features, where to put implementations, and how to keep both internals and public APIs standardized.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when building analytics dashboards with nuxt-ui-tools as a package consumer. Covers schema and view functions (defineDashboardSchema, defineDashboardView) that take their context as typed params, useDashboard with a getter that rebuilds on input change, typed injection (useDashboardView, injectDashboard, InferDashboard, InferDashboardView), filters declared inline with the f builder and synced with the URL, memory, or an external store (one value per key across views), headless filters, filter controls and the shipped UI (UiDashboardPage, UiDashboardFilters, UiDashboardFilter, UiDashboardViewTabs) with slot overrides, remote paginated pickers and remoteTableOptions, staged queries (essential / background / deferred) with select and dependent requires, lazy enabled conditions on views, queries, and filters (blocks of disabled queries hidden, grids closing up), derived values, views (tabs), query-scoped filters, number formats (presets, Intl options, useDashboardFormat), and the dashboard blocks (stats with trends, goals, and comparisons, stat groups, gauges, unovis charts with highlights, value labels, and totals, lists with progress rings, bars, funnel, alerts, activity feeds, sortable tables, custom widgets) with their automatic loading, error, empty, and refresh states, card menus, header and footer actions, row actions, drill-down and selected state, card tabs, split cards, comparison periods, auto-refresh, and data freshness.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when previewing files with nuxt-ui-tools as a package consumer. Covers mounting UiFilePreviewProvider, opening one file or a gallery with useFilePreview() or useNuxtApp().$filePreview, file descriptors (URL, File/Blob, or a function that returns a signed URL), options (index, mode, gallery, loop, pdf page, callbacks), the returned handle, the built-in renderers (image, video, audio, PDF, text/JSON, CSV, Markdown, Office and archive fallbacks), renditions, download and custom header actions, the markdown render hook, custom renderers with defineFilePreviewRenderer and UiFilePreviewTools, theming tokens, and how the upload field uses the preview.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when working with the nuxt-ui-tools form runtime as a package consumer. It covers schema-driven forms, the provider-backed form API, inline rendering, overlay rendering, form pages with a section navigation, choice cards, and typed submit results.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when wiring nuxt-ui-tools translations in an app. Covers UiToolsProvider, locale objects, lazy schema text, and how package-owned UI copy differs from schema-owned text.
日本語の概要は準備中です。原文の説明を表示しています。