@corva/ui 3.58.0-1 → 3.58.0-2

package/MCP_README.md

@@ -8,6 +8,7 @@ supports Claude Code, Cursor, and Codex CLI.
 - [Overview](#overview)
     - [Available Tools](#available-tools)
     - [Usage](#usage)
+    - [Available Prompts](#available-prompts)
 - [Setup](#setup)
     - [Quick Setup](#quick-setup)
     - [Local Setup (Recommended)](#local-setup-recommended)
@@ -21,7 +22,9 @@ supports Claude Code, Cursor, and Codex CLI.
 
 ### Available Tools
 
-- `search_corva_ui` - Search components, hooks, utils by name or description
+- `search_corva_ui` - Search components, hooks, utils by name or description. When the requested `category` (`v2` or
+  `v1`) has no match, the response surfaces a labeled fallback block from the other version so a single search still
+  discovers a candidate.
 - `get_component_docs` - Get detailed component documentation with props and examples
 - `get_hook_docs` - Get hook documentation
 - `get_theme_docs` - Get theme/styling documentation
@@ -41,6 +44,38 @@ No special keywords required. The AI automatically uses these tools when you ask
 
 Mentioning `@corva/ui`, component names, or asking about the design system triggers the MCP automatically.
 
+### Available Prompts
+
+MCP prompts are surfaced as slash commands in clients that support them. In Claude Code they appear under
+`/mcp__corva-ui__<name>`.
+
+- `figma_to_code` — Translate a Figma node into React components that follow `@corva/ui` conventions. Orchestrates the
+  Figma Dev Mode MCP (for design context and Code Connect mappings) and the `@corva/ui` MCP tools above (for component,
+  icon, theme, and hook lookups).
+
+**Argument** (optional; the assistant asks if missing):
+
+- `input` — Freeform request. Paste the full Figma node URL (e.g.
+  `https://www.figma.com/design/<fileKey>/...?node-id=<nodeId>`) together with any extra context: target path or
+  directory in the app, an existing file to extend, naming preferences, edge cases. The assistant extracts the URL
+  itself.
+
+> A single freeform argument is intentional: Claude Code's MCP-prompt bridge splits positional string arguments on
+> whitespace, so a multi-arg schema would only capture the first token of each.
+
+**Example invocation** (Claude Code):
+
+```
+/mcp__corva-ui__figma_to_code https://www.figma.com/design/ABC/Sample?node-id=1-2 create under src/apps/drilling/RigStatusCard.tsx
+```
+
+**Prerequisite:** the Figma Dev Mode MCP must be enabled in the same client session so the prompt can call
+`mcp__figma__get_design_context`. Enable it via Figma Desktop → Preferences → Enable Dev Mode MCP Server, then restart
+your client.
+
+**Scope:** primarily consumer mode — app repos that depend on `@corva/ui` and import from its entry points. Authoring
+mode (inside the `@corva/ui` repo itself) is auto-detected from `package.json` and adjusts output conventions.
+
 ## Setup
 
 > **Just generated a fresh project with the latest `create-corva-app`?** MCP is already configured for Claude Code,
@@ -274,7 +309,9 @@ Node lives inside WSL, so where you point the MCP config depends on where the *M
     "corva-ui": {
       "command": "wsl.exe",
       "args": [
-        "-e", "bash", "-lc",
+        "-e",
+        "bash",
+        "-lc",
         ". \"$HOME/.nvm/nvm.sh\" && exec corva-ui-mcp"
       ]
     }
@@ -396,7 +433,9 @@ lives in WSL, write to `~/.cursor/mcp.json`:
     "corva-ui": {
       "command": "wsl.exe",
       "args": [
-        "-e", "bash", "-lc",
+        "-e",
+        "bash",
+        "-lc",
         ". \"$HOME/.nvm/nvm.sh\" && exec corva-ui-mcp"
       ]
     }
@@ -467,7 +506,9 @@ Find your global install's path with `npm prefix -g`, then substitute it below:
   "mcpServers": {
     "corva-ui": {
       "command": "node",
-      "args": ["<npm-prefix>/lib/node_modules/@corva/ui/mcp-server/server.mjs"]
+      "args": [
+        "<npm-prefix>/lib/node_modules/@corva/ui/mcp-server/server.mjs"
+      ]
     }
   }
 }