Figma field guide · designer workflow
Use the smallest Skill that matches the job. Keep Phoenix Core as the source of truth, review every result on the canvas, and let the Skill support—not replace—design judgement.
/phoenix-design improves, compares and checks selected designs, including requested states and optional brief coverage, using verified Phoenix assets.
Try: “Compare these two assistance states and stress-test the hierarchy using Phoenix Core.”
/phoenix-content replaces placeholders and stress-tests layouts with realistic enterprise data, awkward cases and protected product language.
Try: “Test this disruption flow with long locations, urgent guidance and localisation.”
/phoenix-handoff cleans selected work and runs a concise, designer-led engineering-readiness check with optional annotations.
Try: “Check this flow for handoff blockers and annotate only the non-obvious decisions.”
/phoenix-comments-to-tasks turns actionable Figma page comments into a verified, deduplicated canvas task list.
Try: “Convert the actionable comments on this page into tasks and keep their source context.”
Recommended sequence
Start with a deliberate selection in Figma. Run only the Skill that matches the job. Inspect the canvas result, keep evidence-backed changes, and involve an engineer when the decision affects implementation. Phoenix remains the source of truth.