How it works

Every product here starts with a style. Kits, UX Packs and skins build on top of it, so you buy only the layers your product needs.

  1. 1Stylehow your product looks
  2. 2Kitevery page of a whole product
  3. 3UX Packone flow, worked out in depth
  4. 4Skina seasonal campaign on top

Fig. 1 · one product, four layers

Four layers, one system

Each layer answers one question about your product. Pick the layers your project asks for, and leave the rest.

01 · layer

Style

How does my product look?

Colors, type, spacing and the signature motifs that make a product recognizable. Every other layer reads its look from here.

  • DESIGN.md, tokens and the theme
  • Illustrations, and motifs in the signature styles
  • Figma library in the Full Design System

buy it when

Start here. Every other layer sits on a style.

Browse styles

02 · layer

Kit

Which pages does my product need?

Every page and flow of one product type, from the landing page to billing, with each state on desktop and mobile.

  • Pages and flows in every state
  • Page recipes for your AI tool
  • Works with any of the 16 styles

buy it when

You are building a whole product, like an AI SaaS.

See kits

03 · layer

UX Pack

How should this one flow work?

One flow worked out in depth, such as sign-in: every step, every state and the rules behind them.

  • Steps, states and UX rules
  • Blocks and a clickable demo
  • Works with any of the 16 styles

buy it when

One flow decides your sales or sign-ups.

See UX Packs

04 · layer

Skin

What runs this season?

A campaign layer for Halloween, Diwali, Black Friday or Christmas. It sits on top of your style and switches off when the season ends.

  • Sale hero and illustrations
  • Countdown and price components
  • Leaves your own components untouched

buy it when

A season is coming and you want a sale page fast.

See skins

Build your stack

Switch the layers on and off to see what you get. A style is always the first layer, the rest is up to your project.

Stylealways the first layer

Change the style later and the kit, the UX Pack and the skin follow it. Nothing needs to be rebuilt.

your stack

Full Design SystemFigma library, tokens, theme, shadcn registry, page templates and the full skill$129
AI SaaS KitLanding, dashboard, pricing, onboarding, billing and more, in your style$149

your AI tool reads
DESIGN.md and the tokens, the style skill and the page recipes.

Total$278one-time

Three common stacks

Most buyers start from one of these. A dashed layer is optional and comes and goes with the season.

Try an idea

A landing page or a prototype that should not look like every other AI build.

Free style or a Style Pack

free, or from $39

Build a whole product

An AI SaaS with every page, from sign-up to billing, plus an upgrade flow that converts.

Halloween skin
AI SaaS KitPricing & Paywall UX Pack
Full Design System

from $327

Run client work

An agency or freelancer shipping sites for many brands, all year round.

Every skin, today and while All-access is on sale
Every kitEvery UX Pack
Every style as a Full Design System

All-access · $799 · one license for the whole studio

At a glance

compareStyleKitUX PackSkin
AnswersHow your product looksWhich pages it needsHow one flow worksWhat runs this season
Its own lookYes, this is the lookUses your styleUses your styleSeason colors on the campaign layer
Works withKits, UX Packs and skinsAny of the 16 stylesAny of the 16 stylesEvery style you own
Your AI tool readsDESIGN.md, tokens and the skillPage recipes and flow rulesFlow rules and statesCampaign components
In FigmaLibrary in the Full Design SystemEvery page, in your style's Full Design System fileEvery step, in your style's Full Design System fileThe campaign set
Buy itFirstFor a whole productFor the flow that matters mostBefore the season

Questions about the layers

Do I need a style to use a kit or a UX Pack?

Yes. Kits and UX Packs have no look of their own. They read colors, type and shapes from the style you pair them with, and they work with all sixteen.

Can I buy a UX Pack without a kit?

Yes. A UX Pack works on its own with any style. If you add a kit later, the two fit together.

How is a kit different from a UX Pack?

A kit covers every page of one product type at once. A UX Pack takes a single flow, such as sign-in, and works out every step and state in depth.

What happens when the season ends?

You switch the skin off. It only adds a campaign layer, so your pages return to the style with nothing to clean up.

Where should I start?

Pick the style that fits your kind of product, or try the free style first. Add a kit or a UX Pack once you know what you are building.

Delivery and updates

Where your files are after you pay, and how a new version reaches your project.

  1. Your files after payment

    Everything you buy lands in your library on Polar, our merchant of record, right after payment: the zip, your license key and the invoice. Sign in with the email you bought with; Polar sends a one-time code, and its receipt email links to the library as well.

  2. What the license key is for

    It is your proof of purchase. Keep it with the project, quote it when you write to support, and Polar closes it if an order is refunded. Nothing in the files checks it, so your builds never depend on a server of ours.

  3. How an update arrives

    When a product you own gets a new version, the new zip appears in the same library, and the CHANGELOG.md inside says what changed, version by version. Updates are free for the life of the product.

  4. Putting an update into your project

    The guides keep each pack in its own folder, such as vibecoded-arcade/, so an update replaces that folder and nothing else: delete it, unzip the new version in its place, and your AI tool reads the new DESIGN.md, theme and skill on its next prompt. With a Full Design System, run the same npx shadcn@latest add ./vibecoded-arcade/registry/r/vibecoded-arcade.json command again to update the components. Add --overwrite only after a commit: it replaces your copies in components/ui, including any edits you made, so review the diff before you keep it.

Start with a style

Every kit, UX Pack and skin works with every style, so the first choice is simply the look that fits your product.