claude-figjam 1.0.0 → 1.2.0

package/dist/tools.js

@@ -45,7 +45,7 @@ export const deleteNodesSchema = z.object({
     node_ids: z.union([z.string(), z.array(z.string())]),
 });
 export function registerTools(server, bridge) {
-    server.tool("figjam_read_board", "Returns full board state: all nodes with IDs, types, positions, content, and colors.", {}, async () => {
+    server.tool("figjam_read_board", "Returns full board state: all nodes with IDs, types, positions, content, and colors. ALWAYS call this before making any changes to understand the current state of the board. After a page switch, call this again to confirm you are on the correct page before writing.", {}, async () => {
         try {
             const result = await bridge.execute("read_board", {});
             return {
@@ -62,7 +62,7 @@ export function registerTools(server, bridge) {
             };
         }
     });
-    server.tool("figjam_create_node", "Creates any FigJam node (sticky, shape, text, section, table, code_block). Returns the new node ID.", {
+    server.tool("figjam_create_node", "Creates any FigJam node (sticky, shape, text, section, table, code_block). Returns the new node ID. IMPORTANT: For multi-line content, use actual newline characters in the string — do NOT use \\n escape sequences, as they will render literally. LAYOUT RULES: Use a 4px grid — all x/y positions and width/height values must be multiples of 4. Minimum vertical gap between stacked nodes = 80px. Minimum horizontal gap between pipeline stages = 328px. Use shape nodes as group containers instead of sections (sections cannot be resized programmatically). Container pattern: create container shape first (color #f0f2ff, 48px padding all sides), then child nodes on top. When a node connects both up and down in a column, place the upstream target ABOVE the hub node to separate TOP/BOTTOM slot usage. width+height must both be passed together to resize — passing only one is silently ignored. Decision nodes (branching logic) should use shape=diamond and be positioned as fan-out hubs far to the left of all their branch targets.", {
         type: z.enum([
             "sticky",
             "shape",
@@ -71,14 +71,22 @@ export function registerTools(server, bridge) {
             "table",
             "code_block",
         ]),
-        content: z.string().optional().describe("Text content"),
+        content: z
+            .string()
+            .optional()
+            .describe("Text content. Use real newline characters for line breaks, not \\n."),
         x: z.number().optional().describe("Canvas x position"),
         y: z.number().optional().describe("Canvas y position"),
         width: z.number().optional(),
         height: z.number().optional(),
         color: z.string().optional().describe("Hex color"),
+        font_size: z
+            .number()
+            .optional()
+            .describe("Font size in pixels (text nodes only)"),
         shape: z
             .enum([
+            "rounded_rectangle",
             "square",
             "rectangle",
             "ellipse",
@@ -89,7 +97,7 @@ export function registerTools(server, bridge) {
             "cross",
         ])
             .optional()
-            .describe("Required when type=shape"),
+            .describe("Shape style when type=shape. Defaults to rounded_rectangle if omitted."),
         rows: z
             .number()
             .int()
@@ -122,7 +130,7 @@ export function registerTools(server, bridge) {
             };
         }
     });
-    server.tool("figjam_create_connector", "Draws a connector (arrow/line) between two existing nodes by their IDs.", {
+    server.tool("figjam_create_connector", "Draws a connector (arrow/line) between two existing nodes by their IDs. LAYOUT RULES: Always use style=elbowed (default) — elbowed connectors route around nodes better than curved. For fan-out from a hub node, place the hub far enough left/right that |dx| > |dy| for ALL targets, forcing clean horizontal routing. When adding a node to an existing column, restack ALL column nodes with even 80px gaps. Cross-layer connectors that would cut through container shapes are a layout problem — fix by repositioning nodes or using annotation instead of drawing the connector. CONNECTOR SEMANTICS: only use connectors for data flow relationships. Configuration or contextual relationships should be annotated in the node label instead (e.g. '⚙ configures X') — connectors imply flow. CONNECTOR LABELS: always label decision branch connectors with the branch condition (e.g. '2D image', 'video', '>250MB'). Label key flow transitions to describe what changed (e.g. 'registers asset', 'thumbnail_path set'). Labels are not needed on obvious convergence arrows where multiple paths merge to a single result node.", {
         from_id: z.string().describe("Source node ID"),
         to_id: z.string().describe("Target node ID"),
         style: z
@@ -155,11 +163,15 @@ export function registerTools(server, bridge) {
     server.tool("figjam_update_node", "Edit any property of an existing node. Pass only the fields that need to change.", {
         node_id: z.string().describe("ID of the node to update"),
         content: z.string().optional(),
-        x: z.number().optional(),
-        y: z.number().optional(),
-        width: z.number().optional(),
-        height: z.number().optional(),
+        x: z.coerce.number().optional(),
+        y: z.coerce.number().optional(),
+        width: z.coerce.number().optional(),
+        height: z.coerce.number().optional(),
         color: z.string().optional().describe("Hex color"),
+        font_size: z.coerce
+            .number()
+            .optional()
+            .describe("Font size in pixels (text nodes only)"),
     }, async (params) => {
         try {
             const result = await bridge.execute("update_node", params);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-figjam",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "MCP server for live FigJam board editing from Claude Code",
   "type": "module",
   "bin": {