the current version is 0.2.2

[PRIMARY] This is the main tool for all designs. Operates in TWO modes:

Mode 1 — Get layout overview (sectionIndex NOT provided): Returns the list of all sections with id, name, type, nodeCount, and a page-absolute bounding box (x, y, width, height) for each section, plus totalSections and totalNodes. Also returns rootMetadata (root layer width/height/name/type/fill) when available. Use this FIRST to understand the design scope. The per-section bbox tells you exactly where each section sits inside the root container — use it for absolute positioning when generating code. Example: { "fileId": "123", "layerId": "456:789" }

Mode 2 — Get section DSL (sectionIndex provided): Returns the full DSL for ONE specific section.

• PATH nodes have their svgHtml stripped. After fetching ALL sections, call mcp__getDesignSvgs to retrieve them.

IMPORTANT workflow:

1. First call WITHOUT sectionIndex to get the section list with node counts.

2. Then call WITH sectionIndex=0, sectionIndex=1, ... up to totalSections-1.

3. You MUST fetch ALL sections. Do NOT skip any section index.

4. CRITICAL: Fetch sections in BATCHES of 3-5 at a time. Do NOT request all sections simultaneously — too many concurrent requests will cause timeouts. Send 3-5 sectionIndex calls, wait for all results, then send the next batch.

5. After fetching all sections, call mcp__getDesignSvgs to get SVG icons.

6. Generate the complete HTML with all SVG data.

DO NOT call mcp__getDsl after completing this workflow — all data is already provided. If this tool returns an error (e.g. old server), fall back to mcp__getDsl.

You can provide either:

1. fileId and layerId directly, or

2. a short link (like https://{domain}/goto/LhGgBAK)

After fetching ALL sections via mcp__getDesignSections, call this tool to retrieve all cached SVG HTML strings. Each PATH node in the DSL has an id. Look up that id in the returned svgs map to get the complete SVG string. Insert the svgHtml string directly into HTML where icons should appear.

You can provide either:

1. fileId and layerId directly, or

2. a short link (like https://{domain}/goto/LhGgBAK)

After fetching ALL sections via mcp__getDesignSections, call this tool to retrieve exact text content for large text nodes. In the section DSL, TEXT nodes with long content (>50 chars) have their "text" field replaced with a key like "T{sectionIndex}|{nodeId}". This tool returns the original text mapped by those keys. You MUST use the exact text from this response — never invent, paraphrase, or translate text.

You can provide either:

1. fileId and layerId directly, or

2. a short link (like https://{domain}/goto/LhGgBAK)

[FALLBACK] Use only when mcp__getDesignSections is unavailable or returns an error. This returns the FULL DSL in one response — may be large and exceed context limits for complex designs. Prefer mcp__getDesignSections as the primary tool for all designs. You can provide either:

1. fileId and layerId directly, or

2. a short link (like https://{domain}/goto/LhGgBAK) This tool returns the raw DSL data that you can then parse and analyze. Use the optional 'format' parameter (json/yaml/tree, defaults to json) to control the serialization. This tool also returns the rules you must follow when generating code. The DSL data can also be used to transform and generate code for different frameworks.

使用此工具从 MasterGo 获取 D2C 数据，并在本地落盘： 1）将返回的 code 写入 html； 2）将返回的 svg / image 资源按 resourcePath 落盘到对应目录； 3）返回落盘摘要，避免把大体积资源塞进上下文。

使用此工具将代码文件发送到 MasterGo MCP 服务进行 C2D（代码转设计）处理，将用户代码同步到设计稿。

参数说明：

• filePath：HTML 文件的完整路径（如 /path/to/file.html），工具会自动读取文件内容并发送给后端。

• fileId： 不提供 shortLink 时至少需要 fileId。layerId 不是必填，没有就不要传。

• layerId： 可选。图层 ID（只读取 URL 参数 layer_id）。不传或解析不到则仅按 file 维度同步；pageid/page_id 不会被当作 layerId。

• shortLink：可选，短链接形式（例如 https://{domain}/goto/xxxx）。 注意事项：只允许使用 URL 中的 layer_id 参数作为 layerId，严禁将 pageid/page_id 等任何页面 ID 当作 layerId。 如果短链接或 URL 中没有解析出 layer_id，则不传 layerId。

工具会读取 filePath 指定文件的内容，并传给后端，附带 fileId 与可选的 layerId。

When the data returned by mcp__getDsl contains a non-empty componentDocumentLinks array, this tool is used to sequentially retrieve URLs from the componentDocumentLinks array and then obtain component documentation data. The returned document data is used for you to generate frontend code based on components.

Use this tool when the user intends to build a complete website or needs to obtain high-level site configuration information. You must provide a fileld and layerld to identify the specific design element. This tool returns the rules and results of the site and page. The rules is a markdown file, you must follow the rules and use the results to analyze the site and page.

Users need to actively call this tool to get the component development workflow. When Generator is mentioned, please actively call this tool. This tool provides a structured workflow for component development following best practices. You must provide an absolute rootPath of workspace to save workflow files.

Users need to actively call this tool to get the Flutter component development workflow. When Flutter Generator or Flutter Component is mentioned, please actively call this tool. This tool provides a structured workflow for Flutter component development following best practices. It includes MasterGo DSL to Flutter Widget mapping rules, screen adaptation with flutter_screenutil, and feature-based architecture guidance. It also downloads all image resources from the design file to local disk, rewrites CSS and DSL references to point at Flutter asset paths, and generates an asset manifest. You must provide an absolute rootPath of workspace to save workflow files.

Extract SVG data from MasterGo design files. This tool retrieves the DSL from a design layer, finds all PATH nodes (typically inside INSTANCE/icon components), resolves their color references, and generates SVG markup strings. You can provide either:

1. fileId and layerId directly, or

2. a short link (like https://{domain}/goto/LhGgBAK) Returns { count, svgs: [{ name, id, svg }] } — one entry per icon/instance found in the design.