Claude Code plugins
8 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
8 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplace13 tool skills: rules writer, ticket writer, agent creator, skill writer, skill measure, plugin creator, research, brainstorming, communication style, PR message writer, report writer, stakeholder update writer, and UI review
Architecture analysis, brainstorming, 12-Factor compliance, ADR generation, and LLM-as-judge
Local fine-tuning for your own tasks, except the one doing the training is you. Operate Lore with use-lore, brainstorming-lore, create-area, create-project, create-bot, save-to-lore, transmute-lore, stale-lore, and vespi.
Comprehensive research co-pilot — literature review, methodology, ethics review, data analysis, qualitative coding, brainstorming, manuscript drafting, replication design, grant writing, talk building, citations, survey design, and peer review.
researchTurns dense legal documents, matter notes, and brainstorming dumps into clear, editable Mermaid diagrams to make strategizing and communicating clearer and faster. Use timelines and Gantt charts to uncover chronology gaps, flowcharts and decision trees to map litigation paths and negotiation possibilities, and entity relationship or class diagrams to clarify ownership, control, and corporate structure. Upload source files (.md, .docx, .pdf, .xlsx, or .pptx), paste text, or describe the issue you’re working on. /legal-diagram guides you through a simple interactive process to setup the skill and create timelines, Gantt charts, org charts, obligation checklists, litigation flowcharts, decision trees, corporate structure diagrams, and more.
8 software development skills: code review, TDD, debugging, git worktrees, brainstorming, subagent-driven development
Use when the user needs ideas or a name — brainstorming, naming, developing an idea further, hybridizing ideas, stress-testing candidates, reframing a problem, or picking a final direction. Ideas persist in a per-topic logbook across sessions.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.