Skip to content

Starter specs

A blank app is fine when you know what goes in. Often it's quicker to start from something close and delete what you don't need. These specs are small on purpose: one or two modules, a handful of entities, an enum or two, sometimes a role. The options are the ones I'd pick for that kind of app. Change them before you create it, nothing here is fixed.

The same specs ship inside the CLI and in Coworkee Studio (Start from a template on the welcome page), so you don't need to download anything:

coworkee specs list
coworkee new Sales --template-spec crm
coworkee specs show crm > crm.json   # to change it first

Write your own spec

Pick a starter or start blank, give the app a name and see the spec and the command change as you go. It covers only the switches most people touch first. Everything else (entities, users, branding, the remaining options) goes into the JSON afterwards, or into the Studio, which reads the file too.

Infrastructure and modules
Languages

    Save the file next to where the app should go and run the command; the app ends up in a folder named like it. The check above runs against the JSON schema of a spec, the output of coworkee spec schema. coworkee spec validate knows a few more rules, references between entities for example, and coworkee new runs it anyway before it creates anything.