Design library
A design library for any site.
95 templates across 12 categories. Each one is a complete design system — palette, type, radius and component rules — with starter code. Pick a look, describe your tweaks in chat, and ship it live.
// real code · every colour editable · database, auth, email & payments included
Start here
What a template means on this platform
Not a file you download and maintain. A starting point for a working, hosted application — design and machinery together.
A template here is a complete design system plus starter code. It fixes the decisions that are slow and easy to get wrong — the colour palette, the heading and body typefaces, the corner radius, the spacing rhythm and the component rules — and it comes with the page structure that suits its job: a product grid for a storefront, a schedule for a conference, a listing and detail pair for a marketplace, a table and side navigation for a dashboard.
When you pick one, it becomes the starting point of a real project rather than a folder on your desktop. The app is generated and built in an isolated sandbox so you get a working preview in seconds, and the backend it needs is written in with it — a Postgres schema and data layer, sign-in, email and payments, taken from a catalogue of vetted bricks rather than typed out afresh for your project. Nothing in the preview is a picture of an app. It is the app.
That is the difference from a static theme. A theme hands you markup and stops at the surface; keeping it running, wiring a database to it and deploying it are your problem. Here the design arrives attached to the machinery, you change it by describing what you want, and Go Live puts it on a real URL. If you would rather see the whole pipeline first, the platform overview walks through it end to end, and the docs cover both the prompt-to-app and the connect-a-repo path.
A downloaded theme
A zip of markup and styles. You install it, fight the parts that do not fit, and own every upgrade after that. It has no database, no accounts, no payments and no hosting — those are separate products you assemble yourself. Changing the design means editing files by hand.
A template here
- Real code you can run, deploy and keep
- Database, auth, email and payment code already written in
- Edited by chat, by clicking an element, or from a screenshot
- Published to a live URL, then monitored
Choosing
How to choose a template
Four questions that get you from a wall of options to one starting point — and none of them are about the placeholder text.
Start from the shape, not the subject
Pick the template whose page structure is closest to what you need — a listing grid, a booking flow, a long-form article, a data table. Subject matter is the easiest thing to change by chat; structure saves you the most work.
Judge the look, ignore the words
The names, prices and photos in every preview are placeholder content. What you are choosing is the design system underneath: type, spacing, colour and component style.
Open it and read the tokens
Each template page shows the full front page at desktop size plus its palette, heading and body fonts, corner radius and the design rules the agent keeps to. That is the fastest way to tell two similar-looking templates apart.
When in doubt, just describe it
A template is a head start, not a requirement. If nothing in the library matches, describe the look you want and the agent builds the design system with the app.
The library
Browse 95 templates across 12 categories
Hardcoded design rules and code you can apply to any website — not static downloads. Build on one, swap what you want, and ship.
Animated
10 templates
Motion-led product pages — scroll-driven sequences, video-backed heroes and animated SVG. They suit a single flagship launch: hardware, a camera, a fragrance, a wearable, a vehicle. If your story is best told by scrolling through it, start here.
Experimental
7 templates
Design-forward layouts for galleries, lookbooks, zines, poster typography and immersive, award-site-style pages. These break the standard marketing grid on purpose — pick one when the design is the argument.
Portfolio
7 templates
Work-first layouts for photographers, illustrators, architects, 3D and motion artists, product designers and writers. Big imagery or long-form case studies, with the navigation kept quiet so the work carries the page.
Music
7 templates
Artists, bands, DJs, record labels, podcasts, album launches and music schools — designs built around cover art, release dates, tour and episode lists rather than feature grids.
Marketplace
7 templates
Two-sided layouts with listings at the centre: property, vehicles, jobs, freelance services, event tickets and vacation rentals. Search, filters, listing cards and detail pages are part of the shape.
Content
7 templates
Reading-first designs for magazines, personal blogs, newsletters, course platforms, video channels and editorial nonprofits — typography, article rhythm and archive structure over decoration.
Commerce
11 templates
Storefronts across fashion, beauty, jewellery, coffee, sneakers, furniture, electronics and single-product hardware brands. Product grids, detail pages and a checkout path, in looks that range from minimal to luxury.
Events
7 templates
Conferences, meetups, webinars, festivals, galas, weddings and community listings — schedules, speakers, sessions, tickets and RSVP flows.
Booking
7 templates
Appointment-led businesses: clinics, salons, barbers, spas, hotels, coworking spaces and cabin retreats. Services, availability and a booking call to action are the backbone of the layout.
Marketing
10 templates
Conversion-focused sites for SaaS products, agencies, consultancies, studios, restaurants, wellness brands and waitlists — hero, proof, features, pricing and a clear next step.
Dashboard
8 templates
Data-dense internal surfaces: analytics, CRM pipelines, finance, logistics, project boards, org charts and request routing. Tables, charts, filters and side navigation done in a way that stays readable.
Developer
7 templates
Technical audiences — API products, CLI tools, open-source libraries, documentation, changelogs and status pages. Code samples, reference navigation and dark-friendly surfaces.
Customisation
How customising a template actually works
Four ways to move a template towards what you had in mind — all of them editing real files, none of them requiring you to open one.
Describe the change in chat
The main way. "Make the hero bigger", "drop the pricing section", "this is a bakery, not a SaaS" — the agent edits the real files and the preview updates. Structure, copy, sections and behaviour are all fair game, not just colours.
Click an element to target it
When it is easier to point than to explain, click the element in the live preview and edit it directly. The change lands on that exact piece of the template instead of somewhere approximate.
Show it a screenshot
Upload a screenshot or a reference image of the design you are chasing and the agent matches it — useful when you like a template’s structure but have a specific look in mind.
Swap the whole palette
Every template carries its own colour tokens. Apply a different palette from the palettes library and the design recolours around it — surfaces, accents, text and borders together, not one hard-coded hex at a time.
The four work together rather than in sequence. A normal session looks like: pick the template whose structure fits, swap in a palette you like, describe the sections you actually need, click the two or three things that are still not right, and paste a screenshot when a detail is easier to show than to say. Ready-made elements — buttons, cards, inputs, toggles and loaders — can be dropped in the same way, recoloured to whatever palette the template is running.
Because the design rules travel with the template, edits stay coherent. Asking for a new section does not produce something in a different typeface with different corners: the agent keeps to the system the template defines. That is why the design rules are printed on every template page — they are the contract, not decoration.
Included
What every template includes, whatever the look
The design is the part that differs. Underneath, every template starts from the same pre-wired foundation.
A real data layer
Postgres schema, migrations and a vetted data-access brick are written into the project, so a template with listings, bookings or products has somewhere real to keep them — and real code reading and writing them.
Authentication
The auth brick goes in whole — session provider, sign-in and sign-up form, route guard, profile migration — rather than being written out again. A dashboard or marketplace template does not start with an empty login page.
Transactional email
Confirmations, notifications and receipts are generated as server-side sending code against Resend — the piece booking and event templates always need. You bring the Resend key and verify the domain it sends from.
Payments
The Stripe brick — Checkout Session endpoint, client redirect, signature-verified webhook — is available to every template, so a commerce or ticketing design can actually take money instead of faking a checkout. It runs on your own Stripe account, so the money is yours.
Hosting and a real URL
Builds and deploys run on Cloudflare. Go Live publishes the template to a real, hosted URL with SSL — and custom domains when you want one.
Continuous monitoring
Once it is live, health checks watch the build, the deploy and the running app, with alerts on failure, and a one-click restore to any earlier version.
More detail on each piece lives in capabilities, and pricing covers what is included at each plan.
Ownership
What stays yours after you pick one
A starting point should not become a dependency. Here is what you keep.
The code and the content
Under the terms of service you own the code and content you create with the service, and no ownership is claimed over your projects. A template gives you a head start; what it becomes is yours. The specifics are in the terms.
The repository and the review
Connect a GitHub repository and every agent change arrives as a pull request with its checks already run. Nothing merges without your review, and your repository never changes behind your back. The docs walk through that workflow.
FAQ
Questions about templates
Don't see your style? Just describe it.
Templates are a head start, not a limit. Tell code-anything the look you want and it builds the design system and the app, then deploys it live.