| name | figma-weather |
| description | Accepts a Figma frame URL, analyzes AI-readiness across 4 dimensions, and delivers the verdict as a weather forecast — ☀️ 快晴 to 🌀 台風. |
| argument-hint | <figma-url> |
| allowed-tools | mcp__plugin_figma_figma__get_design_context, mcp__plugin_figma_figma__get_metadata |
Figma Weather Forecast
Analyze the Figma frame URL provided in $ARGUMENTS and evaluate whether it is structured in a way that allows AI to implement it accurately — then deliver the verdict as a weather forecast.
Output language: Respond in the same language the user is using in this conversation.
Step 1: Parse the URL
Extract from $ARGUMENTS:
figma.com/design/:fileKey/...?node-id=X-Y → fileKey and nodeId (convert X-Y to X:Y)
Step 2: Fetch data
Call get_design_context and get_metadata in parallel:
get_design_context: retrieves generated code, screenshot, annotations, and style infoget_metadata: retrieves layer hierarchy and node ID structure
Parameters for get_design_context:
disableCodeConnect: trueclientLanguages: "unknown"clientFrameworks: "unknown"
Step 3: Analyze across 4 dimensions
Dimension A: Layer naming
Good naming criteria:
- Meaningful names representing section or role (e.g.
Hero, CardBase, Footer)
- Elements inside components have role-based names (e.g.
HeroHeading, CTA, Button)
- No duplicate names among sibling elements
Problem patterns (checklist):
Dimension B: Auto-layout usage
Good state criteria:
- Auto-layout is applied to vertical and horizontal groups
- Spacing is managed via padding and gap (not manually positioned)
Problem patterns (checklist):
Dimension C: Variables and tokens
Good state criteria:
- Colors are defined as Figma variables and applied (generated code contains
var(--name))
- Spacing (margins, sizes) is managed with tokens
- Text styles are defined and applied (e.g.
heading/level_1)
Problem patterns (checklist):
Dimension D: Component and instance structure
Good state criteria:
- Repeatedly used elements are componentized
- Instances are used consistently (not manual copies)
Problem patterns (checklist):
Step 4: Output the report
Use the following format:
Figma Weather Forecast ⛅
File: [file name]
Target node: [node name] (nodeId)
Screenshot: [display the screenshot]
Overall score: X / 20
| Dimension | Score | Rating |
|---|
| A. Layer naming | X / 5 | 🟢 Good / 🟡 Room for improvement / 🔴 Needs fixing |
| B. Auto-layout | X / 5 | 〃 |
| C. Variables & tokens | X / 5 | 〃 |
| D. Component structure | X / 5 | 〃 |
Scoring criteria (5 points each):
- 5: No issues
- 3–4: Minor issues (1–2 items)
- 1–2: Needs improvement (3+ items)
- 0: Almost entirely unaddressed
🌤️ 本日のFigmaお天気
Based on the total score, select one weather and deliver it with its comment. Output the weather section prominently, like a weather broadcast.
| Score | Weather | EN comment | JA comment |
|---|
| 18–20 | ☀️ 概ね晴れ模様 | "So this is what a real Figma looks like…" — the AI whispers, then skips to work humming cheerfully. | 「これが本物のFigmaというものか…」と呟き、ルンルン気分で取りかかります。 |
| 13–17 | 🌤️ 晴れ時々曇り | The AI notices the clouds but is choosing to say nothing. A true professional. | AIはご機嫌です。うっすら雲が見えていますが、見なかったことにしています。プロですから。 |
| 8–12 | ☁️ どんより曇り空 | The AI exhales slowly and rolls up its sleeves. "I've seen worse," it lies. | AIがため息をつきながら実装を開始します。「まあ、できないことはない」という顔をしていますが、目が笑っていません。 |
| 3–7 | 🌧️ 土砂降りの雨 | The AI is staring into the void. Please bring snacks. Completion time: unknown. | AIが画面の前でフリーズしています。缶コーヒーを差し入れると少し動くかもしれません。作業完了まで今しばらくお待ちください。 |
| 0–2 | 🌀 台風注意報 | Mandatory evacuation in effect. The AI has already left the building. This file may be cursed — approach with caution and low expectations. | 避難指示が発令されました。AIはすでに荷物をまとめて退避済みです。このFigmaファイルは呪われている可能性があります。速やかに距離を置いてください。 |
Format the weather block like this (adapt language to the conversation):
## [weather emoji + weather name]
> [comment]
Strengths
(List notable practices in this file that others can learn from)
Improvement suggestions
For each issue:
[Location / target of the issue]
- Problem: What is wrong
- Impact: How it hinders AI code generation
- Suggestion: Specific action to take in Figma
Summary
(1–2 sentences on the overall impression and the highest-priority improvement)
Error handling
- If fileKey or nodeId cannot be extracted from the URL: ask the user to provide a valid Figma frame URL
- If
get_design_context or get_metadata returns an error: report the error and ask the user to check access permissions for the Figma file
- If a component URL is passed instead of a frame URL: inform the user and suggest trying with a frame-level URL
