Do we have to create all of these rules and things for every project specifically? How can we automate everything in a way that maybe a Notion page?     See Less

why not use figma's official MCP?     See Less

magic ui price $200 It's very expensive.     See Less

You need at least a dev figma plan 20€ a month to get access     See Less

this is great. I think the final frontier now is Figma. How can we get the Figma designs in the first place? how do we get better at design and use ai tools to make figma designs or start th     See More     See Less

🎯 Key points for quick navigation:

00:00 🧭 The presenter has been testing a Figma → Cursor/Cloud Code workflow tha     See More s daily UI generation using a new Figma MCP and chassis MCP.
00:12 ⚡ The workflow lets you pull UI component libraries from multiple sources so you can generate varied, sophisticated UI styles, not just the default chassis.
00:27 🖼️ Figma MCP can implement a landing-page section nearly pixel-perfect in a couple of prompts, including downloading image/SVG assets.
00:41 🔧 Small manual tweaks (e.g., change an image, add a background color, add a border) are usually all that’s required after generation.
00:54 🎯 Side-by-side comparisons show generated UI often matches the Figma design ~100% after just two prompts.
01:09 📥 The Figma MCP’s asset download (images + SVG logos) is a standout feature that speeds integration.
01:23 🔑 Setup requires adding your Figma personal access token (read permissions) into the MCP tool—generate via Figma settings → security.
01:37 🧩 The chassis MCP server connects chassis-based UI component libraries (registries) so you can import many styled component sets (forms, magic UI, etc.).
02:06 ⚙️ The chassis MCP extracts available components and provides CLI commands and example usage to add them to your project.
02:21 🔗 If your Figma uses properly named chassis components, Figma MCP + chassis MCP can produce nearly pixel-perfect UIs end-to-end.
02:35 📁 You must have a project with chassis already installed; run the MCP init command to add chassis + MCP client (Cursor, Cloud Code, VS Code supported).
02:49 📝 Add an `agents.mmd` file to define agent rules for how tools and components should be used in generation.
03:03 🌐 Registries are hosted JSON files (components.json) listing components; add registry URLs so the MCP can read available libraries.
03:30 📂 If you don’t have a chassis template, upload one to MCP classrooms (chassis + Figma MCP session) to get a working starting point.
03:44 🔁 The flow: copy Figma frame link → paste into Figma MCP → it retrieves Figma data, checks connected libraries, and maps layer names to components.
04:09 🧱 The tool can automatically add matching components (tables, badges, cards) into your project to recreate the Figma layout.
04:36 🔍 Agents can search across registries to find appropriate components and auto-import example code into your project.
04:51 ✨ There are niche registries (animation packs, chat UI, text-editor libraries) you can mix-and-match to extend functionality.
05:18 🛠️ Example: adding a PL UI registry then asking the agent to build a text-editor UI results in a working sophisticated editor scaffold added to the project.
05:45 🔀 You can swap libraries to layer in fancy animations or alternate components for visual polish.
05:59 🏗️ You can publish your own UI component library and import it as a registry for reuse across projects.
06:14 📚 The presenter put full instructions and a chassis starter template on AI Builder Club for folks who want to try it.
06:29 📆 They run weekly workshops (next focuses on UI generation workflows); comment or join the AI Builder Club link for the session.

Made with HARPA AI    See Less

Awesome video     See Less

Never thought Id be diving into design like this. Jasons breakdowns are on point! Im doing similar stuff in my TripleTen UX/UI bootcamp now, using Figma and AI tools. Feels good seeing it al     See More     See Less

why bro stop posting?     See Less

Vibe designing apps are the future     See Less