Documentation Feedback: "Copy for LLM" context bloat & suggestion for Agent Skills #9508
cheema-corellian
started this conversation in
General
Replies: 2 comments
-
|
Agent Skills are definitely on our radar. I think we mainly need to think about maintenance/distribution before we publish anything. If you have any good examples, feel free to share. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for the response, @reidbarber! To help explore what this could look like, I went ahead and created an unofficial AI agent skill for Spectrum 2 here: https://github.com/cheema33/react-spectrum2-skill. It’s intended as a proof-of-concept until an official version is feasible. Feedback and patches are definitely welcome! |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
I really appreciate the new docs—they are definitely more LLM-friendly than before! However, I wanted to share feedback on two areas that could improve the experience significantly:
1. Context Bloat in "Copy for LLM"
On pages like Getting Started, the content changes based on user selection (e.g., selecting Vite + pnpm). However, clicking the "Copy for LLM" button copies the documentation for all possible scenarios, rather than just the active selection.
2. Component Discoverability & Agent Skills
Agents often don't know which Spectrum components exist, so they guess (often wrongly) or build custom React components instead.
Beta Was this translation helpful? Give feedback.
All reactions