@atomixstudio/mcp 1.0.34 → 1.0.35

package/README.md

@@ -80,6 +80,7 @@ Returns DS-derived suggestions so the AI can build a "Suggested" vs "Already pre
 - **iconLibrary** — `package`, `nativePackage`, and a performance hint (use individual imports; apply the DS icon sizing/weight token when rendering icons).
 - **fonts** — Font family names from typography tokens + hint to link fonts via URL (e.g. Google Fonts); no need to download or add font files to the repo.
 - **skill** — `path` (e.g. `.cursor/skills/atomix-ds/SKILL.md`) and `content` (generic, platform-agnostic SKILL.md).
+- **skillFigmaDesign** — `path` (`.cursor/skills/atomix-ds/figma-design-SKILL.md`) and `content` (Figma design skill: advisory and generative UI on the Figma canvas).
 - **tokenFiles** — e.g. `["tokens.css", "tokens.json"]` with copy instructions.
 - **meta** — `dsName`, `platform`, `stack`, `designSystemVersion`, `designSystemExportedAt`. Use `designSystemVersion` to compare with skill frontmatter `atomixDsVersion` and suggest **syncAll** when the design system is newer.
 
@@ -87,7 +88,7 @@ If the design system is unavailable, the tool may fail; the client should tell t
 
 ### syncAll
 
-**syncAll** is the single sync tool: tokens file, AI rules, skills (`.cursor/skills/atomix-ds/SKILL.md`), and **atomix-dependencies.json**. The manifest records icon library, font families, and paths. The **/--sync** prompt invokes it. All paths are resolved under a project root so files are written **inside the repo** (committable). Project root is: `workspaceRoot` argument → `ATOMIX_PROJECT_ROOT` env → `process.cwd()`. Optional: `workspaceRoot` (absolute path to repo root), `output` (default `./tokens.css`), `format` (default `css`), `skipTokens` (if true, only writes skills and manifest).
+**syncAll** is the single sync tool: tokens file, AI rules, skills (`.cursor/skills/atomix-ds/SKILL.md` and `.cursor/skills/atomix-ds/figma-design-SKILL.md`), and **atomix-dependencies.json**. The manifest records icon library, font families, and skill paths. The **/--sync** prompt invokes it. All paths are resolved under a project root so files are written **inside the repo** (committable). Project root is: `workspaceRoot` argument → `ATOMIX_PROJECT_ROOT` env → `process.cwd()`. Optional: `workspaceRoot` (absolute path to repo root), `output` (default `./tokens.css`), `format` (default `css`), `skipTokens` (if true, only writes skills and manifest).
 
 **Skill versioning:** Synced skills get frontmatter `atomixDsVersion` and `atomixDsExportedAt` (from the design system at sync time). The manifest’s `skills.syncedAtVersion` matches. The AI can compare the skill’s `atomixDsVersion` to **getDependencies**’ `meta.designSystemVersion`; if the design system is newer, it can suggest running **syncAll** to update.
 
@@ -103,6 +104,7 @@ Run these prompts from your AI tool (e.g. **/--hello**, **/--get-started**):
 | **/--sync** | Sync tokens, AI rules, skills files, and dependencies manifest (icons, fonts). Use **/--refactor** to migrate deprecated tokens. |
 | **/--refactor** | Migrate deprecated tokens in codebase. Run after **/--sync**. |
 | **/--sync-to-figma** | Push design system to Figma. Requires bridge + Atomix plugin; see [Sync to Figma](#sync-to-figma) below. **Available on all tiers (Free and Pro).** |
+| **/--design-in-figma** | Load the Figma design skill and use the **designInFigma** MCP tool to design UI in the connected Figma file (catalog, query, execute). **Pro only.** |
 
 ## --get-started (get started)
 
@@ -117,7 +119,7 @@ The **/--get-started** prompt suggests dependencies for your design system so yo
 5. **Optional: suggest global typeset** — If the project has no global styles that use the design system tokens, offer to build a full typeset (Display, Heading, body, caption) from the DS typography tokens via getToken/listTokens, including fontFamily, fontSize, fontWeight, lineHeight, letterSpacing—not just font imports.
 6. **Report what was created** — After any install/copy steps, list what was created or updated (e.g. "Installed: lucide-react. Added: .cursor/skills/atomix-ds/SKILL.md. Synced: tokens.css.").
 
-**SKILLs:** The get-started flow suggests adding a generic SKILL at `.cursor/skills/atomix-ds/SKILL.md` (coding-platform agnostic; call `getRules` for governance rules). Run /--sync to write the skill; .rules files (e.g. .cursorrules) are no longer written.
+**SKILLs:** The get-started flow suggests adding two skills: `.cursor/skills/atomix-ds/SKILL.md` (generic, platform-agnostic; call `getRules` for governance rules) and `.cursor/skills/atomix-ds/figma-design-SKILL.md` (Figma design — advisory and generative UI). Run /--sync to write both skills; .rules files (e.g. .cursorrules) are no longer written.
 
 ## Sync to Figma
 
@@ -130,6 +132,12 @@ The **/--get-started** prompt suggests dependencies for your design system so yo
 1. **Plugin not connected?** The tool checks first. If the plugin is not connected, the response includes `bridgeNotRunning`, `agentInstruction`, and `userInstruction`. Ensure Cursor has this MCP server running, then in Figma run the Atomix plugin and click **Connect to Cursor**, then call **syncToFigma** again.
 2. **Only if that fails** should the user check MCP configuration and plugin connection manually.
 
+## Design in Figma
+
+**/--design-in-figma** (or the **designInFigma** tool) loads the Figma design skill into context and directs the AI to use the designInFigma MCP tool to create or edit UI in the connected Figma file. The prompt injects the full Figma design skill content and instructs the agent to call designInFigma with `action: "catalog"` first, then `"query"` (e.g. get_selection, get_design_screenshot) or `"execute"` (design steps).
+
+**Tier:** Design in Figma is **Pro only**. Free users do not see this prompt or the designInFigma tool in their MCP session.
+
 **User steps (when needed):**
 
 1. **Ensure MCP is running** — Cursor should have this MCP server configured and running (the bridge is built in; no separate bridge process).