zlacker

[parent] [thread] 3 comments
1. shosta+(OP)[view] [source] 2025-05-06 15:28:37
What does your tool and model stack look like for this?
replies(1): >>ramesh+f1
2. ramesh+f1[view] [source] 2025-05-06 15:35:27
>>shosta+(OP)
Cline with Gemini 2.5 (https://cline.bot/)

Framelink MCP (https://github.com/GLips/Figma-Context-MCP)

Playwright MCP (https://github.com/microsoft/playwright-mcp)

Pull down designs via Framelink, optionally enrich with PNG exports of nodes added as image uploads to the prompt, write out the components, test/verify via Playwright MCP.

Gemini has a 1M context size now, so this applies to large mature codebases as well as greenfield. The key thing here is the coding agent being really clever about maintaining its' context; you don't need to fit an entire codebase into a single prompt in the same way that you don't need to fit the entire codebase into your head to make a change, you just need enough context on the structure and form to maintain the correct patterns.

replies(1): >>jjani+oc
◧◩
3. jjani+oc[view] [source] [discussion] 2025-05-06 16:35:48
>>ramesh+f1
The designs itself are still done by humans, I presume?
replies(1): >>ramesh+9G
◧◩◪
4. ramesh+9G[view] [source] [discussion] 2025-05-06 19:40:33
>>jjani+oc
>The designs itself are still done by humans, I presume?

Indeed, in fact design has become the bottleneck now. Figma has really dropped the ball here WRT building out AI assisted (not driven) tooling for designers.

[go to top]