Most products have an implicit conceptual model that nobody wrote down, which is why the UI contradicts itself and engineers rebuild the same confusion in code. This skill gives you techniques to make it explicit: what objects exist (and what's just an attribute or instance), how they relate, what states matter, and what to call everything. The disciplines are the real value here, especially "real objects only" and catching when generic verbs like "edit" hide operations with different consequences. Use noun foraging when you have research to mine, relational diagrams when relationships are murky, or just define objects directly if you know what they are. It sits between domain understanding and interaction design, and it's genuinely load bearing even though most teams skip it.
npx skills add https://github.com/jamiemill/layers-skills --skill layers-conceptual-model