design-lab
v0.2.0See real components before deciding: /design-lab:preview renders 2-3 candidate variants with the project's OWN components on its own dev server (Vite React/Vue/Nuxt or Laravel Blade/Livewire, scratch surface removed at cleanup, strict consent gate, shell-mockup fallback for greenfield); and two MCP servers read component registries from the source, never from memory — a dependency-free local one for Aceternity, shadcn and Magic UI (24h-cached, every answer carrying its source URL, fetch date and stale flag, 3D/particle runtimes flagged) plus ReUI's own hosted server, delivered by install and authenticated by the user's own browser sign-in.
By Ivan-WG1 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 5, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install design-lab for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install design-lab@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/galaykos/cc-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/design-lab/.
Plugin files
├── .claude-plugin/plugin.json├── skills/real-preview/SKILL.md└── .mcp.json
Included Skills1
Use when a visual or UI decision needs REAL component fidelity — the project's actual design-system components, true typography, spacing and states — beyond token-mimicking static mockups. Vite (React or Vue/Nuxt) and Laravel Blade/Livewire; scratch entry, strict consent, guaranteed cleanup. Greenfield or non-Vite/non-Laravel stacks fall back to the taskmaster shell mockup — no sandbox is stood up.
MCP servers2
- command
- node
- args
- ${CLAUDE_PLUGIN_ROOT}/mcp/server.mjs
- url
- https://mcp.reui.io
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "design-lab",
"version": "0.2.0",
"description": "See real components before deciding: /design-lab:preview renders 2-3 candidate variants with the project's OWN components on its own dev server (Vite React/Vue/Nuxt or Laravel Blade/Livewire, scratch surface removed at cleanup, strict consent gate, shell-mockup fallback for greenfield); and two MCP servers read component registries from the source, never from memory — a dependency-free local one for Aceternity, shadcn and Magic UI (24h-cached, every answer carrying its source URL, fetch date and stale flag, 3D/particle runtimes flagged) plus ReUI's own hosted server, delivered by install and authenticated by the user's own browser sign-in.",
"author": {
"name": "Ivan-WG",
"email": "[email protected]"
},
"keywords": [
"ui-ux",
"frontend",
"tooling",
"research",
"navigator"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[design-lab on Agent Plugins Marketplace](https://pluginsmp.com/plugins/design-lab)