Use cases
Use cases
Four ways to use the foundation. The names and items are made-up examples.
A new product on the scaffold
Keep the platform, remove the CRM example, and build your own domain in its place.
Sample items
- Keep apps/api auth, roles and rate limiting as they are
- Replace /api/clientos routes with /api/orders (sample)
- Ship the web app to Vercel and the API to Render
A new resource next to clientos
Follow the clientos pattern to add one resource end to end.
Sample items
- A Drizzle table and migration in packages/db
- An OpenAPI route in apps/api, then `pnpm openapi:dump`
- A dashboard page using the generated hooks
An operator CLI
Give operators a command-line tool that shares types with the API.
Sample items
- client health --api-url https://api.example.com
- A new `client` subcommand in apps/cli (sample)
- A single-file binary from `build:sea`
LLM context for client work
Keep each Client’s LLM context current and hand it to an assistant.
Sample items
- client clientos init acme-corp
- client clientos bind acme-corp --project website
- client clientos context acme-corp | pbcopy
Skip the setup week
Clone it, run five commands, and start on the part that is actually your product.