agentsclimarketplace

Create figjam content

Skill southleft/skills-for-figma/skills/create-figjam-content

Open-source agent skills for the native Figma MCP server — design tokens, components, accessibility, Slides, and FigJam.

Install
npx -y skills add southleft/skills-for-figma --skill create-figjam-content

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Author FigJam boards with granular control — sticky notes (single + batch), connectors between nodes, shapes-with-text, sections, tables, code blocks, and auto-arrange — plus read back board contents and the connection graph. Use when the user wants to build or edit a FigJam board element-by-element. Triggers: 'add stickies to FigJam', 'create a flowchart/diagram in FigJam', 'connect these nodes', 'make a section/table/code block in FigJam', 'auto-arrange the board', 'read what's on the FigJam board', 'map the connections'. More granular than the native generate_diagram (which produces a whole diagram in one shot). FigJam files only (figma.editorType === 'figjam'). Requires the Figma Desktop app (Plugin API).

SKILL.md

3.5 KB, as published. Nobody here has run it

create-figjam-content — author & read FigJam boards

Build FigJam boards one element at a time and read them back. Covers stickies (single + batch), connectors, shapes-with-text, sections, tables, code blocks, auto-arrange, plus get board contents and get connections. This gives you fine-grained control when the native one-shot generate_diagram is too coarse (e.g. you want specific colors, positions, magnets, or to extend an existing board).

Skill boundaries

  • use_figma rules — load the official figma-use skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level await + return (no IIFE, no figma.closePlugin(); console.log is not returned), inputs inlined as const at the top of each script, colors in 0–1 range, load fonts before any text op, await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).
  • One complete snippet per operation → references/figjam-snippets.md.
  • Whole-diagram generation in one call → use the native generate_diagram tool instead.

Workflow

  1. Confirm it's a FigJam file. Every op throws outside FigJam. Check first: return { editorType: figma.editorType }; — it must be 'figjam'.
  2. Pick the operation from references/figjam-snippets.md: create sticky / stickies / connector / shape-with-text / section / table / code block, auto-arrange, or read board contents / connections.
  3. Run the snippet via use_figma (skillNames: "create-figjam-content"), editing the inlined constants (text, position, color, node IDs).
  4. Connectors need real node IDs. Create the nodes first, capture their returned IDs, then create connectors referencing those IDs (start/end + magnets).
  5. Return created IDs and, after a batch, read the board back (get board contents) to confirm.

Notes

  • Fonts must be loaded before text. Stickies, shapes-with-text, table cells, and connector labels all write text — each snippet await figma.loadFontAsync(...) before setting .characters, with an Inter fallback where the default font may be unavailable.
  • Sticky colors use a named palette (YELLOW, BLUE, GREEN, PINK, ORANGE, PURPLE, RED, LIGHT_GRAY, GRAY); other colors fall back to the default sticky fill.
  • Shape shapeType values: SQUARE, ROUNDED_RECTANGLE, ELLIPSE, DIAMOND, TRIANGLE_UP, TRIANGLE_DOWN, PARALLELOGRAM_RIGHT, PARALLELOGRAM_LEFT, etc.
  • Connector magnets: AUTO, TOP, BOTTOM, LEFT, RIGHT.
  • These tools require the Figma Desktop app (the Plugin API isn't available in the browser).

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.