storybook-visual-state-nested-props

What problem does it solve? Storybook's URL-arg resolver only handles flat props and top-level dot paths, so an arg targeting a nested array element or object path (like actions[0].pressed) is silently ignored — the screenshot captures the default render while the test still passes, producing a baseline that proves nothing. ## Core Features & Use Cases - Silent-failure diagnosis: Identifies when &args= values targeting nested props are dropped without error, leaving the story in its rest state. - Story-based state pattern: Guides moving nested values into a dedicated named story whose args contain the fully built object, then pointing the visual spec at that story id. - Baseline regeneration workflow: Covers verifying the story render in a browser, regenerating baselines via the repository's visual-baseline update target, and inspecting the written PNG. - Use Case: A Playwright visual test sets ?args=actions[0].pressed:true but the recorded baseline looks identical to the rest state — this Skill explains why and shows how to bake the pressed state into an EyePressed story instead. ## Quick Start Ask the assistant to fix a Storybook visual state test whose nested URL args never apply by moving the state into a dedicated story and regenerating the baseline.