Figma Launches New Design Features to Automate Coding
Design teams can now use integrated Markdown and code layers to standardize documentation and accelerate software production.
Updated on Oct. 15, 2026 in Remote Work

Live Poll
Would you use AI agents to automate and manage design tasks in your own workflow?
Figma introduced new Markdown-based design documentation tools and expanded beta access to its code layers feature. These tools aim to improve the predictability of AI-generated outcomes for remote design and engineering teams.
Why it matters
Design teams and software developers face increasing pressure to maintain consistency while scaling production. These tools allow operators to standardize design language and automate code generation to reduce manual handoff friction.
Figma reported a 17-times increase in lines of code produced and a 1.3-times rise in software releases using its integrated platforms. The firm now supports 20 tools via its Model Context Protocol and serves 40% of the top 100 companies on the Bombay Stock Exchange.
The players
Figma
A cloud-based design and collaboration platform that provides interface design, prototyping, and developer handoff tools for remote teams.
Payload
A headless content management system designed to provide developers with extensible and type-safe data handling capabilities.
The details
Figma Specs enables users to create Markdown documents within the design canvas to serve as a central reference for teams and AI agents. Concurrently, the code layers feature allows developers to convert design elements directly into functional code, enabling interactive prototypes. The company also integrated the Payload headless content management system to further automate the connection between design assets and final code implementation.
Timeline
Late 2025: Figma opened its first office in India.
June 2026: The company released its code layers feature in private beta.
October 15, 2026: Figma announced these new platform features at Config India.
Market Landscape
Figma is aligning its platform with the Model Context Protocol, a standard gaining traction for connecting AI models to external data systems. This strategy marks a pivot toward making design software the primary source of truth for AI-driven software development workflows.
Operators managing design-to-code workflows should monitor how these documentation tools impact sprint velocity and error rates. Teams currently using manual documentation should evaluate whether Figma Specs can consolidate their technical requirements and reduce the need for external asset handoffs.
The takeaway
The industry is shifting toward treating design files as functional code repositories rather than static visuals. Review your current developer handoff process to identify if automated conversion tools can eliminate repetitive documentation tasks.
Further reading
For more on managing distributed teams through software, visit Remote Work.
Live Poll
Would you use AI agents to automate and manage design tasks in your own workflow?








