What problem does it solve? Deciding which game values belong in external JSON Docs versus code, how to split Docs by concern, and how to structure schemas so the Studio editor renders usable forms is error-prone; this Skill codifies those design decisions. ## Core Features & Use Cases - Externalize vs. code decisions: Criteria for which values (tunable numbers, lists, color themes) go into JSON Docs and which stay in code. - Doc splitting rules: One Doc per concern, with concrete split signals such as 5+ same-prefix keys, 30+ scalars, or 16+ list items. - Schema dialect reference: The five Studio-supported kinds (value/field, record, catalog/map, list) plus common mistakes that silently break form rendering. - Use Case: When adding a new tunable section to a game like harvest.kind.json, use this Skill to decide the Doc boundaries and schema shape so the editor shows grouped tabs instead of 29 flat fields. ## Quick Start Use the doc-design skill to review my new game configuration JSON and tell me how to split it into Docs and which schema kinds to declare.