Coding agents

• The MCP server (https://wingo-ui.com/mcp) answers with everything that changes: components, props, usage, blocks, design rules, tokens and the changelog. It ships with every release.
• The rule files are short and stable: use the MCP tools, prefer blocks for whole screens, install with the CLI, check for updates first.
• The CLI writes the files, installs components and merges updates.

In your project:

npx wingo-ui@latest login                     # once per computer, for Pro components
npx wingo-ui@latest agents install claude     # or codex, gemini, grok, cursor, all

Running it again changes nothing. It never touches text outside its own marked blocks, and keeps the other servers in your MCP configs.

Use --scope user to write your user config instead (for Claude Code the CLI prints the claude mcp add --scope user command).

• --mcp http connects the agent straight to https://wingo-ui.com/mcp. The configs read the key from WINGO_UI_API_KEY in each agent's own syntax (${WINGO_UI_API_KEY}, ${env:WINGO_UI_API_KEY} in Cursor, bearer_token_env_var in Codex), so the key never lands in the repository. This is the default when the variable is set.
• --mcp stdio starts npx -y wingo-ui@latest mcp, a local proxy that uses the key saved by wingo-ui login. No environment setup, works in every agent that runs local commands. This is the default otherwise.
• Without a key both work too: docs for everything and the source of free items.

This block goes into CLAUDE.md, AGENTS.md or GEMINI.md. Claude Code also gets a skill with the full workflow, Cursor a project rule.

<!-- wingo-ui:start v=1 -->
## Wingo UI

This project builds its UI with Wingo UI (React 19 + Tailwind CSS v4 components installed as source, see `wingo-ui.json`).

- Before writing UI, use the `wingo-ui` MCP tools: `search_components` to find what exists (blocks for whole screens), `get_component` / `get_block` for props and usage, `get_design_rules` for tokens, sizes, motion and mobile rules. Never recreate a component the library has.
- Install with `npx wingo-ui@latest add <slug...>`. At the start of UI work run `check_updates` (or `npx wingo-ui@latest outdated`) and mention updates; update with `npx wingo-ui@latest update`.
- Semantic tokens only (`bg-background`, `bg-surface`, `text-muted-foreground`, `border-border`), configure components through props, keep `cn()`, `data-slot` and license headers in copied files. Check 390px and 1440px, light and dark.
- No MCP tools available? The CLI has `search`, `info`, `add`, `outdated`, `update`; the docs for models are at https://wingo-ui.com/llms.txt.
<!-- wingo-ui:end -->

The plugin bundles the skill and the stdio MCP server, for teams that prefer plugins over project files. It carries the same rules as agents install claude.

/plugin marketplace add wingo-ui/wingo-ui-claude
/plugin install wingo-ui@wingo-ui

• New components, changed props and new design rules reach your agent through the MCP server the moment a release ships.
• The rule files carry a version (now v1). npx wingo-ui@latest agents status shows whether yours are current and agents update refreshes them from https://wingo-ui.com/agents/manifest.json.
• The rules tell the agent to run check_updates at the start of UI work, so it mentions component updates on its own.
• Edited a managed file and want to keep it? Delete its wingo-ui:managed line and updates leave it alone.

The same files, for copying by hand:

• /agents/SKILL.md
• /agents/AGENTS.md
• /agents/CLAUDE.md
• /agents/GEMINI.md
• /agents/wingo-ui.mdc
• /agents/manifest.json

6 files across 5 agents, rules v1.