Skip to main content
Glama
Sign In
SIN-Code-Frontend-Design-Skill

SIN-Code-Frontend-Design-Skill

by OpenSIN-Code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

design_figma_export

Export design tokens from source code into Figma Tokens JSON format for design handoff.

Instructions

Export extracted tokens to Figma Tokens JSON.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "design_figma_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource code with design tokens.
source_formatNoFormat of source (css|scss|tailwind|json|figma).css

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Only states export action without disclosing whether this is a write operation, permissions needed, side effects, or what happens to input. Minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise single sentence, front-loaded with action and output. Could benefit from slight structuring (e.g., listing input expectations), but efficient for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema existing, return value is partially covered, but description does not clarify whether export generates a file or returns JSON, or if tool is read-only or modifies state. Adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage), so baseline 3. Description adds no extra meaning beyond parameter names and types; e.g., no hints on format usage or validation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it exports extracted tokens to Figma Tokens JSON, distinguishing from sibling design_token_extract which extracts tokens. Specific verb+resource with output format indicated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage after token extraction, but no explicit when-to-use or when-not-to-use guidance. Does not reference alternatives or context for when to use this tool vs siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools