A stateful field, state by state
A header search field with suggestions and recent results looks like it breaks a presentational model. It doesn't — you model the state space, not the transitions. Each state becomes its own story and its own Figma frame.
How it works
Take a search field in a header: it opens a dropdown, shows suggestions as you type, remembers recent searches. The instinct is that this is too behavioural to model. But you do not model "typing filters the list" — you model the states: Closed, WithSuggestions, RecentSearches, Empty, Loading. Each is a story with sampled data; each renders as its own Figma frame; a designer tweaks the dropdown's spacing on the state that needs it and it round-trips. The filtering logic is never touched, because it was never Inkbridge's job. States are design; transitions are engineering. That split is why even a genuinely complex component fits the methodology — and why you write one story per state rather than one story that toggles them.