data-normalization
Data Normalization
Define a shared, authoritative format for every primitive type in a project and
produce the artifacts that enforce it: a CANONICAL_DATA_MODEL.md, field
mapping tables per source, adapter / validator code, and an ADR.
Related skills: domain-language (align on naming before locking formats) ·
adr (record format decisions)
Scope
This skill covers:
- Authoring or updating a
CANONICAL_DATA_MODEL.mdthat defines the internal format for each primitive type used in the project - Producing field-by-field mapping tables from each external source to the canonical model
- Generating adapter / validator code in the project's target language
- Filing an ADR that records why these formats were chosen and what was rejected
More from yldgio/vibe-grimoire
pre-mortem
>-
13create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11prd-slice
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9