<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frontend on Vibe Coding</title><link>https://vibecoding.rest/tags/frontend/</link><description>Recent content in Frontend on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/frontend/index.xml" rel="self" type="application/rss+xml"/><item><title>v0</title><link>https://vibecoding.rest/tools/v0/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/v0/</guid><description>&lt;p&gt;v0 generates production-ready frontend code from a prompt, a rough sketch, or a screenshot. It leans on Tailwind CSS and shadcn/ui, so the output looks polished by default and drops straight into a Next.js project.&lt;/p&gt;</description></item><item><title>Artifacts Builder</title><link>https://vibecoding.rest/skills/artifacts-builder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/artifacts-builder/</guid><description>&lt;p&gt;The Artifacts Builder skill covers the conventions for producing standalone, self-contained interactive outputs — inlined styles and scripts, responsive layout, no external dependencies that would break in a sandboxed viewer.&lt;/p&gt;</description></item><item><title>Frontend Design</title><link>https://vibecoding.rest/skills/frontend-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/frontend-design/</guid><description>&lt;p&gt;The Frontend Design skill packages a design-lead mindset for building web UI: pin down the subject and its audience, build a compact token system — palette, type pairing, layout concept, one signature element — then critique that plan against known AI-generic defaults before writing any code.&lt;/p&gt;</description></item><item><title>Figma</title><link>https://vibecoding.rest/mcp-servers/figma/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/figma/</guid><description>&lt;p&gt;Figma&amp;rsquo;s Dev Mode MCP server exposes a selected frame or component&amp;rsquo;s structure, styles, and metadata directly to a coding agent, from either the Figma desktop app or a hosted endpoint. It lets an agent generate frontend code grounded in the real design file instead of a screenshot or description of it.&lt;/p&gt;</description></item><item><title>Superflex</title><link>https://vibecoding.rest/tools/superflex/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/superflex/</guid><description>&lt;p&gt;Superflex converts Figma frames or plain screenshots into frontend code, tuned specifically to match the conventions and components already present in a target codebase rather than generating generic markup.&lt;/p&gt;&#10;&lt;h2 id="why-it-stands-out"&gt;Why it stands out&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Codebase-aware generation&lt;/strong&gt;, matching existing component patterns and styling conventions instead of producing one-off code.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Screenshot-to-code support&lt;/strong&gt;, working from a plain image when there&amp;rsquo;s no Figma file available.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;IDE integration&lt;/strong&gt;, delivering generated code inside the editor developers already use rather than a separate export step.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="good-for"&gt;Good for&lt;/h2&gt;&#10;&lt;p&gt;Frontend teams who want design-to-code output that actually matches their existing component library, not generic boilerplate.&lt;/p&gt;</description></item></channel></rss>