Skip to content
cccskills
FreePublished on GitHub

nuxt-ui-tools-maintainer

Use this skill for internal maintenance and feature work in the nuxt-ui-tools repository. It explains the repository operating model, exact placement rules, how runtime domains relate, how features should be structured and extended, how consumer skills must be maintained, and what to keep in sync when changing the library.

The English summary is being prepared. Showing the original description.

See how to install

Files included (12)

  • SKILL.md4.2 KB
  • references/change-workflow.md2.2 KB
  • references/consumer-skills.md2.2 KB
  • references/core-approach.md3.8 KB
  • references/dashboard-runtime.md27.8 KB
  • references/file-preview-runtime.md4.4 KB
  • references/form-runtime.md13.3 KB
  • references/placement-rules.md3.6 KB
  • references/query-state.md1.8 KB
  • references/shared-runtime.md809 B
  • references/spreadsheet-runtime.md6.0 KB
  • references/table-runtime.md7.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

nuxt-ui-tools Maintainer

Use this skill for internal repository work.

This is the main internal maintainer skill. It should be the first deeper skill loaded after AGENTS.md when the task is about implementing, refactoring, organizing, or extending code in this repository.

Read First

  • AGENTS.md
  • .agents/skills/nuxt-ui-tools-maintainer/references/core-approach.md
  • .agents/skills/nuxt-ui-tools-maintainer/references/placement-rules.md
  • .agents/skills/nuxt-ui-tools-maintainer/references/change-workflow.md
  • .agents/skills/nuxt-ui-tools-maintainer/references/consumer-skills.md

Then load the domain reference that matches the task:

  • table runtime: .agents/skills/nuxt-ui-tools-maintainer/references/table-runtime.md
  • query-state runtime: .agents/skills/nuxt-ui-tools-maintainer/references/query-state.md
  • shared runtime: .agents/skills/nuxt-ui-tools-maintainer/references/shared-runtime.md
  • form runtime: .agents/skills/nuxt-ui-tools-maintainer/references/form-runtime.md
  • dashboard runtime: .agents/skills/nuxt-ui-tools-maintainer/references/dashboard-runtime.md
  • file preview runtime: .agents/skills/nuxt-ui-tools-maintainer/references/file-preview-runtime.md
  • spreadsheet import runtime: .agents/skills/nuxt-ui-tools-maintainer/references/spreadsheet-runtime.md

For technical foundation work, also load the matching skill:

  • TypeScript policy and schema typing: .agents/skills/nuxt-ui-tools-typescript/SKILL.md
  • lean reactivity and query-state integration: .agents/skills/nuxt-ui-tools-reactivity/SKILL.md
  • config/registry-driven feature architecture: .agents/skills/nuxt-ui-tools-config-driven/SKILL.md

What This Skill Exists To Solve

It should make two things easy:

  1. maintenance and development by both AI agents and humans
  2. adoption of the library by package consumers

That means internal code decisions should optimize for:

  • clear placement
  • low cognitive load
  • modular structure
  • predictable extension patterns
  • stable and discoverable consumer surfaces

Core Internal Rule

When making changes, always think in both directions:

  • inward: does this make the codebase easier to understand, evolve, and validate?
  • outward: does this make the package easier to use, document, and teach?

If a change improves implementation convenience but makes consumer usage or future maintenance worse, it is probably the wrong move.

What Agents Must Be Able To Answer

After reading this skill, an agent should be able to answer all of these quickly:

  • which runtime domain owns the change
  • which layer inside that domain owns the change
  • whether the feature should be config-driven, registry-driven, or a simpler direct abstraction
  • whether complexity should be absorbed by the package instead of leaking to consumers
  • which tests, playground routes, consumer skills, and internal references must be updated

If the current guidance does not make those answers obvious, improve the guidance as part of the task.

Internal Routing

If the task is about:

  • overall repository structure, placement, or feature organization: use core-approach.md and placement-rules.md
  • extension workflow or how to land a feature cleanly: use change-workflow.md
  • table internals: use table-runtime.md
  • query-state internals: use query-state.md
  • TypeScript and type-system shaping: use .agents/skills/nuxt-ui-tools-typescript/SKILL.md
  • reactive state design: use .agents/skills/nuxt-ui-tools-reactivity/SKILL.md
  • config-driven or registry-driven architecture: use .agents/skills/nuxt-ui-tools-config-driven/SKILL.md
  • consumer-facing package skill maintenance: use consumer-skills.md

Skill Split Reminder

Internal maintainer guidance belongs in:

  • .agents/skills/

Consumer package guidance belongs in:

  • skills/consumer/

Do not mix them.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

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.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

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.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

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.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

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, rich options (icon, avatar, chip, description, suffix, grouped menus, and renderOption/renderValue render functions on select, auto-complete, radio, and checkbox group), choice cards, and typed submit results.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

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.

The English summary is being prepared. Showing the original description.

ChronicStone/nuxt-ui-tools2Updated Oct 17, 2026

See all skills by ChronicStone

Report a problem with this skill