reqwise-figma-mcp: Skill for Claude Code

/figma-activity — Who does what, and what gets handed over

Read ../reqwise-diagram-rules.md first — connection gate, the four levels of correct, the findings loop, frame placement, verification. This file carries only what is specific to an activity diagram.

Goal

Draw a process that crosses people. Approval, onboarding, fulfilment, escalation — anywhere the interesting failures are handoffs: the step that sits in someone's inbox, the rejection that goes back to the wrong person, the parallel work nobody waits for.

Output: one Figma frame Activity · <title>, plus the process questions the diagram exposed.

Constraints

Hard rules — never violate

• ASK which way it runs before drawing. rankdir: "LR" gives horizontal lanes — the classic swimlane, reading left→right. "TB" gives vertical lanes, reading top→bottom. It changes how the whole thing reads and it costs one question. Do not guess.
• With lanes, EVERY node needs a lane. A step nobody owns is exactly the bug this diagram exists to expose; it is drawn in a visible "(no lane)" band rather than quietly filed under the first lane.
• Drop lanes entirely for a single-owner process. Same notation, no bands. Do not invent a second lane to make it look like a swimlane.
• Label a lane-crossing edge with WHAT is handed over — "hồ sơ đã duyệt", "lý do từ chối" — not "next", not "tiếp theo", not nothing.
• A decision needs at least two ways out, each with a condition on the edge.
• Never invent a step. If the source stops at "rồi duyệt", that is the finding.

Write it in the compact form

text is one line per thing. The <lane>: prefix is the field this diagram exists for — who performs the step — and here it is two characters at the front of the line rather than a property buried in an object, so a missing owner is visible at a glance.

rankdir LR                                  # ask the user first — see Phase 2
lane cus "Khách hàng"
lane cvkh "CVKH" / chi nhánh
lane los "LOS" / external
cus:  s start "Nộp hồ sơ vay"
cvkh: check "Kiểm tra giấy tờ"
cvkh: enough ? "Đủ hồ sơ?"                  # ? = a decision
los:  score "Chấm điểm tín dụng"
cvkh: reject err "Từ chối | và nêu lý do"   # err = the failure path, | splits a detail line
cus:  done end "Nhận kết quả"
s > check "hồ sơ + giấy tờ"
check > enough
enough > score "đủ"                          # a decision branch MUST carry its condition
enough > reject "thiếu"
score > done "hồ sơ đã duyệt"                # a lane-crossing edge says WHAT crossed
reject ~> check "bổ sung giấy tờ"            # ~> = rework, routed outside the lanes