| name | mastergo-mcp-reader |
| description | Read and structure MasterGo design data through configured MCP tools for Android feature implementation. Use when user provides a MasterGo link and asks to extract specs, page structure, component details, spacing, states, copy, and interaction rules, then convert them into dev-ready tasks/checklists. |
MasterGo MCP Reader
Workflow
- Confirm inputs:
- MasterGo file URL
- target pages/frame ids (if provided)
- platform (Android by default)
- Prefer local MCP stdio fetch first with this command:
npx -y @mastergo/magic-mcp --token=$env:MASTERGO_TOKEN --url=https://mastergo.com- After MCP initialize, call
mcp__getDsl with fileId + layerId (preferred) or shortLink.
- Parse IDs from URL when needed (example:
file/166007320435232 + layer_id=1109:05949).
- Use MCP capability to fetch page/frame data (nodes, text, sizes, interactions, assets).
- Normalize output into these sections:
- 页面清单（page/frame）
- 组件清单（组件名、层级、状态）
- 视觉规格（尺寸、间距、颜色、字号）
- 文案规格（标题、按钮、toast、错误文案）
- 交互流程（入口、分支、成功/失败/回退）
- 研发注意项（系统能力、边界、降级策略）
- Produce implementation-ready artifacts:
- Android任务拆分（P0/P1）
- 验收清单（QA steps）
- 待确认问题（ambiguities）
Output Template
Use this output structure for each feature:
- 功能概览
- 页面与状态机
- 字段与文案表
- 交互与错误处理
- Android实现清单（类/页面/埋点）
- 测试用例
- 未决问题
Rules
- Prefer source-of-truth from MCP design data over screenshots.
- Keep exact text/copy from design; do not paraphrase product copy unless asked.
- Mark uncertain values explicitly as
TODO(DesignConfirm).
- If MCP read fails, fallback to browser snapshot/manual extraction and label as fallback.
- For Android delivery, map design nodes to current code entry points before proposing new pages.
