Lisaross Claude Code Plugins
lisaross-claude-code-plugins is a Claude Code plugin marketplace for the Build phase that helps migrate monolithic CLAUDE.md and rules files into a modular directory structure.
by lisaross · github.com/lisaross/claude-code-plugins
Install Lisa Ross’s single plugin to migrate a monolithic CLAUDE.md or rules file into a modular directory structure Claude Code can load cleanly.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install lisaross-claude-code-plugins@lisaross/claude-code-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:lisaross/claude-code-plugins") and the paste-ready config with skillselion.get_install_config("plugin:lisaross/claude-code-plugins").
What it does
lisaross-claude-code-plugins is a minimal Claude Code marketplace with one plugin dedicated to taming oversized agent instruction files. Solo builders who started with a single monolithic CLAUDE.md or rules blob—and now struggle to edit, version, or reason about what the agent sees—use this bundle to migrate toward a modular layout with clearer directories and file boundaries. The problem is familiar: early projects optimize for speed, then agent behavior becomes opaque because every rule lives in one file. This marketplace does not ship application features; it reshapes how Claude Code ingests project guidance so you can iterate rules like code. It fits the Build phase under agent-tooling because you are configuring the agent workspace before scaling feature work. Prerequisites are simply Claude Code and a project ready to refactor its rules tree; no external API keys are implied by the ingested metadata.
Highlights
- Marketplace with 1 focused plugin for CLAUDE.md and Claude rules organization
- Migrates monolithic rules into a modular directory and file structure
- Aligns with claudemd and clauderules naming conventions for discoverability
- Reduces context bloat by splitting instructions into maintainable chunks
- Community-maintained marketplace aimed at cleaner long-term agent projects
Why builders use it
A single giant rules file makes Claude Code hard to maintain and causes confusing, overlapping agent instructions on solo projects.
After install, you can reorganize claudemd and clauderules into a modular tree the agent loads predictably.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 2 stars, 0 votes.
FAQ
Who is lisaross-claude-code-plugins for?
Claude Code users, especially solo builders, who need to split monolithic project rules into organized modular files.
When should I use lisaross-claude-code-plugins?
Use it during project setup or refactor when your CLAUDE.md or clauderules file is hard to edit and you want a sustainable directory structure.
How do I add lisaross-claude-code-plugins to my agent?
Register lisaross/claude-code-plugins as a Claude Code marketplace, install the lone plugin, then follow its migration flow on your repo’s rules files.
Comments
Share how you use lisaross-claude-code-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.