share the component API? #24
markacianfrani
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Can this bare minimum at least give the LLM the component API? This requires me to know the full component name ahead of time, which, even as a librarian...I forget the official names for some of these things.
Or return the docs as markdown? All an LLM needs is the public API and maybe a few examples of the markup if it's crazy complicated. They can even guess the API like 70% of the time because all of our components are basically the same anyway. But pointing it to fetch storybook is crazy inefficient for the context window.
The number one use case for a storybook MCP is to be able to give it to designers, product, and onboard new developers IMO. I just can't quite tell if that's the vision for this project or should be something else.
Beta Was this translation helpful? Give feedback.
All reactions