New in Dev Mode, 19 Nov
Developers can now ask a Figma file how to build it
Step 1 of 7
Today's art direction
The Inspect Launch
A feature launch page whose hero is the product's own three panes.
A SaaS feature launch page that borrows its first screen from the tool it announces: a layers panel that doubles as the table of contents, a canvas holding the day's image, and an inspect panel carrying the pitch. Violet redlines and selection handles mark one icon the way a developer would select it.
Below the fold the layers become numbered steps on a single rule, so the page reads as one guided handoff. The ground is a cool crimson basket weave; the type is a soft slab for display over a sturdy text serif.
- Weave crimson
#B8123E - Sheet cream
#FBF3EA - Aubergine ink
#22101F - Redline violet
#5B2C8F - Blush label
#F6C6D2
Step 2 of 7
Dev Mode now takes questions
Figma's agent has worked in design files for months. Its 19 November release note moves it into Dev Mode, where developers can now ask about a design and get back explanations, code and export links instead of reading values off the inspect panel one at a time.
The help article lists four jobs. It explains how a component behaves and points out layers that could use a variable the file already has. It describes how to build a layout with CSS grid or flexbox, or writes a React snippet. It compares two versions of a component as a visual diff or as a written list of changes.
A Dev seat can ask the file anything and still cannot move a pixel.
Seats set the limits. A Dev seat can chat with the agent but cannot change the design, while a Full seat can also ask for edits. Credits scale with the task, and the agent runs in the desktop app and the browser, not on mobile.
Last week Dev Mode started copying 3D transforms as CSS. This release changes what the panel hands over: an approach to the layout, where it used to hand over values.
- Coming soon
- Vector editing and drawing tools, icon creation, slots, prototyping
- Not supported
- Exporting assets for you (it writes links instead); diagrams and charts, which go to FigJam AI
- Plans
- Professional and up; Dev Mode is not on Starter, and nothing runs on mobile
- Cost
- AI credits, scaled to the complexity of the task
| Ask about | What comes back | Dev seat | Full seat |
|---|---|---|---|
| Understanding | How a component's interactions work; layers that could use existing variables | Yes | Yes |
| Implementation | How to build it with CSS grid or flexbox, or a React snippet | Yes | Yes |
| Versions | A visual diff, or a list of changes in the chat | Yes | Yes |
| Export | Links to save icon components as SVG; CSS for variables | Yes | Yes |
| Edits | Changes to the design itself | No | Yes |

It writes the links, not the files
Ask for an icon set and the agent returns links that save each icon component as SVG, along with CSS for the file's variables. Figma lists exporting assets on your behalf as unsupported, so the download stays a click someone makes.
Step 3 of 7
Drop caps that move, and a multi-select that folds
Safari Technology Preview 257, out 18 November, makes the first-letter and first-line pseudo-elements animatable, and limits them to the properties the Pseudo-Elements spec allows. A drop cap can now ease into its hover color like any other element.
It also renders a multiple select with a size of one as a dropdown on macOS. An enhanced version that copies the chosen options into the button is in the preview behind a flag, a step past the styleable select Safari 27 shipped in September.
Further down the full release notes, print layout now uses 96 CSS pixels per inch instead of 90, so a page measured for the screen prints at the same scale.
On iPhone, that engine is the only one
In a post published today, Mozilla says no browser maker has shipped a non-WebKit engine on iOS under the conditions Apple set in the EU and Japan, which require a separate app and moving users over by hand. Until that changes, what WebKit ships is the CSS your iPhone visitors get.
Inspect a frame, ask how it was built, then compare it with last week's version before anyone writes a line of layout code.
Hover or focus. Where first-letter animates, the initial eases from crimson to violet; elsewhere it switches..specimen p::first-letter { float: left; font: 800 76px/.8 Solway, serif; color: #B8123E; transition: color .45s ease; } .specimen:hover p::first-letter { color: #5B2C8F; }
Step 4 of 7
Framer's agent paints its own shader input
Framer's 12 November update lets its site agent generate a custom image, texture or illustration for the page, or take one you drop in and swap the subject, remove the background or restyle it. The same agent writes shaders such as halftone, bokeh blur, CRT and a pencil effect, and adjusts one already on the canvas.
The two meet at the end of the entry: a generated image can be set as the input of an image shader. Framer's example turns a picture into a pen drawing that smudges as the pointer moves over it.
- Generates
- Images, textures, illustrations
- Edits
- Subject swap, background removal, restyle
- Shaders named
- Halftone, bokeh blur, CRT, pencil
- Combines
- A generated image as a shader's input
Step 5 of 7
A handoff routine for the agent in Dev Mode
Ask for structure first
Ask whether the frame wants grid or flexbox, and why, before asking for a snippet. The reasoning shows how the designer built it, which is the part worth checking.
Diff before you build
Compare the version you estimated against the version you received, and paste the change list into the ticket so scope changes are written down.
Collect links last
Generate the SVG links and the variable CSS once the diff is settled, so the assets you download match the design you are building.
Step 6 of 7
The design move
Borrow this pattern
Key every visual diff to a numbered change list
When a client approves two versions of anything, number each change on the new version and print the same numbers in a written list beside it. The reviewer reads the list and finds the pin, so nobody has to hunt for what moved. It suits approval pages, changelogs and redesign proposals.
- Pins sit on the new version only.
- One change per number, and the list says what changed in plain words.
- Keep plain before and after views one tap away, so the pins never hide the design.
.bench:not(:has(#v-changes:checked)) .pin {
opacity: 0;
}
.bench:has(#v-before:checked) .price {
font-size: 30px;
}
Studio plan
$19 per month
Three editors, unlimited client reviews.
Start free trial- Label added above the plan name.
- Price set larger, so it reads before the plan name.
- Button filled violet and relabelled Start free trial.
Step 7 of 7
Prompt Lab
Builds a SaaS feature launch page whose hero is the product's own layers, canvas and inspect panes. Paste it into Figma Make, Lovable, Claude, v0 or Beaver Builder AI.
Build a SaaS feature launch page for a new feature inside a design or developer tool. The hero is the product's own three-pane workspace, so the visitor sees the feature where it lives. Layout: 1. Top bar with the brand left and three plain text links right. 2. A breadcrumb rail as the masthead: a dark aubergine (#22101F) bar with radius 10px holding a breadcrumb list (chevrons drawn with CSS borders, not slashes) on the left and two labelled facts on the right (Published date, Read time). Monospace, 14px. 3. Hero: a solid cream kicker label, then a full-width slab headline (Solway 800, about 80px desktop, set to break in two lines, line-height 1). 4. Under the headline, a three-pane stage on a cream (#FBF3EA) panel with radius 14px and one tight shadow, the only shadow on the page: - Left, 200px: a "Layers" panel. Its list is the page's table of contents: real anchor links, each with a monospace step number, two indented child items, and a one-line footer pinned to the bottom. - Centre: a canvas on a slightly darker cream (#F2E5D8) holding the hero image. Above the image put a small monospace frame label row. Over one object in the image, draw a selection box in violet (#5B2C8F): 2px border, four small square handles, a violet name tag beside it and a small outlined tag below naming the export format. Mark it aria-hidden and explain it in the figcaption. - Right, 300px: an "Inspect" panel holding the deck, a filled violet button plus a text link, and a ruled dt/dd list of plan or seat facts. 5. Below the hero, sections run as numbered steps on one vertical blush rule at the left: each opens with a 56px cream square holding the step number in crimson, a "Step N of 7" monospace label and a slab h2. Use the same numbers as the Layers panel. 6. Vary the containers by step: cream cards for reading sections, one section set directly on the ground, one dark aubergine card for the pattern section, a ruled numbered list with large slab numerals for a routine, and a split card for the prompt (intro and copy button left, the prompt in a scrolling frame right). 7. Include one real comparison table (row headers, Yes/No columns in monospace) and one live demo: a segmented Before / After / Changes radio control that switches a small pricing card with :has(), showing numbered violet pins and a matching change list only in the Changes view. 8. Close with a two-column row: field note left, sources list right, under a 2px cream rule. Ground: a vivid cool crimson (#B8123E) with a basket-weave pattern from a 32px inline SVG tile of alternating horizontal and vertical bars in aubergine at about 8 percent opacity. No gradients, no glow. Type: Solway (500, 700, 800) for display; Petrona (400, 600, italic 400) for body; Victor Mono (400, 600) for labels, steps and code. One italic pullquote in violet-plum under a 2px violet rule. Palette: crimson #B8123E, cream #FBF3EA, aubergine #22101F, violet #5B2C8F for buttons and redlines only, blush #F6C6D2 for labels on the crimson ground. Guardrails: body text at least 18px with line-height 1.65 or more; reading columns about 690px; long prose sits on cream, not on crimson; every small label meets WCAG AA against its real background; violet is never used as text on crimson. Radius 14px for cards, 6 to 8px for labels and buttons, no pill shapes. No accent stripe borders, no fake search fields or toggles, no readable text inside images, no purple-blue gradients or neon. Hover and focus states on every link and button at about 150ms, and a prefers-reduced-motion guard. On mobile, the stage stacks with the canvas first, then inspect, then layers in two columns; the step rule disappears and the numbers sit above each heading; table rows stack into labelled cards; code blocks scroll sideways instead of wrapping.
Field note
The inspect panel was built to answer what a value is. Now it answers how the design should be built, and that is the question to ask before anyone asks for code.
Sources
- Figma release notes: Work with the Figma agent in dev mode (19 November 2026)
- Figma Help Center: Work with the Figma agent in design files
- WebKit: Release Notes for Safari Technology Preview 257 (18 November 2026)
- Apple Developer: Safari Technology Preview 257 release notes
- Mozilla: Apple's iOS browser engine rules (20 November 2026)
- Framer Updates: Image and Shader Generation (12 November 2026)