Total Skills
7
Author Profile: DominikPieper
Skills published by DominikPieper with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
component-review
0
Stars
0
Downloads
0
adr-author
0
Stars
0
Downloads
0
backlog-tick
0
Stars
0
Downloads
0
canon-component-author
0
Stars
0
Downloads
0
mcp-tool-add
0
Stars
0
Downloads
0
schema-field-add
0
Stars
0
Downloads
0
uianatomy-mcp
0
Stars
0
Downloads
0
Published Skills
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
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
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
canon-component-author
Research and author a new canonical component YAML in content/components/<id>.yaml from scratch — synthesizing anatomy, axes, mismatches, mistakes, frameworkMap, motion, responsive, and all P2 sections from W3C APG, MDN, WCAG, and at least three mature headless libraries (Radix, React Aria, Headless UI, Spectrum) plus two design systems (Polaris, Carbon, Material 3, Atlassian, GOV.UK). Use whenever the user asks to add, draft, or research a new canonical component — phrases like "neue komponente X", "draft canonical Y", "research and write the Z anatomy", "add component", "author canon for component", "synthesize component anatomy". Strictly canon-first per ADR-001 — never references implementations like Atelier UI. Validates against the depth contract in shared/tests/depth.test.ts before declaring done.
Repository SourceNeeds Review
mcp-tool-add
Add a new tool to the uianatomy MCP server (mcp-server/src/server.ts) — Zod input schema, handler that reads from getComponents/getPatterns/getImplementations state, deterministic output shape, error-path for unknown ids, and a matching test in mcp-server/tests/. Use whenever the user wants a new MCP tool, a bulk-fetch wrapper, an aggregation across canon, or a new query surface for AI agents — phrases like "neues MCP-tool", "add tool to MCP server", "expose X via MCP", "bulk-fetch tool", "aggregation tool", "new tool X". Picks the right naming bucket (list_/get_/search_/validate_), writes consistent error returns, and updates the tool-count in docs/backlog.md and project_state memory.
Repository SourceNeeds Review
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.
Repository SourceNeeds Review
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