Map Product Anatomy

Given a software product surface, workflow, or shaped feature, use Anatomica to make its structure and behavior inspectable as text. When a structural drawing is useful and requested, translate that anatomy into a breadboard and use what it reveals to revise the anatomy and any source pitch.

Boundaries

Map the product that is supported by the supplied evidence. Do not invent screens, states, actions, or flows to make the map look complete. Preserve assumptions and unknowns explicitly.

For a proposed feature, map supported intent from its pitch and scopes as provisional structure, distinguishing existing behavior, proposed decisions, and unresolved choices. A complete-looking map or drawing does not establish user demand or validate the proposal.

This Skill describes product anatomy; it does not replace product discovery, visual design, technical architecture, or implementation planning.

Grammar

[Screen]::Component.SubComponent@state.action() => [dest] | ::Component | .action() | @state

Read references/anatomica.md for the notation and source conventions.