Robinebers Cc Plugins
robinebers-cc-plugins is a Claude Code plugin for the Ship phase that adds two frontend-focused skills for codebase deduplication and maintenance on React and Next.js.
by robinebers · github.com/robinebers/cc-plugins
Add when you maintain Next.js or React frontends and want agents to find duplicate components, unused exports, and dependency noise before merge.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install robinebers-cc-plugins@robinebers/cc-pluginsBuilt 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:robinebers/cc-plugins") and the paste-ready config with skillselion.get_install_config("plugin:robinebers/cc-plugins").
What it does
robinebers-cc-plugins is a compact Claude Code offering with two specialized plugins for frontend teams and solo maintainers who care about Next.js and React hygiene. It helps an agent reason about duplicate UI patterns, stray exports, dependency bloat, and common Next-specific footguns so refactors stay small and reviewable. The bundle sits in Ship because its value peaks when you are hardening a codebase before release or during regular maintenance sprints, not when you are sketching a new product idea. Expect analysis and cleanup guidance rather than greenfield scaffolding or marketing automation. With two plugins and a narrow keyword set around dedup and unused symbols, it pairs well with a linter but adds conversational, repo-wide reasoning that static rules often miss.
Highlights
- Two plugins focused on frontend development and ongoing codebase maintenance
- React and Next.js-oriented analysis for duplicate components and export hygiene
- Dependency and pattern checks to surface unnecessary or unused code paths
- Agent-friendly workflows for identifying cache and proxy TypeScript issues
- Tagged for code-quality and frontend in the catalog—not a design system generator
Why builders use it
Frontend repos accrue duplicate components and dead exports that slow reviews and confuse agents during refactors.
After install, Claude can systematically flag duplicates, unused exports, and related Next.js maintenance issues during review-oriented sessions.
At a glance
- Type - Plugin in Frontend & UI.
- Adoption - 0 installs, 6 stars, 0 votes.
FAQ
Who is robinebers-cc-plugins for?
Developers maintaining React or Next.js codebases who want Claude Code help with deduplication and unused-code cleanup.
When should I use robinebers-cc-plugins?
Use it in Ship review when auditing exports, dependencies, and duplicate patterns before a release or large refactor.
How do I add robinebers-cc-plugins to my agent?
Register the robinebers/cc-plugins marketplace entry as robinebers-cc-plugins in Claude Code and enable its two plugins for your repo.
Comments
Share how you use robinebers-cc-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.