v2.1.0 — a design of its own, and skills that start and restyle your product

v2.1.0 is about the first hour with the kit: how it looks when you open it, and how quickly it becomes your product. Nothing you built has to change.

A design of its own

The kit no longer looks like every other starter.

• One palette everywhere: warm paper and ink, with one accent color, marigold. The same colors are in the web app, the mobile app, the marketing site and the emails, light and dark.
• Type: Instrument Sans for text and headings, and JetBrains Mono for labels and code.
• Yours to change: see Restyle it in one prompt below.

Screens laid out for real use

• Settings: every settings page uses one layout, with what each section is for on the left and its controls on the right. Forms with one field fit on one line.
• Profile: you first, then your details, your devices with the current one at the top, and deleting the account last.
• Audit log: grouped by day, with who did it, what changed and how long ago.
• First screen: a checklist of first steps that ticks itself off. Replace the steps with your product’s own.
• Empty states that say what goes there and how to add the first one.

Signing up converts better

• Sign-in and sign-up show your product’s one-line promise beside the form.
• The plans mark the one most people should pick.
• A locked feature shows the price and what the plan adds, not just “Upgrade”.

The assistant

• Answers are drawn: lists, code, tables and bold come out as Markdown, as the answer arrives.
• Waiting is clear: a typing indicator until the first words, and the page follows the answer unless you scroll up to read.
• Starter questions on an empty chat, so nobody faces a blank box.
• History: your past conversations, grouped by day. Open one to carry on, or delete it.
• On the phone too: the mobile app has the same answers, history and starter questions, and its audit log is grouped by day.

The marketing site

• Laid out to convert: a hero with a screenshot, short promises, a showcase of the product, pricing with the recommended plan marked, questions and a last call to action.
• Light, dark or system, with a switch in the header, and screenshots that follow it.
• A place for proof that stays hidden until you have real customers to put in it.

See Marketing site.

Start your product

A new skill, start-product, for the day you clone the kit. Describe what you are building, in a sentence or a whole spec, and your coding agent:

1. Asks only what changes the build: who signs up, and what you charge for.
2. Writes PRODUCT.md: each part of your idea and the piece of the kit that builds it, and a list of what the kit has no pattern for, with options.
3. Waits for you to approve the plan before writing any code.
4. Builds it in small slices with the other skills, and runs the tests for each one.

Start your product walks through it with an uptime monitor.

Restyle it in one prompt

A second new skill, redesign. Tell your agent the look you want, in a few words, with a screenshot of a site you like, or with your logo. It changes the colors, fonts, corners, logo and app icon in the web app, the mobile app, the marketing site and the emails, light and dark, then looks at every main screen.

• Every place the look lives is listed in one page: Change the design.
• Readable by test: bun run check now checks every pair of colors that puts words on a background, in both modes. A palette that fails names the pair.

A demo with everything open

For your own product’s public demo: DEMO_ALL_FEATURES=true, beside DEMO_MODE, gives every visitor every feature and the top plan’s allowances without paying. The billing page still shows their real plan, and checkout still works in test mode. Our own demo now runs that way.

Upgrading

1. Run bun install: fonts and the Markdown renderer are new.
2. If you changed appConfig in packages/contracts/src/app.ts, add a tagline.
3. Where your colors, fonts or marketing words conflict with the kit’s, keep yours.

UPGRADING.md has the full list, and the upgrade-kit skill applies it on a branch.

Next

Notifications for one person, from any module with one call: a bell and an unread count, sent to their phone or by email as they choose, and system events to their open apps. The roadmap has the details.