fakenerd.ai

daily nerdingDesign like Ras Mic

Design like Ras Mic

Ras Mic says he's not a designer and didn't write a line of code, yet his apps look designed. His method: copy the design system of a site you love, try it on a real page, fix the page, then write the fixes back into the system. Repeat until it's yours.

Jump to the six steps, his tools, or set it up yourself.

The video

17 minutes, posted Sept 28, 2026. Every timestamp on this page opens the video at that moment. 4:52 to 7:08 is a sponsor read.

  1. 0:00 Software gets judged by its cover
  2. 0:40 What he designed: portfolio, Pluto, Goshen Labs
  3. 2:15 You need two things: Paper and a screenshot tool
  4. 2:35 Step 1 · Find inspiration
  5. 3:22 Step 2 · Build the design system
  6. 4:52 Sponsor (Firecrawl), skip to 7:08
  7. 7:08 Step 3 · A landing page from the system
  8. 7:28 Step 4 · Iterate: Pluto goes from gray to color
  9. 8:19 Paper comments: “address all the comments I left”
  10. 9:26 Mixing two design systems
  11. 10:07 Why the page comes before the system
  12. 10:48 Step 5 · Exploration: the banking page
  13. 11:47 One prompt, whole dashboard
  14. 12:36 Recoloring GitBook's design system
  15. 14:48 The loop, said once more
  16. 15:17 Which model: Opus 5.5
  17. 16:53 The loop, final recap

Eight signals

The whole video in eight boxes. Each links to the part of this page that explains it.

  1. 012:35

    Start from a site you love

    You don't need design skills to begin. Find an app or site that looks right to you on Mobbin or X, even outside your niche, and screenshot it.

    How
  2. 023:22

    Turn it into a design system

    Give the agent the screenshot and the link. It writes down the colors, fonts, spacing, corners and components in Paper. He calls this “the most important part.”

    How
  3. 0310:07

    Fix the page, then the system

    A sheet of swatches tells you little. Build a real page, fix it until you like it, then have the agent write the changes back into the design system.

    How
  4. 048:19

    Rough comments are enough

    He pins notes like “not a fan” right on the design, then asks the agent to address all the comments. You don't have to know why something is wrong.

    How
  5. 0510:40

    It takes days, not one prompt

    Page, comments, update the system, and again. In his words: “Go multiple rounds, multiple days.”

    How
  6. 0615:10

    Ask for many versions

    “I would never build one version.” One exploration prompt gets several layouts of a page, all on the same design system.

    How
  7. 0712:04

    Short prompts work once the system exists

    He calls his dashboard prompt terrible, and it still came back looking right. The design system does the heavy lifting.

    How
  8. 0815:17

    The system matters more than the model

    He uses Claude Opus 5.5 and finds Claude models best at design. But with no design system to follow, any model's work looks “AI smelly.”

    How

Words on this page

Twelve terms, in plain words. Skip this if you already design with coding agents.

Agent
The AI that does the work: Claude Code, Codex or Cursor, running a model. Here it's Claude Opus 5.5, which Ras Mic thinks is best at design.
Harness
The app you run the agent in. His is T3 Code, a free desktop app over Claude Code and Codex. Plain Claude Code works too.
Thread
One running conversation with the agent. He gives each design job its own thread and runs several side by side.
Paper
A Figma-style design app where every frame is real HTML and CSS. The design system, the pages and his comments all live there.
MCP
Short for Model Context Protocol. It's the plug that lets the agent read and draw on Paper. It only works while Paper Desktop is open, and the free plan allows 100 MCP calls a week.
Canvas and frame
The canvas is Paper's open workspace. A frame is one board on it, like a page. He copied a whole design system frame from one project into another.
Mobbin
A library of screens from real, well-designed apps and websites. He browses it by niche to find a site to borrow from.
Design tokens
The named values in a design system: each color, size and spacing step. His devin.ai build had 105. Telling the agent to use the tokens stops it inventing new values.
Radii and surfaces
Radii are how rounded the corners are. Surfaces are how a card sits on the page; his file had four: hairline, raised, frosted and floating.
AI smell
Ras Mic's name for the generic look you get when a model designs on its own, with no design system to follow.
Vibe-coded
Built by telling an AI what you want instead of writing the code. He vibe-coded his own screenshot tool.
DESIGN.md
A plain text file in your project that writes down the design system. FakeNerd's take: the loop works with one of these and screenshots, without Paper.

Borrow taste, then make it yours

“Design is less about math, more about feeling.” AI can't supply the feeling. A design system can carry someone else's until you have your own.

A design system is

The rules behind a look, written down: colors, fonts, spacing, corner rounding, shadows, and the buttons and cards built from them. “That is what a design system is.”

The twist

Don't edit the system directly. Build a page, fix the page, then have the agent update the system. “You and I do not have the eyes to see what a design system looks like on an actual page.”

Without one

“When you give them no design system and they design on their own, then it's very AI smelly.”

What he's made this way: a portfolio redesign, the Pluto app (dark and light mode, animations, a little character), his Goshen Labs site, and a dashboard for Bezalel. He sees his own style starting to form across them. 0:40

His kit

Five things. Only Paper and a screenshot are required; the rest are his picks.

  • Canvas

    2:15
    Paper

    A Figma-style design app where every frame is real HTML and CSS. Its MCP lets the agent read and draw on the canvas. Also where he leaves comments and generates images.

    Free: 100 MCP calls a week. Pro: $20 a month per editor.

  • Harness

    3:36
    T3 Code (nightly)

    Theo's open-source desktop app for running coding agents in threads. He runs one thread per design job, several at once.

    Free, MIT. Nightly builds on GitHub.

  • Model

    15:17
    Claude Opus 5.5

    On screen: Opus 5.5, Extra High effort, 1M context, full access. “Generally, the Claude models are the best at design.”

    Your Claude plan or API.

  • Inspiration

    2:35
    Mobbin

    A library of screens from real, well-designed apps and websites. Browse by niche, find a site you like. He also follows designers on X.

    Free to browse. MCP needs a paid plan.

  • Capture

    2:24
    A screenshot tool

    He vibe-coded his own. Any works: the screenshot of a site you like is the input to step 2. On a Mac, ⌘⇧4.

    Free.

On the model: “Honestly, generally, the Claude models are the best at design.” He has also used Astra. Any model does fine “as long as you have a design system and you're telling it to follow the design system.” 15:17

The six steps

Click a step. Step 4 is a loop: fix the page, update the system, fix the page again. “Go multiple rounds, multiple days.”

  1. then back into step 02

Step 1 of 6

Watch at 2:35

Find a site you wish was yours

Browse Mobbin or X for apps in your niche, or outside it. Pick one or two that look right to you. He picked devin.ai. Screenshot it.

Why: You're not a designer, so don't start from a blank page. Start from someone else's taste and bend it into yours.

Say something like

(No prompt yet. Just the screenshot and the URL.)

Watch out: Picking by niche only. Good ideas come from other niches too.

His prompts

Typed ones are copied off the screen. Said ones are how he read them out. They're short. The design system does the heavy lifting.

  • Make the design system

    Typed3:36

    Create a project on paper using the MCP, create this website and it's design system

    Attached: a screenshot of devin.ai and the link. Opus 5.5 worked 28m 15s and came back with a Paper file: the rebuilt homepage (1440 × 7214), a Foundations page (color system, type specimen, spacing scale with grid rules measured from the site, corner radii, four surface styles) and a Components page. 105 design tokens in all.

  • Add color

    Said7:55

    I want us to explore adding color.

    The first Pluto was pure black and white. This got a few versions back; he kept blue accents and colored buttons, in dark and light mode.

  • Act on the comments

    Said8:27

    Address all the comments I left.

    His comment on one card: more space around the picture, and rounder. The agent came back with a new version of the card.

  • Mix two systems

    Said9:53

    Combine these two design systems and build me a new page.

    He copied his portfolio's design system frame in Paper, pasted it into another project next to the new one, and asked for this.

  • Explore one page

    Said11:01

    Can we do an exploration of the banking page?

    Pluto's connect-your-bank page was “pretty ugly.” One prompt, several full layouts back.

  • Design the product

    Typed11:47

    Build out the product dashboard using the Paper MCP on the Paper project. You already have access to the code so you know what the app can do. Using the design system and the landing page that was created, design for me the product, which is the dashboard

    For Bezalel, his agent project. The thread already knows the codebase, so the agent knows what the dashboard has to show. A few minutes later: a dashboard he calls beautiful.

  • Recolor a system

    Said12:48

    Please go on the GitBook project on Paper using the MCP. I want you to change the design system. I actually want different versions because the base color is orange. I like everything else, I'm just not a fan of orange. Create for me different versions with different colors.

    Started in a separate thread while the dashboard was cooking. Back came blue, teal and purple versions. He deleted orange and purple.

He runs these in separate T3 Code threads at the same time: one recolors a design system while another designs a dashboard. His thread names on screen read like a to-do list: Explore Banking Page, Review and Rebuild Icon System, Redesign Site in Pluto Style.

What lands in Paper

Three things worth copying, read off his screen.

1 · The design system file

From one screenshot of devin.ai, after 28 minutes:

  • Landing page. The whole homepage rebuilt, 1440 px wide, checked against the live site.
  • Foundations. Color system, type specimen, spacing scale, corner radii, four surface styles (hairline, raised, frosted, floating).
  • Components. Buttons, nav, headings, content blocks, product UI pieces at true size.
  • 105 tokens for colors, fonts, sizes, spacing, radii, opacity and breakpoints.

It also listed what it couldn't match. Devin's font isn't in Paper, so it picked Geist.

2 · His comments

Pinned right on the design with Paper's comment tool, then one prompt: “address all the comments I left.” Note how rough they are. 8:19

  • not a fan

  • im not a fan of these colors and balls, idk what would be better but not a fan

  • borders too strong

  • borders are too dark, not following the design system

  • badge should be bouncy and user should be able to drag it and move it around and the physics should feel […]

Knowing why you don't like something is optional. “Not a fan” is feedback.

3 · The agent's report

After building his Bezalel landing page, Opus 5.5 ended with these headings. Worth asking for by name. 11:47

  • Design system use

    Every color, size and spacing value comes from the file's tokens.

  • Imagery

    Which images are new, and how they were made.

  • Where I departed from the design system

    Each exception, and why (for example, text left darker so it stays readable).

  • Not done yet

    No code changed, placeholder links, no mobile layout.

Set it up

About 15 minutes. You need Claude Code (or Codex, or Cursor) already working. Paper's free plan is fine to try it; see pricing.

  1. 01

    Install Paper Desktop

    The MCP only works while the desktop app is open. The web app alone won't do.

    paper.design
  2. 02

    Connect Paper to your agent

    In Paper Desktop, open the MCP panel and click Add to Claude Code (or Codex, or Cursor). Restart the agent. Or from a terminal:

    claude plugin marketplace add paper-design/agent-plugins && claude plugin install paper-desktop@paper
    Paper MCP docs
  3. 03

    Optional: a harness like his

    T3 Code is a desktop app over Claude Code and Codex, with threads you can run side by side. Plain Claude Code works too.

    brew install --cask t3-code
    T3 Code releases
  4. 04

    Optional: Mobbin in your agent

    So the agent can search real app screens itself. Needs a paid Mobbin plan. You'll sign in once in the browser.

    claude mcp add mobbin --scope user --transport http https://api.mobbin.com/mcp
    Mobbin MCP

FakeNerd starter · one prompt per step

# 1 · Design system (attach a screenshot of the site you like)
Create a project on Paper using the MCP. Recreate this website [URL] and
extract its design system: colors, type, spacing, radii, surfaces and
components, each on its own page. Then build a landing page for [my app]
that uses only that design system.

# 2 · Iterate (after leaving comments on the canvas)
Address all the comments I left on the Paper project.

# 3 · Write it back (once the page looks right)
Update the design system so it matches the landing page as it is now.
List every change you made to the system.

# 4 · Explore
Do an exploration of the [page name] page: 3 different layouts, all on
the design system. Put them side by side in Paper.

# 5 · New pages
Using the design system and the landing page, design the [dashboard].
You have the code, so you know what the app can do.

# 6 · Ship
Build the [dashboard] design from Paper into the app. Use the design
system's tokens, not new values.

Swap the brackets for your own site and app. Run step 1 once, steps 2 and 3 as many times as it takes, then 4 to 6 for each new page.

FakeNerd's take

The order is the insight

Most people tweak the tokens and hope. He tweaks a real page and makes the agent update the tokens after. That's how a non-designer gets taste into a system.

The free tier won't last a day

Paper's free plan is 100 MCP calls a week. One 28-minute design system build can use most of that. Budget for Pro ($20/month) if you try this for real.

Don't ship the copy

Step 2 clones someone's look on purpose. That's fine for learning. Steps 4–5 are what make it yours: new color, mixed systems, your own comments. Ship after those.

The model matters less than the system

He likes Opus 5.5 best for design, but says other models do fine when told to follow a design system. Without one, every model looks “AI smelly.”

It works without Paper

The loop is the point. You can run it with a DESIGN.md file and screenshots of your own app. Paper just makes the system and comments visible.

More from Ras Mic on this site: his software factory, for how he ships what he designs, and his stack, for everything he builds with.

Attribution

↑↓ move enter openBrowse every card