Blog

pnpm new my-crm --demo crm generates a two-entity Mini CRM — pipeline board, revenue stats, follow-up calendar, sample data, and MCP tools — from one declarative spec.

Idea to deployed full-stack MVP in one sitting, driven by any AI coding agent or by hand. One CLI, machine-readable everywhere.

pnpm new my-app --demo tasks generates a project tracker — workflow columns, priorities, a deadline calendar, throughput stats, and a seeded backlog — on Convex or the Supabase SQL variant.

Capability manifests, a single parseable result line, doctor checks that name their fix, and a canonical playbook: what changes when your primary user is an agent loop.

pnpm new my-shop --demo catalog generates an inventory with a gallery showroom, stock and price stats, toned categories, and seed products — and shrinks to a minimal list app with one flag.

The entity-view kit: a single EntityConfig drives table, list, grid, board, gallery, timeline, calendar, stats, and canvas — plus a generated form. Cloning it costs three small edits.

Why the demo apps are declarative specs run through codegen: multi-entity domains, seed rows, role keys that hide views, --fields without a demo, community spec files, and one manifest an AI agent can drive.

Enable the mcp feature and your scaffolded app exposes MCP tools over its tables — with OAuth 2.1 for chat apps, API keys for dev tools, and interactive UI resources.

Six providers, automatic login flows, an idempotent Convex backend, SITE_URL sync, per-host SPA fallbacks, and a remembered choice — pnpm deploy does the whole dance.

Why --db supabase is not a Convex mimic: schema.sql owns the logic, RLS is the API surface, triggers and RPCs and Edge Functions do the work, and there is deliberately no realtime.

The full walkthrough: paste your endpoint as a custom connector, approve the consent screen, watch your app's tools appear in chat — and the API-key path for Claude Code.

100 designs across 15 families, 18 accents, dark and light — all pure CSS variables. Why every shell primitive and entity view themes itself, and how --design works at scaffold time.

Sidebar, header, a Windows-style desktop, and a macOS-style desktop — all consuming the same five LayoutSlots. Why slots beat per-layout page code.

A 14-shape self-test matrix, a leak-guard that deletes broken scaffolds instead of leaving them, and a Playwright smoke that signs up and crawls every page — the gates behind pnpm new.

A worked example of the domain-building recipe: turn the records pattern into a contacts-and-deals CRM by copying a schema block, a backend module, and one CONFIG.

How the ai feature keeps the Anthropic key on the server: a Node action behind an internal boundary, streaming through database patches, and a system prompt you can edit in one place.

The static content pipeline: blog.json and docs.json as arrays of typed blocks, a generator that emits TOC, client-side search, prev/next, and copy buttons — and why git is the better CMS for a developer site.

What an MVP boilerplate should optimize for, what it should deliberately leave out, and how geenius-mvp's conventions map onto the full Geenius boilerplate when your product graduates.