ui-pack-maintainlisted

Creates, extends, repairs, validates, versions, and publishes reusable UI Packs. Use when adding or changing UI Pack Foundations, Components, Patterns, Presets, design tokens, state adapters, manifests, or registry metadata, or when extracting a reusable visual system from screenshots, existing pages, or computed styles. Creating a Pack relies only on the self-contained contract plus user intent; maintenance may additionally read existing Packs. Do not use for generating business prototypes, editing production frontend code, installing packs for end users, or ordinary page styling.
Lisuiwen/ai-html-annotation · ★ 18 · Web & Frontend · score 79

Install: claude install-skill Lisuiwen/ai-html-annotation

# UI Pack Maintain Self-contained authoring and publication workflow for UI Packs. This skill owns the pack contract, schema version rules, registry format, validator, and release metadata. It does not own consumer-side discovery, download, or prototype generation. ## Quick start Create a Pack, then validate and resolve it: ```bash node scripts/validate-pack.mjs --pack=<pack-directory> --strict node scripts/resolve-pack.mjs --pack=<pack-directory> --entry=<id>[,<id>...] ``` Before publishing pack changes: ```bash node scripts/generate-registry.mjs node scripts/generate-registry.mjs --check ``` Landing paths, create/update steps, and the consumer resolver smoke test are in [Pack authoring](references/pack-authoring.md). ## Responsibility split | Owns `ui-pack-maintain` | Owns `html-prototype-build` | |---|---| | pack contract, `schemaVersion`, `validate-pack.mjs`, registry generation | pack lookup chain, `install-pack.mjs`, `deliver[]` copy-out | | in-pack `resolve-pack.mjs` (`--pack=<dir> --entry=`) | consumer `resolve-pack.mjs` (`--list` / `--select`) | | pack lifecycle: create → validate → version → publish | prototype generation | ## Workflow 1. Read `references/contract.md` for structure and responsibility boundaries. In **creation** mode, stop here for evidence. In **maintenance** mode, continue to step 2. 2. Read the target Pack's `PACK.md` and `manifest.json`, plus only the resource entries this task touches (maintenance only). 3. Classify the chang