Plugin within a plugin?

[jgorfine-zendesk]

Hi @taylorarndt & @jeffreybishop, my name's Jen, and I've been tasked with figuring out how my team at work can best leverage gen AI to further our accessibility efforts. (No pressure. 🙃) I started by creating an accessibility plugin in my company's internal Claude marketplace. That plugin is still very small and new, and mostly concentrates on how to maximize our design system + component library for accessibility.

About a week ago, I came across your project on LinkedIn. After reading your (Taylor's) Substack post and perusing the accessibility-agents repo contents, I'm feeling confident that this is exactly what I — and my company — needs. Thank you so, so much for creating such a fabulous and robust plugin —and for making it open source. 👏

Here's where my question comes in: what might be the best way for me to incorporate your work with mine? i.e., to use your plugin within another plugin.

I'm seeing manual setup steps, in the Getting Started docs...but I'm concerned that if I go down that road:

1. Our plugins would become to tightly coupled
2. My teammates and I would miss out on invaluable automatic updates

Here's what I'm imagining instead, at a high level:

1. Folks only need to download one plugin: the one I'm working on, which is considered the one and only "source of truth" for accessibility
2. Company plugin helps manage accessibility-agents plugin:
   • If this is the first time company plugin is installed, it goes on to also install accessibility-agents
   • If someone already has company plugin installed, but not accessibility-agents, accessibility-agents is installed
   • If someone already has company plugin + accessibility-agents, check for updates
3. Claude will use the fundamentals/concepts from accessibility-agents while prioritizing code that implements our design system components over custom components
   • For example, we have a component that could create a visually-hidden live region like this: <Span role="status" aria-live="polite" hidden></Span>. We would want code to write it like that rather than with the custom class suggested by the live-region-controller's visually-hidden live region pattern.

Maybe this is a matter of adjusting the install commands so that they could recognize a plugin directory structure and install accordingly? Or maybe my plugin's primary agent calls the accessibility-agent's one-liner install command, on behalf of the user? 🤔

I'm still pretty new to Claude (+ gen AI in general), so I'm very much open to ideas and suggestions.

Thanks in advance!