Plugin · Claude Code · Development Tools

Nevaberry Nevaberry Plugins

nevaberry-nevaberry-plugins is a Claude Code plugin marketplace for the Build phase that supplies knowledge patches so agents use correct post-cutoff language and framework behavior.

by Nevaberry · github.com/Nevaberry/nevaberry-plugins

Fill post-cutoff gaps in Claude’s knowledge across dozens of languages and frameworks via installable knowledge patches.

14
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install nevaberry-nevaberry-plugins@Nevaberry/nevaberry-plugins
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:Nevaberry/nevaberry-plugins") and the paste-ready config with skillselion.get_install_config("plugin:Nevaberry/nevaberry-plugins").

About

What it does

nevaberry-nevaberry-plugins is a large Claude Code plugin collection from Nevaberry that treats each plugin as a knowledge patch: curated facts about language and framework behavior that shipped after LLM training cutoffs. Solo builders install subsets matching their stack so the agent stops inventing deprecated APIs, wrong auth flows, or missing async patterns. With roughly ninety plugins spanning web frameworks, mobile, cloud, tooling, and security advisories, the bundle is closer to a living changelog library than a one-shot generator. On Skillselion it shelves under Build → Integrations as the primary attach point, but journeyScope is journey-wide because you invoke patches whenever coding—not only greenfield build. Complexity trends intermediate because you must pick the right patches and keep them updated. It complements official docs and MCP doc fetchers by embedding opinionated, version-tagged guidance directly in the agent session.

Highlights

  • 90 Claude Code plugins as knowledge patches for post-training-cutoff features
  • Broad coverage: Rust, Bun, Angular, AWS, auth, Android, Ansible, and more
  • Behavioral alignment and breaking-change notes baked into patch topics
  • Community-maintained Nevaberry catalog for agent-accurate codegen

Why builders use it

Claude Code confidently uses outdated APIs and missing features because training data stopped before your stack’s latest releases.

After registering the marketplace and enabling relevant patches, codegen and explanations align with newer framework and runtime behavior.

At a glance

  • Type - Plugin in Development Tools.
  • Adoption - 0 installs, 14 stars, 0 votes.

FAQ

Who is nevaberry-nevaberry-plugins for?

Developers using Claude Code who need accurate, post-cutoff knowledge for many languages and frameworks via small installable patches.

When should I use nevaberry-nevaberry-plugins?

Use it whenever agent suggestions drift from current docs—during build, review, or upgrades—by enabling patches for your active stack.

How do I add nevaberry-nevaberry-plugins to my agent?

Add the Nevaberry/nevaberry-plugins source in Claude Code, browse the ~90 plugins, and install only the knowledge patches matching your project dependencies.

Discussion

Comments

Share how you use nevaberry-nevaberry-plugins, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.