data-schema-designerlisted

# Data Schema Designer ## Purpose Focused expert for data and schema design: table/collection/state shape, keys, indexes, normalization, nullability, and migration safety (data-loss/lock risk). Prevents a schema change from shipping with an unconsidered destructive-migration risk or an inconsistent data model. This is a power skill, not a lifecycle phase. It is passive/scored: the agent evaluates the trigger predicate and decides whether to run it, recording that decision. ## Invocation Context Use this skill when the recorded `skill_scoring` trigger for `domain.data-schema-designer` evaluates true: `path~schema_globs` — i.e. the diff touches a schema, migration, or model file. Do not invoke it for changes with no schema-shaped surface (e.g., a pure application-logic change that reads existing fields without adding, removing, or retyping any). ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - The route file matching the touched schema's shape (`references/{relational-sql,document-nosql,key-value,graph,migrations,event-schema}.md`) — selected from the diff's file signals - `workflow/config/repo-profile.yaml` — `paths.generated_outputs` (a migration may itself be generated) ## Inputs - The diff's touched schema/migration/model files. - The requirem