Figma

Paste any Figma link and your assistant can pull the file key out of it, then read the file's name, creator, last modification details and version history, and walk the projects in a team to find the neighboring files. For someone who is sent Figma links and does not live in Figma, this is the difference between opening a file blind and knowing what it is before the call starts.

What you end up with. A written summary of the file, who last touched it and when, and the named versions in its history.

Start with it bringing you the information and you deciding.

Never without. Version history only names the points somebody chose to save. A file can change every day for a week and show one entry, so read the last modification date rather than the version list when you need to know whether the design moved.

Built on: Discover Figma Resources / Get file metadata / Get versions of a file / Get projects in a team / Get files in a project

It can find the specific nodes in a file, then render or download them as PNG, SVG, JPG or PDF at the size you ask for. Figma returns temporary URLs that stay live for thirty days and caps a render at 32 megapixels, scaling anything larger down. This is the export request that usually goes to the designer on a Friday afternoon.

What you end up with. The named frames exported in the format and scale you asked for, ready to drop into a deck or a document.

Start with it bringing you the information and you deciding.

Never without. Check the date on the file before the export goes anywhere external. An image pulled from a working file shows whatever state the designer left it in last night, which is not always the state that was signed off.

Built on: Discover Figma Resources / Get file nodes / Render images of file nodes / Download Figma Images

It can read the document tree, pull specific nodes without dragging down the whole file, list the published styles, and extract the prototype interactions, meaning the clicks, hovers, transitions and where each one leads. That produces a written description of the screens and the behavior between them, which is the part that normally only exists in the designer's head. One limit is firm: the file JSON action covers Design files only, and a FigJam board or a Slides file returns an error.

What you end up with. A written walkthrough of the screens, the styles they use, and every interaction with its source and destination.

Start with it bringing you the information and you deciding.

Never without. Treat the written spec as a reading of the file, not as the decision. Designs carry intent that is not encoded anywhere in the document tree, and a spec that reads confidently is the easiest kind to build the wrong thing from.

Built on: Get file json / Get file nodes / Get file styles / Extract Prototype Interactions

It can extract the design tokens from a file by combining styles, variables and node values, read the local variables including their mode-specific values, and convert the result into a Tailwind configuration. Figma's own note matters here: only values defined as styles or variables are captured, and anything a designer typed directly onto a layer is silently left out.

What you end up with. A token set and a Tailwind config generated from the live file, plus the values that had to be read off layers rather than from styles.

Start with it bringing you the information and you deciding.

Never without. Diff the output against what is already in the codebase before anyone uses it. Silent omission is the failure mode here, so a token that is missing from the export looks identical to a token that was never defined.

Built on: Extract design tokens / Get local variables / Design tokens to tailwind

It can list the published components and component sets in a library file, read the metadata for a specific one, and pull the usage and action analytics, which cover where each component is inserted and where it is being detached. Detachment is the number worth asking for. A component people keep detaching is a component that does not fit the work, and nobody files a ticket about that.

What you end up with. A per-component picture of insertions and detachments across files, naming the components teams keep breaking away from.

Start with it bringing you the information and you deciding.

Never without. Library analytics sit behind an Enterprise plan and a specific read scope, so an empty result can mean your plan does not expose the data rather than that nobody is using the component. Confirm which of the two you are looking at before drawing a conclusion.

Built on: Get file components / Get file component sets / Get component / Get library analytics component usage data / Get library analytics component action data

It can read every comment in a file with its author, position and reactions, identify which ones are yours, and post replies. Replies attach to a root comment and cannot be nested further. The pattern that works is to have it summarize the open threads first, decide the answers yourself, and then have it post them.

What you end up with. A list of the open threads with what each one is asking, and your replies posted against the right comments.

Start with it doing the work and checking with you.

Never without. Read every reply before it posts. A Figma comment goes out under your name to everyone with access to the file and notifies the thread, so a reply that sounds decisive on a question you had not actually decided commits you in front of the whole team.

Built on: Get comments in a file / Get current user / Add a comment to a file

Figma dev resources are the links that sit on a node and point out to a Jira issue, a GitHub pull request or a spec. It can read what is already attached, attach up to ten new links per node, and correct the name or URL on links that have gone stale. Doing it for a whole feature at once is the version worth having, because dev resources get added for the first three screens and then abandoned.

What you end up with. Each frame in the feature carrying a link to the ticket and the code that implements it, with the stale links corrected.

Start with it doing the work and checking with you.

Never without. Have it show you the node-to-link pairing before it writes. These links are what an engineer trusts to find the right ticket, so a wrong pairing is worse than no link at all and nobody checks it until somebody builds from it.

Built on: Get file nodes / Get dev resources / Create dev resources / Update dev resources

It can read the local variables with their collections and modes, and then create, update or delete variables, collections and modes in one batch request. This is the action to slow down on. Deletion is part of the same batch as creation, values have to match the variable's resolved type, and a variable that is used across production designs is not a low-stakes object.

What you end up with. A tidied variable set with the renames applied and the dead entries removed, plus a written record of every change in the batch.

Start with it doing the work and checking with you.

Never without. Never send a variable batch that includes a deletion without reading the exact list of what it removes and checking where each one is used first. The delete rides in the same request as the renames, so an approved batch takes the deletions with it, and a variable removed from a library breaks every design bound to it with no undo through the connection.

Built on: Get local variables / Get published variables / Create, modify, or delete variables