MAG Claude Plugins
MadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend
- 287 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The Frontend plugin wires in external Apidog, Figma and Chrome DevTools MCP servers with their own keys and access to designs and API docs
- The /implement slash command runs code, tests and a browser layout check without asking for confirmation at every step inside a phase
Install
- Works in
Manual install
/plugin marketplace add MadAppGang/claude-codeOne-time setup. After it, enable the plugins you need with /plugin install <name>@mag-claude-plugins.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The Frontend plugin wires in external Apidog, Figma and Chrome DevTools MCP servers with their own keys and access to designs and API docs
- The /implement slash command runs code, tests and a browser layout check without asking for confirmation at every step inside a phase
This is third-party code. Review the repository files before installing.
What it does
MAG Claude Plugins is a Claude Code plugin marketplace that the MadAppGang studio built out of its own project workflows. You add the marketplace once and enable plugins one by one in project settings. The Frontend Development plugin ships agents for CSS, design and UI work in TypeScript and React. It has an /implement command with eight phases, from architecture to final approval. The plugin wires in the Apidog, Figma and Chrome DevTools MCP servers. Bun Backend Development targets Hono, Prisma and one camelCase convention from the database to the frontend, with /implement-api and /apidog commands. Code Analysis adds an agent for exploring unfamiliar code plus semantic search. Orchestration contains skills only: rules for running subagents in parallel, quality gates and error handling.
Who it is for. For TypeScript, React and Bun teams working in Claude Code who want one shared set of agents, commands and rules.
Good fit when
- The team builds UI in React, TanStack and shadcn/ui and wants an /implement command that checks layout fidelity against Figma files
- A Bun and Hono backend needs one camelCase convention from the database to the API, with Apidog docs kept in sync
- A new developer enters a large unfamiliar repository and needs an agent that traces relationships between files and explains the architecture
- Several Claude Code subagents run in parallel and need ready rules for sequencing, quality gates and error recovery
Not a fit when
- Your stack is not TypeScript, React or Bun: the Frontend and Backend plugins are built around those
- You want Figma fidelity checks but the project has no Figma links: without them /implement skips step 2.5
- You need ready agents and commands for subagent coordination: the Orchestration plugin ships only rules and templates
Example request
Add the MadAppGang/claude-code marketplace and enable the Frontend Development plugin for this projectLimitations
- The Frontend and Backend plugins target a specific stack: React 19, Tailwind CSS 4, shadcn/ui on the frontend and Bun, Hono 4.6, Prisma 6.2 on the backend.
- The Apidog, Figma and Chrome DevTools MCP servers that the Frontend plugin wires in need their own setup and access keys.
- Orchestration's multi-model validation runs through the separate Claudish CLI. It is not part of this marketplace and needs its own OpenRouter API key.
- The figures about MadAppGang's own projects in the repository description cannot be verified from the code.
How to disable. Disable a plugin by setting enabledPlugins to false for it in the project's .claude/settings.json, or remove the marketplace with /plugin marketplace remove mag-claude-plugins.
FAQ
How do I install MadAppGang's Claude Code plugins?
Run /plugin marketplace add MadAppGang/claude-code once, then enable the plugins you need per project: /plugin install frontend@mag-claude-plugins, bun@mag-claude-plugins, code-analysis@mag-claude-plugins or orchestration@mag-claude-plugins. It helps to save the enabledPlugins list in .claude/settings.json and commit it.
Do I need a separate CLI for multi-model validation?
Yes. The multi-model-validation skill in the Orchestration plugin runs Grok, Gemini and GPT-5 through the Claudish tool. It ships in the neighboring MadAppGang/claudish repository and installs separately.
How is the Orchestration plugin different from Frontend and Backend?
Orchestration is a skills-only plugin: five files of rules for subagent coordination, quality gates and error recovery, with no agents or slash commands of its own. Frontend and Backend add actual agents and commands tied to a specific stack.
What does the Frontend plugin's /implement command do?
It runs implementation through eight phases. First come architecture planning, writing the code and a Figma fidelity check. Then a triple review (manual, AI and browser) and test generation. At the end you approve the result, and the command cleans up temporary files and delivers the finished feature with documentation.
Can I install just one plugin from the marketplace?
Yes, each of the four plugins installs with its own /plugin install <name>@mag-claude-plugins command and doesn't need the others. You can enable only Code Analysis or only Bun Backend Development, without Frontend or Orchestration.
Discussion
No questions or reviews yet.
Related
PluginsClaudeKit Skills
ClaudeKit - Agent Skills
A plugin marketplace for Claude Code with a set of thirty-plus skills: frontend, backend, devops, databases, documents, debugging and MCP work
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A marketplace of 18 Claude Code plugins: access to blocked pages, second-model review, design systems from a site, research and planning
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
A marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
A marketplace of Claude Code plugins for engineering workflows: feature planning, tests, review, git automation and a code execution runtime
README in short
The description opens with the story of the MadAppGang and 10xLabs studios and moves on to installation. Each of the four plugins is listed with its version, agents, commands and skills.