reqwise-figma-mcp: Skill for Claude Code

/figma-state — What a record is allowed to be

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 a state machine.

Goal

Turn a status field into a contract. A spec says status: draft | pending | approved | rejected and stops; the questions it never answers are which change is allowed from which, what triggers it, and what has to be true first. That is what a developer needs to write the guard clause and a tester needs to know what to try.

Output: one Figma frame State · <title> for one entity, plus the transition questions the diagram exposed.

Constraints

Hard rules — never violate

• One entity per diagram. Two lifecycles on one canvas is two diagrams sharing a frame, and every reader loses track of which state belongs to which. Draw the second one separately.
• Exactly one kind: "initial", and at least one kind: "final" unless the entity genuinely never ends (a session, a switch). The tool reports both.
• Every transition needs a reason — see the table below. This is the rule the tool checks hardest, and the one specs leave out most often.
• Use the states the SYSTEM uses. If the DB stores pending_review, the id is pending_review and the label is what a human calls it ("Chờ duyệt"). A diagram whose state names do not match the data is a diagram nobody can implement against.
• Never invent a transition to connect an orphan. A state nothing can reach is a finding about the spec, not a missing arrow.

Write it in the compact form

text is one line per thing, and the transition line is the UML sentence — which is what keeps event, guard and action three separate things instead of one string with the guard missing.

held   "Seats held"
  entry hold_expires_at = now() + 10 min
  detail booking_seats rows written
paying "Awaiting payment"
  do wait for the payment gateway
paid   "Paid" final ok                  # kind + class on the state line
void   "Released" final err
[*] -> held:   Reserve the seats / insert bookings
held -> paying: Confirm the order [payment method chosen] / insert payments
held -> held:   Change seats            # a self-transition is normal, not odd
paying ~> held: Gateway declined [attempts < 3] !err    # ~> is a way BACK
paying -> paid: Gateway confirmed
paying -> void: [attempts = 3]          # guard only, no event