What problem does it solve? Adding or changing a store editor in this Go codebase requires coordinating four layers — Cobra commands, domain adapters, the storeui orchestration package, and TUI presentation models — and getting the reflection, override, and per-field save semantics right is error-prone without a documented contract. ## Core Features & Use Cases - Architecture guidance: Documents the four-layer design (command → domain adapter → orchestration → presentation) and the import boundary that keeps bubbletea out of storeui. - Step-by-step build recipe: Walks through creating a domain adapter with Overrides and LayerTargets, wiring a Cobra edit command, and registering it in the parent command. - Testing patterns: Provides concrete test templates for override path validation, round-trip integration tests, WalkFields checks, and BubbleTea model tests. - Use Case: When adding a new settings or project edit command, follow the checklist to define field overrides, derive save targets from store.WriteTargets(), and verify behavior with round-trip tests. ## Quick Start Ask the agent to add a new store editor for a configuration domain following the store-editor skill's adapter, command, and testing checklist.