[v2] Anatomy Editor

[GarthDB]

Overview

Build an editor for component anatomy parts with validation against the global anatomy-parts enum.

Context

Component schemas need an anatomy field listing their parts (e.g., button-control, icon, label). These feed into token naming.

Goals

1. List and edit anatomy parts
2. Validate against global anatomy-parts.json
3. Suggest parts from similar components
4. Show usage across components

Tasks

• Build anatomy parts list UI

  • Display current anatomy parts for selected component
  • Add/remove parts with validation
  • Reorder parts (drag-and-drop or move up/down)
  • Show which parts are used in tokens

• Add anatomy validation

  • Validate against anatomy-parts.json enum
  • Check for duplicate parts
  • Validate naming conventions (kebab-case)
  • Warn about unused parts

• Build suggestion engine

  • Suggest parts from similar components (same category)
  • Show most commonly used parts
  • Recommend standard parts for component type
  • Flag potentially missing parts

• Add anatomy usage tracking

  • Show which tokens use each anatomy part
  • Show which components share anatomy parts
  • Display anatomy coverage (% components with anatomy defined)

• Integrate with mapping editor

  • Show anatomy parts in mapping preview
  • Validate token names use defined anatomy
  • Link from anatomy to related tokens

• Add anatomy part management

  • Request new global anatomy parts
  • Deprecate unused anatomy parts
  • Rename anatomy parts with migration

Success Criteria

• All components have anatomy field defined
• Anatomy parts validated against global enum
• Suggestions reduce manual lookup
• Usage tracking helps identify consolidation opportunities

Dependencies

• [Epic] v1 MVP: Basic Mapping Editor Tool #648 (Basic tool)
• Global anatomy-parts.json enum

Estimated Effort

2-3 weeks

Related

• RFC [DRAFT RFC] Token Schema Structure and Validation System #646: Token structure uses anatomy parts
• Token naming relies on anatomy definitions