@atomixstudio/mcp 1.0.31 → 1.0.33

package/README.md

@@ -62,15 +62,13 @@ Once connected, the AI can call these tools:
 | `listTokens(category)` | List all tokens in a category |
 | `searchTokens(query)` | Search tokens by name or value |
 | `validateUsage(value)` | Check if a hardcoded value should use a token |
-| `syncAll(options?)` | Sync tokens, AI rules, skills (.cursor/skills/atomix-ds/*), and atomix-dependencies.json. One tool for full project sync. **/--sync** invokes this. Optional: `output` (default ./tokens.css), `format` (default css), `skipTokens` (if true, only skills + manifest). |
+| `syncAll(options?)` | Sync tokens, AI rules, skills (.cursor/skills/atomix-ds/*), and atomix-dependencies.json. One tool for full project sync. **/--sync** invokes this. Optional: `workspaceRoot` (project root so files are written in the repo; else `ATOMIX_PROJECT_ROOT` env or cwd), `output` (default ./tokens.css), `format` (default css), `skipTokens` (if true, only skills + manifest). |
 | `getAIToolRules(tool)` | Generate AI coding rules for your design system |
 | `exportMCPConfig(tool)` | Get MCP configuration for different tools |
 | `getSetupInstructions(tool)` | Get detailed setup guide |
 | `getDependencies(platform?, stack?)` | Get suggested dependencies (icons, fonts, SKILL.md, token files). Optional: `platform` (web, ios, android), `stack` (e.g. react, vue, next). Use with **/--get-started** prompt. |
 | `syncToFigma()` | Push design system to Figma (variables, paint styles, text styles, effect styles). Uses built-in bridge + Atomix plugin. If the plugin is not connected, the response includes `agentInstruction` to connect. **Available on all tiers (Free and Pro).** |
 
-Other Figma tools (getFigmaVariablesAndStyles, createDesignPlaceholder, resolveFigmaIdsForTokens, designCreateFrame, designCreateText, etc.) are **Pro only** — they appear when the design system owner has a Pro subscription.
-
 ### getDependencies
 
 Returns DS-derived suggestions so the AI can build a "Suggested" vs "Already present" list and, after user approval, install or copy assets.
@@ -82,7 +80,6 @@ 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-SKILL.md`) and `content` (design-in-Figma skill: principal product designer, correct token use, prefer existing Figma variables).
 - **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.
 
@@ -90,7 +87,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`, `FIGMA-SKILL.md`), and **atomix-dependencies.json**. The manifest records icon library, font families, and paths. The **/--sync** prompt invokes it. Optional: `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 **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).
 
 **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.
 
@@ -106,7 +103,6 @@ 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** | Design UI in Figma: **3 passes** (wireframe → tokens/rules → audit), **getDesignScreenshot** after each pass, then **finalizeDesignFrame** (rename + ✅, remove placeholder) and summarise. No code generation. **Pro only.** |
 
 ## --get-started (get started)
 
@@ -121,13 +117,13 @@ 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 (1) a generic SKILL at `.cursor/skills/atomix-ds/SKILL.md` (coding-platform agnostic; calls `getAIToolRules` for the current environment), and (2) a **Figma design skill** at `.cursor/skills/atomix-ds/FIGMA-SKILL.md` for designing in Figma using granular MCP commands (syncToFigma, resolveFigmaIdsForTokens, designCreateFrame, designCreateText, etc.) with no code generation.
+**SKILLs:** The get-started flow suggests adding a generic SKILL at `.cursor/skills/atomix-ds/SKILL.md` (coding-platform agnostic; calls `getAIToolRules` for the current environment).
 
 ## Sync to Figma
 
 **/--sync-to-figma** (or the **syncToFigma** tool) pushes your design system into the open Figma file: color variables, paint styles, number variables (spacing, radius, borders, sizing, breakpoints), text styles, and shadow effect styles. The **Figma bridge runs inside this MCP server** (no separate process). You only need the Atomix Figma plugin and "Connect to Cursor" (no Figma REST API or token).
 
-**Tier:** Sync to Figma is available on **all tiers** (Free and Pro). The design-in-Figma prompt and design tools (getFigmaVariablesAndStyles, createDesignPlaceholder, resolveFigmaIdsForTokens, designCreateFrame, etc.) require a **Pro** subscription for the design system owner.
+**Tier:** Sync to Figma is available on **all tiers** (Free and Pro).
 
 **Flow:**
 
@@ -141,17 +137,6 @@ The **/--get-started** prompt suggests dependencies for your design system so yo
 3. **Connect** — In the plugin UI, tap **Connect to Cursor** and wait until the status shows "Connected".
 4. Run **Sync to Figma** again.
 
-## Design in Figma
-
-**/--design-in-figma** designs in the open Figma file using **granular MCP commands** (no script execution) and a **three-pass flow**:
-
-1. **Setup:** **syncToFigma** → **createDesignPlaceholder** (save `frameId`) → **getAIToolRules** + **listTokens** → **resolveFigmaIdsForTokens**.
-2. **Pass 1 — Layout and contents (wireframe):** Build structure with designCreateFrame, designCreateText, designCreateRectangle, designSetAutoLayout, designSetLayoutConstraints, designAppendChild. You must use auto-layout/fill/hug. Then **getDesignScreenshot** and check the image; 
-3. **Pass 2 — Apply design tokens and AI rules:** Set all fills and text styles from the resolved map; follow getAIToolRules for all design foundations. Prioritise colors, typography, and buttons. No hardcoded values only use Figma variables. Then **getDesignScreenshot** and verify. 
-4. **Pass 3 — Confirm no hardcoded values:** Audit that every value uses an id from resolved. **getDesignScreenshot** again, then **finalizeDesignFrame** with `frameId`, `name` (e.g. "Login card ✅"), and `fillVariableId`/`fillPaintStyleId` for surface (removes placeholder gray). Summarise what was built.
-
-**If the bridge is not reachable:** ensure the Atomix plugin is running in Figma and **Connect to Cursor** is clicked; leave the plugin open. The MCP server (and bridge) must be running in Cursor.
-
 ## Token Categories
 
 - **colors** — Brand, background, text, icon, border, action, feedback (light + dark)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atomixstudio/mcp",
-  "version": "1.0.31",
+  "version": "1.0.33",
   "description": "MCP server for Atomix Design System - query your design foundation and tokens for AI coding tools",
   "type": "module",
   "main": "dist/index.js",