URL copied — paste it as a website source in a new notebook
Summary
Prajwal Tomar, founder of IgnytLabs (an AI-first MVP agency), presents a comprehensive workflow for building and designing production-ready applications using Google Stitch 2.0 and Claude Code. The core thesis is that "AI slop" design isn't an AI problem—it's a workflow problem. The author addresses a fundamental pain point in AI-assisted development: consistency degradation. When solo builders or teams use AI to generate features individually, each prompt operates in isolation, leading to drifting colors, inconsistent typography, and disjointed user experiences.
Tomar's solution centers on a single markdown file called "design.md" that acts as a design system specification. Stitch 2.0 automatically generates this file by extracting typography scales, color palettes, component rules, and design tokens from AI-generated designs. When developers feed this design.md into Claude Code at the start of each session, the AI coding agent maintains design consistency across every screen and feature—solving what has been an intractable problem in AI-generated applications. The workflow starts with design (using Stitch's visual tools), documents it systematically (design.md), then implements it with architectural consistency (Claude Code with MCP access).
The post walks through the exact workflow: take screenshots → feed them to Stitch 2.0 → curate variants → export the auto-generated design system → copy design.md into your codebase → connect Claude Code to Stitch via MCP for direct HTML/CSS access. Tomar then demonstrates how to integrate backends using Claude Code: Supabase for authentication (with automatic role-level security and session persistence), Stripe for payments (complete checkout flow integration), and Resend for email functionality. He emphasizes that Claude Code "coaches you through every integration," so developers don't need deep knowledge of webhook systems or auth models.
The author acknowledges limitations: fonts sometimes need manual adjustment, colors don't always carry over perfectly, and the workflow is token-hungry. However, he argues these gaps are closing rapidly and the fundamental shift is dramatic—what previously cost thousands of dollars and weeks of designer time can now be executed by one person in an afternoon. He positions this as democratizing access to professional design practices that were previously available only to funded teams with dedicated designers.
Key Takeaways
The 'AI slop' design problem stems from workflow, not AI capability—each isolated prompt lacks design context, causing colors to drift, fonts to change, and spacing to become inconsistent across screens
design.md is the critical linchpin: Stitch 2.0 auto-generates this markdown file containing typography scales, color palettes, component rules, and design tokens; Claude Code references it on every prompt to lock design consistency
Stitch 2.0's MCP connection gives Claude Code direct access to actual HTML and CSS source code from design frames, not descriptions—Claude rebuilds UI by reading real code and automatically adds details like hover effects and transitions
The complete workflow involves: screenshots → Stitch variant curation → design system export → design.md integration → Claude Code backend (Supabase auth, Stripe payments, Resend email, Vercel deployment) all in one session
Solo builders can now execute design work that previously required hiring a designer ($3,000–$10,000) and waiting weeks for Figma files—this workflow compresses that timeline to under an hour for app redesigns
Claude Code acts as a coach through integrations: developers provide credentials, and the tool handles Stripe webhook systems, Supabase security models, and auth flows automatically without requiring deep technical knowledge
Production-ready integrations are achievable: Supabase ensures session persistence on refresh; Stripe sandbox mode (test card 4242 4242 4242 4242) allows safe testing; Vercel auto-deploys every change to live production
Design decisions like serif headings + clean sans-serif body text are simple but high-impact—typography is identified as the single fastest way to elevate an app's perceived quality
Stitch generates multiple design variants from a single prompt; cherry-picking the best elements from each variant (typography from one, layout from another, color from a third) produces stronger results than accepting first outputs
The author built 16 SaaS products for clients using Cursor previously; his shift to Claude Code + Stitch indicates meaningful competitive advantages in the current AI development landscape
About
Author: Prajwal Tomar
Publication: X (Twitter)
Published: 2026-03-30
Sentiment / Tone
Confident, evidence-driven, and pragmatic with measured optimism. Tomar avoids hype—he explicitly acknowledges limitations (font adjustments, color accuracy issues, token costs) while arguing these gaps are worth accepting given the dramatic productivity gains. The rhetorical style is instructional and action-oriented: "No theory. Just the workflow." He positions himself as an experienced builder sharing battle-tested practices, not as a promoter. The tone is conversational but authoritative, with phrases like "This is where the workflow gets CRACKED" balancing technical precision with enthusiasm. He frames the moment as a democratization opportunity for solo builders and small teams, historically excluded from professional design systems, rather than dismissing designer roles entirely.
Related Links
Stitch MCP Setup Documentation Official documentation for setting up the Stitch MCP integration with Claude Code—directly referenced in Tomar's workflow
Stitch MCP CLI Tool on GitHub Open-source CLI tool for integrating Google Stitch designs with AI coding agents; enables the MCP connection Tomar describes
Claude Code by Anthropic Anthropic's official product page for Claude Code, the terminal-based coding agent central to Tomar's workflow
Prajwal Tomar is a credible source: he's the founder of IgnytLabs, an AI-first MVP agency, and creator of the AI MVP Builders community (1,900+ members), where he teaches design-to-production workflows. His background is software engineering (NIT Kurukshetra graduate, previously SDE at KPMG Lighthouse). He has publicly documented building 16 SaaS products for clients and has shifted workflows from Cursor to Claude Code, suggesting evidence-based tool selection rather than marketing alignment. The post references Google Stitch 2.0, which is real and launched in 2025 at Google I/O, with major updates in December 2025 and March 2026. Stitch 2.0 is documented to use Gemini 3.1 Pro and supports 400 free generations monthly. Claude Code is Anthropic's real terminal-based coding agent (launched February 24, 2025). The MCP (Model Context Protocol) integration between Stitch and Claude Code is documented and available via GitHub (davideast/stitch-mcp). The "design.md" concept is validated in multiple sources as Stitch 2.0's actual approach to design system documentation. Community reactions (Reddit r/ClaudeCode) confirm the workflow is functional but highlight ongoing edge cases. The timing of this post (March 30, 2026) coincides with recent Stitch 2.0 updates, suggesting Tomar is commenting on current capability maturity. No significant contradictions or critiques were found—the limitations he mentions are echoed in community discussions. His claim that the workflow "changes everything" is positioned as workflow transformation, not technological revolution, which is reasonable given the demonstrated evidence.