Hi! Thanks for react-grab!
It's sooo great for feeding component context to AI agents.
We made a Storybook addon on top of it. It loads react-grab in the Storybook preview and, in addition to the normal copy, appends the current story's id and args. So when you grab an element, the agent also sees which story and variant it came from.
[<button> in Button (at src/Button.tsx:12:5)]
--- Storybook ---
Story: Components/Button › Primary (components-button--primary)
Args: { variant: "primary", size: "md" }
The goal was to bring designers into the AI-agent dev loop. Our designers work in Figma, and getting that design intent into an agent workflow was finicky, especially on a brownfield codebase where vibe design tools didn't hold up well. Storybook already renders our actual components, so having someone grab the real thing there, with its story context, turned out to be a far more reliable bridge to the agent.
We'd love any feedback or suggestions, and feel free to link it if it's useful to others.
Thanks again for building react-grab 🙏
Hi! Thanks for react-grab!
It's sooo great for feeding component context to AI agents.
We made a Storybook addon on top of it. It loads react-grab in the Storybook preview and, in addition to the normal copy, appends the current story's id and args. So when you grab an element, the agent also sees which story and variant it came from.
The goal was to bring designers into the AI-agent dev loop. Our designers work in Figma, and getting that design intent into an agent workflow was finicky, especially on a brownfield codebase where vibe design tools didn't hold up well. Storybook already renders our actual components, so having someone grab the real thing there, with its story context, turned out to be a far more reliable bridge to the agent.
We'd love any feedback or suggestions, and feel free to link it if it's useful to others.
Thanks again for building react-grab 🙏