Use cases
Start from the problem. Each one states what goes wrong, then walks through solving it with the packages and components in the kit — in the order you would actually do it.
Build this app
6
A subscription SaaS app
Plans, checkout, per-plan feature gating and metered usage — with the catalog in your database rather than the payment processor.
An e-commerce storefront
Catalog, cart and Stripe checkout, with the product data owned by your app instead of the payment processor.
A referral or network-marketing platform
Downline trees, commission runs and rank qualification — the parts that are hard to get right and expensive to get wrong.
An analytics dashboard or admin console
Charts, stat bands and tables over live data — the internal surface every product grows whether it was planned or not.
An online course and coaching platform
Curriculum, lessons, graded tests and certificates — with the selling side already attached.
A real estate listing portal
Search, map, listing detail and enquiry capture — with the agent-facing side built in.
Agents in your app
4
Let an agent operate your app alongside the user
Give an AI assistant real control of your interface — without screen scraping.
Have an agent build a spreadsheet the user can check
Model-generated workbooks, reviewed in the browser, exported as real xlsx.
Build a terminal app an agent can use too
Ink components for CLIs, plus a bridge so an agent drives the same TUI.
Let people accept or reject an agent's edits
Per-change review for anything a model rewrites.
Automation
2
Commerce
3
Sell plans and subscriptions with Stripe
Products, prices and checkout, managed in your app instead of the Stripe dashboard.
Gate features by plan and meter usage
One check for "can they do this?", whether it is a flag or a quota.
Run a referral or affiliate program
Referral trees, commissions and rank progress, with the UI to show them.
Surfaces
5
Build a dashboard that stays current
Charts that update when the server changes, without a refresh button.
Put a map with live tracking in your app
One map component, either engine, with tracking built in.
Give people a canvas to work on together
Whiteboard and design-canvas surfaces, with agents as participants.
Add a code editor and a file browser
Editing, browsing and previewing files inside your product.
Show repositories, history and pull requests in your product
Provider-neutral Git surfaces — GitHub, GitLab or Bitbucket.
Platform
5
Add passkey sign-in
WebAuthn login and passkey management, on top of Fortify.
Let non-developers edit pages
A CMS whose output is your components, not arbitrary HTML.
Be legible to search engines and to AI agents
Server-rendered SEO plus the well-known files agents look for.
Ship a PWA that notices when it is out of date
Installable, offline-capable, and honest about stale builds.
Find out where your interface actually fails people
Interaction analytics you host, plus an embeddable verification badge.