Member-only story
They’re all organized by who built them. You’re always looking for something else: the job you’re trying to do.
A year ago, “AI in your editor” meant autocomplete. Now there’s a whole layer of add-ons beneath the agent — Claude Code plugins, MCP servers, framework packs, editor extensions. Between the official and community catalogs alone, there are well over 250 of them, and more land every week.
Finding the right one is genuinely hard, and it’s hard for a structural reason: they’re catalogued by vendor, but you search by job.
Think about how the need actually arrives. Something breaks in production and you want the agent to trace why — not explain what a null reference is. You just wrote a feature and want the tests you skipped. A sprint’s half over and nobody knows what’s actually done. Those are jobs. But the directories answer a different question — who published this? — and hand you an alphabetized list to dig through.
Organize by job instead #
Flip the axis and the whole thing gets usable. Sort add-ons by what you’re trying to accomplish, and the shortlist for any given moment drops from forty to about three. A reasonable set of jobs looks like this: