Make Figma AI Your Daily Instrument

Workflow area: Figma AI & Prototyping · Tier: Foundation · Hands-on time: ~30 minutes

Most designers touched Figma's AI features once during a launch week and reverted to habit. That's a tooling loss but also a judgment loss: the features are unevenly good, and knowing which five minutes of your day each one deserves is a skill. The other half of this playbook is governance in miniature — a one-page convention that answers, before the argument happens, whether an AI-generated frame is allowed anywhere near production.

When to use — and when not to

• Use First Draft for zero-to-something momentsa blank frame for a stakeholder conversation in ten minutes, or unblocking a layout you can't start.
• Use rename-layers and smart search constantlynear-zero-risk, pure time reclamation; there is no artistic argument for hand-renaming 200 layers before handoff.
• Use Weave's image tools for exploration and placeholder workrestyles, image generation and edits while direction is still in motion.
• Skip First Draft for anything shipping this sprintits output is generic by design and isn't built from your components; it drafts, you design.
• Skip generation entirely in regulated or brand-critical surfaceslegal disclosures, consent flows, brand campaign assets: human-crafted, human-reviewed, no exceptions in the convention.

The recipe

1. 1.

   Run a 30-minute gauntlet to calibrate each feature. Take one real screen from your current project and, in order: First-Draft a variant from a text description; use make-an-image / replace-image for its hero asset; run rename-layers on your messiest frame; smart-search for a component you know exists under a wrong name; restyle a section with Weave. You're not producing work — you're producing calibration: a felt sense of what each feature is good for and where it lies.

2. 2.

   Score the gauntlet honestly. In Claude or a doc, one line per feature:

   Copy

   For each Figma AI feature I tested, I'm recording:
   FEATURE | WHAT IT DID WELL | WHERE IT FAILED | MY USE RULE
   Help me tighten these into one-line use rules a teammate could
   follow without having run the test:
   [PASTE YOUR FIVE ROUGH NOTES]
   

   Good output looks like:

   Copy

   First Draft   | fast plausible layouts | invented non-DS components,
   generic IA    | RULE: blank-page breaker + stakeholder sketches
   only; never pasted into working files
   Rename layers | 90% correct semantics  | mislabeled overlapping
   icons | RULE: run before every handoff, scan the diff once
   

3. 3.

   Draft the AI-allowed zones convention. This is the artifact the team actually needs:

   Copy

   Draft a one-page "AI-allowed zones" convention for a product design
   team using Figma's AI features. Structure:
   - GREEN (use freely, no review needed): [YOUR LIST — e.g. layer
     renaming, smart search, placeholder imagery in exploration files]
   - YELLOW (allowed as draft input; must be redesigned on-system
     before shipping): [e.g. First Draft output, Weave restyles]
   - RED (never AI-generated): [e.g. legal/consent copy, final brand
     assets, production components]
   For each zone: the reasoning in one sentence, and who can grant
   exceptions. Keep it to one page. Blunt language over policy-speak.
   

4. 4.

   Pressure-test the convention against last month. Walk three recent real deliverables and ask where each AI feature would have sat in the zones. If the convention would have banned something that was actually fine, or green-lit something that would have embarrassed you, adjust the zones — the document has to survive contact with real work before it's ratified.

5. 5.

   Ratify and pin it. Ten minutes in team critique: walk the page, take objections, edit live, done. Pin it in the team space and put a one-line pointer in every project file's cover page. A convention nobody can find governs nothing. Revisit quarterly — the feature set moves fast enough that zones drift.

Make it yours

• Solo designer version: skip ratification, keep the zones — a personal convention protects you from your own deadline-pressure exceptions, which is when AI output slips into production unexamined.
• Agency version: add a fourth zone per client — some client contracts prohibit generative tools on their IP entirely; the convention page per project states which client rules override house rules.
• ChatGPT or Claude as the quarterly reviewer: each quarter, paste the convention plus Figma's release notes and ask which new features need zoning — a standing 15-minute ritual that keeps governance current without a committee.

Quality check

• Every feature has a use rule from YOUR testnot from a launch blog; rules inherited from marketing are marketing.
• The zones are behaviorally specific"be careful with AI" governs nothing; "First Draft output never pastes into working files" governs.
• The RED zone is genuinely redif everything is negotiable, the convention is a mood; at least legal surfaces and production components should be non-negotiable.
• Layer names and file structure stayed semantic after AI passesspot-check that renamed layers describe intent, not appearance; pb-34's agent-readable files depend on it.
• The convention is findable in under ten secondsfrom any project file, by any teammate, or it isn't real.