Walk into any design team in 2026 and the AI is already there. A Figma plugin is generating component variants. An agent is rewriting microcopy across a brand audit. Asset generators are spitting out hero images in five aspect ratios. The work is real. The problem is what happens after. Variations land as Slack screenshots. The brief lives in a doc no one updates. The agent's reasoning, the prompts that worked, the rejected directions, the brand reviewer's QA notes, all of it evaporates between Figma comments and Loom recordings. By the time eng asks why a spacing decision was made, the trail is gone.
The gap is not the one you might assume. Figma is the canvas. Adobe Creative Cloud, Sketch, Webflow, and Framer stay the source of truth for design files. Dock is the system of record for the agent's interpretive work around those files: the brief, the variation analysis, the brand QA findings, the handoff notes. Rows carry pointers like figma_file_id or webflow_collection_id, and the agent's output lives next to the pointer. Persistent. Resumable. Reviewable. Canvas tools render pixels. Dock holds the decisions.
Three workflows make this concrete.
Brief to variation to publish. A PM drops a brief into a Dock surface. The brand agent reads it, picks up the library via the official Figma MCP, and drafts six hero variations in a working file. Each returns as a Dock row with a figma_node_id pointer, a rationale, and a confidence score. Design lead approves two, rejects four with one-line reasons. Approval triggers a publish handoff to Webflow via a community MCP wrapper. Rejected variations stay in the row with reasoning intact, so the next brief does not re-litigate the same dead ends. The drafted-by-agent pattern, applied to pixels.
Brand audit across files. Marketing wants every customer-facing surface checked. An agent walks the org's Figma files via REST, Webflow collections via wrapper, and the Adobe asset library via Adobe's REST endpoints. Findings land as Dock rows: file pointer, frame coordinates, deviation type, severity, suggested fix. Brand lead filters by severity, assigns owners, watches the queue burn down. The audit is a workspace, not a PDF.
Handoff spec with linked frames. Design hands off to eng. The doc holds references to specific Figma frames, accessibility notes the agent flagged, and a thread that survives the sprint. Engineers ask inline; the agent answers from original brief context. The handoff stops being a one-way throw. The shared workspace primitive at a cross-functional seam.
Why design specifically. Three reasons. Cross-functional handoff is where design work goes to die, and fragility compounds when an agent is in the mix and no one can reconstruct what it was told. Brand consistency at scale needs attributed findings, a list of rows with file pointers ready for assignment. And agent-generated visual content needs provenance for legal review. A workspace that retains the prompt, the model, the brief, and the approver is what will hold up. Dock surfaces are how, the same way agent-rendered HTML makes rich review possible inside the workspace, and the shape cap argument explains why constraint is what makes it work.
This is not an AI assistant for designers. It is an AI workspace where canvas tools keep doing what they do and the agent's contribution finally has somewhere to live. For the workflow-craft companion, see how design teams work with AI. Otherwise: open /use-cases/design, or fork a design template and point it at one Figma file.
FAQ
Does Dock replace Figma? No. Figma stays the canvas and the source of truth for design files. Dock holds the brief, the agent rationale, the reviews, and the handoff notes. Rows carry figma_file_id pointers; the pixels stay in Figma.
How do agents read from Figma? Through the official Figma MCP and the public REST API. For Webflow, agents use community MCP wrappers. Adobe Creative Cloud is reached through Adobe's REST endpoints. Agent-readiness varies by platform, and Dock surfaces are tolerant of that.
Where do brand reviews live? As Dock rows with file pointers, frame coordinates, severity, and assignee. Reviewers filter and assign. The audit is a queue, not a deck.
What about asset versioning? Versioning stays in the canvas tool. Dock holds the decision log: which version was approved, by whom, against which brief, with which agent rationale. The two layers compose; neither tries to be the other.
Sources:
- Figma Developer Docs (REST API)
- Figma, design statistics 2026. 85% of designers and developers say AI will be essential to their future success; 78% report AI tools significantly speed up their workflows.