01
Declare the product system
App surfaces, shared capabilities, agent instructions and verification commands live in one inspectable contract.
Build web and mobile products with typed APIs, durable workflows and practical AI tooling. Shared packages, secure environment loading and executable checks give your team and its agents a system to build on.
included
AI tools + evaluations
included
Web + mobile
included
Typed APIs + workflows
included
Vercel + portable APIs
Harness as Code
Start with a schema. Carry it through validation, OpenAPI and a typed client, then add persistence, tests and instrumentation. The harness records the boundaries and checks that keep this workflow repeatable.
export const harness = defineHarness({
surfaces: ["api", "web", "mobile", "extension"],
capabilities: ["api", "ai", "auth", "cms", "database", "email", "storage", "ui"],
boundaries: "workspace",
agentContext: {
policy: "versioned",
files: ["AGENTS.md", "skills/monokit-app-boilerplate/SKILL.md"],
},
});4
surfaces
8
capabilities
12
checks
01
App surfaces, shared capabilities, agent instructions and verification commands live in one inspectable contract.
02
The harness makes boundaries and safe operations legible before an agent changes code.
03
Run the commands declared in the harness, from contract tests to runtime smoke checks.
Production capabilities
Connect your app surfaces to reusable APIs, AI tooling and integrations, with checks that keep changes verifiable.
Zod contracts connect validation, interactive API docs and typed clients. Request IDs, structured errors and health checks are built in.
Explore the docsTransactional state changes, idempotency, audit entries and an outbox. Signed webhooks and leased jobs handle retries and recovery.
Explore the docsExpo Router connects to tRPC or Hono with shared session handling, account-scoped queries and cache rules.
Explore the docsTyped tools, permission checks, structured outputs and versioned prompts, with deterministic test doubles, evaluations and tracing.
Explore the docsSupply your own rate cards and track usage by request and feature. Model contribution margins with explicit handling of unpriced usage.
Explore the docsdotenvx keeps local keys in the OS credential store. Three shared environment keys, output redaction and typed validation cover every app.
Explore the docsBetter Auth serves web and Expo sessions. The Hono API verifies the same identity and enforces ownership on its example resources.
Explore the docsNext.js, Expo and a browser extension starter, with HeroUI, Tailwind and theme-aware components for your product.
Explore the docsSanity content, React Email templates and AWS SES/S3 integrations live in shared packages you can adapt across apps.
Explore the docsCheckout and license validation patterns provide a starting point for paid products, backed by your own Polar account and configuration.
Explore the docsStart on Vercel. The Hono backend also includes Cloudflare Workers and Node/Docker adapters with explicit database migrations.
Explore the docsAn inspectable harness declares real checks for types, lint, tests, builds and smoke tests. Database fixtures cover concurrency and recovery.
Explore the docsLegible by default
Four app starters, focused shared packages and a versioned harness. Explore the toolkit layout to see where contracts, AI costs, environment policy and verification live.
Selected files from the toolkit. Expand a folder to explore its purpose.
Clear before checkout
Start inside the harness
Start with the architecture, integrations, and agent context already working together, then make the product unmistakably yours.