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 locates local packs for maintenance. It does not own download or prototype generation.

Quick start

List installed packs (same lookup chain as html-prototype-build), then validate and resolve:

node scripts/list-packs.mjs
node scripts/validate-pack.mjs --pack=<pack-id|directory> --strict
node scripts/resolve-pack.mjs --pack=<pack-id|directory> --entry=<id>[,<id>...]

Pack discovery order: --pack-root= / HTML_PROTOTYPE_PACK_ROOT, then <cwd>-upward .html-prototype/packs/, then ~/.html-prototype/packs/. Pass a filesystem path to --pack= to skip id lookup. Details in Pack authoring.

Before publishing pack changes:

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.

Responsibility split

Owns ui-pack-maintain	Owns html-prototype-build
pack contract, schemaVersion, validate-pack.mjs, registry generation, maintenance lookup (list-packs.mjs)	consumer lookup, install-pack.mjs, deliver[] copy-out
in-pack resolve-pack.mjs (`--pack=<id	dir> --entry=`)
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 change as Pack creation, Foundation, Component, Pattern, Preset, registry/publication, or repair.
4. Read Pack authoring and implement the smallest reusable change.
5. Update manifest.json, then run deterministic validation.
6. For a new Pack or substantial semantic change, run the isolated review in Isolated semantic review.
7. Regenerate registry.json when publishing or changing downloadable metadata.
8. Apply only verified findings, then rerun validation and the resolver smoke test.

Evidence priority is documented in Evidence authority.

Publication references:

• Registry format
• schemaVersion contract

Hard boundaries

• Keep a UI Pack inside the directory resolved by --pack=; this skill discovers installed packs through the shared root chain (explicit roots, project, user cache). It does not implement consumer download flows.
• Keep the Foundation DOM-free; include only shared tokens and a document-level CSS baseline.
• Keep each Component as one leaf implementation with a local contract.
• Compose Components through Patterns without copying their implementations.
• Keep Presets business-fact-free.
• Keep state adapters to projecting passed local state only; never access PrototypeViewers, persist state, parse URLs, or register global event handlers.
• Treat manifest.json as the only machine-readable index and dependency source.
• Declare only required dependencies in requires; keep conditional capabilities in optional.
• Patterns and Presets must not select internal components directly.
• Declare sketch atoms in components[<id>].atoms, and mark each one with data-pack-atom in its own component.html. Mark one control per atom, not a composite demo.
• Do not implement consumer download flows here; point users to html-prototype-build Pack install.

Deterministic validation

node scripts/validate-pack.mjs --pack=<pack-directory> --strict

The validator enforces the pack contract, including pack-local vendor / runtime / assets and manifest.delivery. Fix every error before semantic review. Warnings must be resolved or explicitly reported as evidence gaps.

It cannot judge whether a component boundary is useful or whether visual evidence is sufficient; delegate those questions to the semantic reviewer.

Resolver smoke test

node scripts/resolve-pack.mjs --pack=<pack-directory> --entry=<id>[,<id>...] [--optional=<id>[,<id>...]]

This covers in-pack requires/uses closures only. After validation, also run the consumer resolver check in Pack authoring. Cross-pack references are out of scope and must be reported as a ponytail: evidence gap.

Completion report

Report:

• changed Pack entries
• evidence used
• provisional decisions and missing evidence
• validator and resolver test results
• registry regeneration status
• unresolved independent-review findings