How to build your MVP’s UI in a week: a Figma kit, React code and an AI agent

To build an MVP’s UI in a week, start from a UI kit with Figma screens and matching React code. On mebius.design, 19 kits ship both: design your flows in Figma, install the code with the shadcn CLI or an AI agent, then wire your backend, auth and payments.

7 min read · Updated Nov 19, 2026 · React + Tailwind

What does mebius.design cover when you build an MVP?

The UI only: the Figma file and the React front end.

mebius.design covers an MVP’s UI and nothing behind it. Each mebius.design code kit gives you a Figma file and a React front end in the same style. The backend, database, auth, payments and hosting stay yours to build or buy.

Every mebius.design code kit includes sign-in, onboarding, settings and billing blocks. They are screens, not services: the sign-in form creates no accounts until you connect an auth provider.

Code UI kits on mebius.design at a glance
Kits with code19 of 35 kits, for dashboards, mobile apps and websites
ScreensA Figma file per kit, e.g. 161 screens in Arcline
Components2,046 React components across the code kits
Blocks1,061 React blocks, with sign-in, onboarding, settings and billing in every kit
Code stackReact 19, TypeScript and Tailwind CSS v4, in shadcn registry format
Installshadcn CLI, or the mebius MCP in Claude Code, Cursor and VS Code
ScopeThe UI only. The backend, database, auth and payments are yours.
LicenseSingle license, client work included. The Agency license adds handing the files to clients, white-label and resale.
Price$19 once per kit, or $259 for all items. No subscription.
Counts as of19 Nov 2026, live from the catalog

What does a one-week plan for an MVP’s UI look like?

Seven days, one kit, one AI agent.

This plan for a mebius.design code kit assumes a small team and Claude Code or Cursor. Days 5 and 6 bring in your own backend.

  1. Day 1: pick the kit and list the screens

    Write down the MVP’s three to five core flows, such as sign-up and the main dashboard, and match each to the kit’s screens. Cut the rest.

  2. Day 2: make the Figma file yours

    Copy the screens you need to a new page and change the logo, colors and copy. Build any missing screen from the kit’s own components, since the code matches them. Or skip Figma and go straight to code.

  3. Day 3: set up the project and the theme

    Create a React 19 + Tailwind v4 app with Next.js or Vite, run shadcn init, add the @mebius registry and install the kit’s theme on its own.

  4. Day 4: install the blocks

    Add the blocks for your flows with the shadcn CLI, or ask your AI agent to add them over the mebius MCP, then lay them out as pages.

  5. Day 5: connect auth and data

    Wire the sign-in block to your auth provider and replace the blocks’ sample data with calls to your API.

  6. Day 6: connect payments and email

    Point the billing block at your payment provider’s checkout and send receipts from your email service.

  7. Day 7: test and ship

    Sign up as a new user, check every empty state, deploy, and show the MVP to its first users.

How do you choose a UI kit for an MVP?

By the core screen, not by the screen count.

Choose the mebius.design kit whose screens are closest to your product’s main flow. A kit that already has your core screen saves the most days.

How do you install a mebius.design kit with the shadcn CLI?

Theme first, then items, from the @mebius registry.

mebius.design code installs with the shadcn CLI 4.x into a React 19 + Tailwind v4 project that uses shadcn’s @/ aliases, with Next.js or Vite. Run init once if the project has no components.json:

Terminal
npx shadcn@latest init

Create a token in Settings › Tokens and add the @mebius registry to components.json:

components.json
{
  "registries": {
    "@mebius": {
      "url": "https://www.mebius.design/r/{name}.json",
      "headers": {
        "Authorization": "Bearer ${MEBIUS_TOKEN}"
      }
    }
  }
}
.env.local
MEBIUS_TOKEN=mbs_your_token

Install the kit’s theme on its own first, then items with --overwrite so shared parts take the kit’s version. For a SaaS MVP on Arcline, the sign-in, settings and billing blocks are:

Terminal
npx shadcn@latest add @mebius/arcline-theme
npx shadcn@latest add @mebius/arcline-login-and-sign-up @mebius/arcline-settings-page @mebius/arcline-billing-overview --overwrite

Every CLI command and error message for the @mebius registry is in the shadcn MCP and CLI guide.

How do Claude Code and Cursor add mebius.design items over MCP?

A hosted server with browser sign-in.

The mebius.design MCP server lets an AI agent list a kit’s items, read their source and usage docs, and get the exact install commands. It runs at https://www.mebius.design/api/mcp and signs in through the browser, so there is no token to copy. In Claude Code:

Terminal
claude mcp add --transport http mebius https://www.mebius.design/api/mcp

Run /mcp, choose Authenticate and approve in the browser. Cursor takes the same URL in .cursor/mcp.json. Then ask for a flow, for example “Add the Arcline login and sign-up block to this app.” The agent runs the shadcn CLI commands the server returns, theme first.

A free mebius.design account covers the free charts and forms, so you can sign up and test the whole setup before you buy a kit.

How do you wire the backend, auth and payments to a mebius.design kit?

Your stack, the kit’s screens.

mebius.design kits include no backend, so this part of the MVP depends on the stack you pick. The blocks are React components with sample data, easy to connect to any provider.

Ask your AI agent to do this wiring one block at a time, and keep your data logic in your own files.

What are the other ways to build an MVP’s UI?

Checked on each product’s own site on 19 Nov 2026.

AI app builders and shadcn block libraries solve the same problem from other sides. Each fact links to its source.

An AI builder is quickest when the look can wait. A block library suits teams that design in code. A mebius.design kit suits founders who want a designed product in Figma and React from day one.

FAQ

Answers to what people ask most.

Can you build an MVP’s UI in a week?

Yes, if the MVP has a few core flows and you start from a UI kit with code. Design and install take four days; the backend, auth and payments take the rest, or longer. mebius.design covers the UI only.

Does mebius.design include a backend, auth or payments?

No. mebius.design covers the UI: the Figma file and the React front end. Every code kit has sign-in, onboarding, settings and billing screens, but connecting them to an auth provider, a database and a payment provider is your work.

Which AI coding tools work with the mebius.design MCP?

Claude Code, Cursor and VS Code sign in through the browser. Tools that can’t open a browser send a token from Settings › Tokens. The shadcn CLI installs the same items without any AI tool.

How much does a mebius.design kit cost for an MVP?

$19 per kit, paid once, or $259 for all items. Every purchase covers client work; the Agency license adds handing the files to clients, white-label and resale. The free charts and forms need only a free account.

Is v0 or a UI kit better for an MVP?

It depends on what the MVP needs first. v0 and Lovable generate working apps from prompts, which suits testing an idea fast. A UI kit gives you designed screens and code in one style. v0 can start from a Figma file, so the two can work together.

Item pages, kits and guides this guide uses.