Skip to content

ChronicStone/nuxt-ui-tools / .agents/skills/nuxt-ui-tools-maintainer

nuxt-ui-tools-maintainer

Verified

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.

references/change-workflow.md

View on GitHub
# Change Workflow

Use this reference when implementing or refactoring a feature.

## Step 1: Classify The Change

Identify whether the change is primarily about:

- public package surface
- domain runtime behavior
- query-state primitive behavior
- shared helper behavior
- rendering/presentation
- documentation/consumer guidance

## Step 2: Decide The Owning Layer

Ask:

- is this a public contract change?
- is this orchestration?
- is this pure transformation?
- is this rendering?

Then place it in the right layer.

Also ask:

- does this belong in a current runtime domain, or should it be shared?
- is this a variant-specific implementation that should live behind a config/registry contract?
- is this an opportunity to reduce a current abstraction leak?

## Step 3: Normalize Before Branching

If the feature introduces variants, do not immediately write a giant branching implementation.

Ask first:

- what is the shared contract?
- what are the variant-specific pieces?
- should this be config/registry-driven?
- can I make the public surface simpler by moving complexity inward?

## Step 4: Protect Consumer Simplicity

Before finalizing the implementation, ask:

- does this improve or damage inference?
- does it force awkward consumer-side typing?
- does it create a workflow that is hard to explain?

If yes, fix the abstraction.

## Step 5: Update The Full Surface

When relevant, update:

- implementation
- tests
- playground validation surface
- consumer skills
- internal skills if architecture or extension patterns changed
- `src/imports.ts` and `src/components.ts` if the intended public surface changed

If the change touches user-facing behavior, treat the consumer skill update as required, not optional.

## Step 6: Prefer Refactoring Over Layering

If the existing code is wasteful or over-layered:

- simplify it
- reorganize it
- remove unnecessary wrappers

Do not preserve a weak structure just because it already exists.

## Step 7: Leave The Area Easier To Navigate

When you touch a confusing area, try to improve at least one of:

- file placement
- naming
- type clarity
- reactive simplicity
- config/registry structure
- related internal or consumer guidance
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall