Open Design
Register nexu-io/open-design so your coding agent reaches a local-first design workspace over MCP with 139 skills and file/preview tools.
Overview
open-design is a plugin marketplace for the Build phase that connects coding agents to a local Open Design app over MCP with 139 skills and file tools.
What is this marketplace?
- 1 plugin: Open Design MCP server (stdio) backed by local od daemon
- 139 skills plus projects, files, and preview tools for agent-driven design work
- Local-first: design app stays on your machine; agents connect through stdio MCP
- Requires od CLI on PATH (Homebrew, npm, or DMG install per marketplace copy)
- nexu-io maintained marketplace schema aligned with Claude Code marketplace.json
- 1 plugin in marketplace
- 139 skills advertised in plugin description
- MCP transport: stdio; requires local od daemon
Community signal: 62.3k GitHub stars.
What problem does it solve?
Agents cannot see or update real design files when assets live in a separate desktop app with no stdio bridge to the repo.
Who is it for?
Solo builders using Open Design locally who want Claude Code to read and act on design projects without cloud design APIs.
Skip if: Teams with no Open Design install or builders who only need CSS tweaks inside the repo with zero design-app integration.
What do I get? / Deliverables
After installing nexu-io/open-design and od, your agent accesses projects, files, previews, and 139 design skills through one MCP marketplace plugin.
- Registered open-design MCP plugin with stdio transport
- Agent reachability for design projects, files, preview, and 139 listed skills
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Open Design exposes a local design app to coding agents via MCP; the canonical shelf is Build frontend because agents pull layouts, files, and previews while implementing UI. frontend matches design-to-code workflows; the MCP plugin serves projects, files, preview, and a large skill surface rather than backend or CMS configuration.
How it compares
MCP-integrated design marketplace with 139 skills, not a static frontend-design SKILL.md or a CMS plugin.
Common Questions / FAQ
Who is Open Design for?
It is for developers running nexu-io’s Open Design app locally who want agent access via MCP and a large bundled skill library.
When should I use Open Design?
Use it when UI work spans a local design tool and your codebase and you need previews, files, and agent skills in one install.
How do I add Open Design to my agent?
Install od on PATH, then add the nexu-io/Open Design marketplace plugin with your agent’s plugin command so the stdio MCP server starts with sessions.