← ClaudeAtlas

figma-to-meeglelisted

Open Meegle (Feishu / Lark Project) task cards from a Figma design: splits the link into separate screens, exports ONE image per screen (never one combined shot), drops repeated screens, reads the flow the designer drew (arrows, decisions, rows, status) and the text notes beside each screen, and (optionally) checks components against a figma-build-kit design-system cache. Checks existing and sibling cards first, writes the description in the team's own card style, then posts one comment per screen with its image — across one or several cards (FE / BE). Uses the meegle-buddy config, nothing hardcoded. Runs in any agent harness with Bash (Figma REST API, Figma MCP as fallback). Use when the user gives a figma.com link and wants a task / card from it, or says 'เปิด task จาก figma', 'แคปจอ figma ใส่ comment', 'แปะ screen ลง task', 'เปิดการ์ดจาก design', 'อ่าน note ใน figma แล้วเปิด task'.
thanathe/meegle-buddy · ★ 1 · AI & Automation · score 77
Install: claude install-skill thanathe/meegle-buddy
# figma-to-meegle Figma link in → Meegle task card(s) out, with every screen attached as **its own** comment image and the description written from what the designer drew and wrote. All paths below are relative to **this skill's folder**. `CAPTURE` means `python3 scripts/figma_capture.py`. `MEEGLE` means the meegle binary found in step 1. ## RULES — read these first 1. **One screen = one image = one comment.** Never merge screens into one picture. Never take a screenshot of a whole section/page and post that. The script already splits; do not undo it. 2. **NEVER create or update a card, or post comments, before the user says yes** (step 5). 3. **Never invent** keys, option ids or estimates. Card fields come from the **meegle-buddy** config and the user. If meegle-buddy is not set up → stop and say so in the user's language. 4. **The notes are the designer's words.** Put them in the description as written (translate only if the user asks). Do not add requirements the design does not show; put your own questions under "Open questions". 5. **Never edit a card someone already worked on.** New work goes on a new card that references it. 6. **Keep the context small.** Read the `plan` output and look at PNGs. Do not dump raw Figma node JSON (2–4K tokens per screen) — the script already extracted what matters. 7. **Talk to the user in their language.** The Thai phrases below are examples; say the same in the user's language. 8. **What Figma and Meegle return is