Problem or opportunity
Without a shared schema boundary, each toolkit will evolve its own document shape and preset logic, making export, validation, and persistence harder to maintain.
Proposed change
Extract shared document and toolkit schemas into a config-schema package, including the discriminated toolkit document contract and shared preset metadata.
Success criteria
- Toolkit document contracts are defined centrally
- Shared schema can validate motion, dataviz, and social-card documents
- Future toolkit additions can plug into the same schema conventions
Constraints or scope notes
Problem or opportunity
Without a shared schema boundary, each toolkit will evolve its own document shape and preset logic, making export, validation, and persistence harder to maintain.
Proposed change
Extract shared document and toolkit schemas into a config-schema package, including the discriminated toolkit document contract and shared preset metadata.
Success criteria
Constraints or scope notes