Scope the Selection
Aim the agent at one frame, not the whole file.
Design files are huge. Point the agent at one frame or component, not the whole document. Select the node in Dev Mode or paste a link to that exact selection, then ask for code. Narrow scope means the agent reads real structure instead of drowning in a thousand layers and inventing the rest.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Aim at One Frame
Your team's Figma file holds the entire product — 40-plus screens across a dozen pages. A teammate connected the Figma MCP server and prompted 'convert my Figma file to React.' Claude tried to read everything, got back an enormous blob of nodes, ran long, and produced a vague…
Other principles in Context
Declare the Tools You Need
Name the tool or MCP server by name, and say what to do if it isn't reachable.
Describe Before You Prescribe
Describe the Data Shape
Claude can't clean data it can't picture.
Explain the Integration Point
Keep Memory Reusable
Save patterns and preferences that survive across sessions; never save snapshots of finished work.
Map to Real Components
Use Code Connect so it reuses your components, not new markup.