schema-field-add

Drive the full lifecycle of adding or renaming a field on the canonical Zod schema in shared/src/schema.ts — ADR check, schema edit, schema.md doc, YAML migration across content/components/*.yaml + implementations/*/*.yaml, render-side update in site/, test guard, and build-hygiene cleanup. Use whenever the user asks to add a new field to the canon, rename one, change a vocabulary, or make a non-additive schema change. Triggers on phrases like "add field X", "neues feld auf schemaX", "rename type to kind", "migrate vocabulary", "schema change for X", "extend componentSchema", "extend patternSchema", "extend a11yAcceptanceSchema". Prefer this over ad-hoc edits because forgetting any of the seven steps leaves the repo half-migrated; the build-hygiene gotcha (`pnpm -F @uianatomy/shared build && rm -rf site/.astro`) and the YAML-migration step are the two most commonly forgotten parts.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "schema-field-add" with this command: npx skills add DominikPieper/skillsmp-dominikpieper-dominikpieper-schema-field-add

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

General

adr-author

Author a new ADR for the uianatomy project under docs/adr/ following the established template (Status / Date / Supersedes / Context / Decision / Rationale / Consequences). Use whenever the user wants to record an architectural decision, deprecate a prior ADR, or document why a proposal was rejected — phrases like "ADR für X", "neue ADR", "decision record", "supersede ADR-NNN", "reject this proposal as ADR", "schreib eine ADR". Picks the next sequential number, links the supersedes target, and sets the status correctly. Prefer this over freehand writing whenever the topic is an architectural choice that shapes the schema, repo layout, MCP tools, or content conventions.

Repository SourceNeeds Review
-0DominikPieper
General

uianatomy-mcp

Query the UI Anatomy MCP server for canonical UI component anatomy, axes, slots, transitions, motion, tokens, events, cross-framework mapping, library divergences, and compositional patterns.

Repository SourceNeeds Review
-0DominikPieper
Security

component-review

Audit one or many existing canonical components in content/components/<id>.yaml against every schema section, the depth contract, recent schema additions, vsRelated bidirectional integrity, vocabulary drift, and source-claim staleness — emit a structured gap report with pre-formatted backlog items ready to drop into docs/backlog.md. Use whenever the user asks to review, audit, check, lint, or QA a component or the whole canon — phrases like "review tabs", "audit modal", "check accordion", "QA-Pass über alle komponenten", "find gaps in X", "atelier-v3 review", "ist X vollständig", "missing was bei Y". This is the systematic per-component version of the broad Atelier-v2 review pass that produced 22 backlog items in one go; running it on stale components catches schema-additions they didn't get migrated for.

Repository SourceNeeds Review
-0DominikPieper
Automation

backlog-tick

Maintain docs/backlog.md as the single source of workflow truth — flip [ ] → [x] when an item finishes, append the completion date and a one-line outcome plus affected files, update the "Empfohlener Pfad" line if the next item shifted, and append newly discovered work in the right priority bucket. Use whenever the user says "fertig", "done", "erledigt", "gerade gepusht", "ship that", or whenever any non-trivial work concludes; also use mid-session when new follow-ups, bugs, missing tests, deferred cleanups, or schema gaps surface — append them automatically per docs/CLAUDE.md without waiting to be asked. Keeps PX-NN ids sequential within their bucket and prevents stale items from accumulating.

Repository SourceNeeds Review
-0DominikPieper
schema-field-add | V50.AI