The setup prompt

Copy the line below into an AI assistant that can run commands on your computer — Claude Code, Codex, Cursor. Answer the questions it asks, then open the link it gives you.

Set me up on Lotics: fetch https://lotics.ai/docs/prompt.md and follow it.

For the assistant

You are setting up a Lotics workspace for the person you are talking to. They never see
commands, file contents, ids, findings or error text — you handle all of that. They answer
one message of questions, at most one short follow-up, and receive a link.

1. Install the command line, even if it is already there — the same command upgrades in
   place and does nothing when it is current. On macOS, Linux or WSL:
     curl -fsSL https://lotics.ai/install.sh | bash
   In Windows PowerShell:  irm https://lotics.ai/install.ps1 | iex
   This needs nothing already on the machine — no Node, no npm.
   If you also have Lotics tools or a Lotics connector, do not use them here: they can point
   at a different workspace than the command line does.
2. Ask them, in ONE message: what do they manage, what do they track about it today — the
   columns in their spreadsheet, the things that have names — and which email address the
   account should be under. Plain words, no list of categories: what they call their work is
   what their tables will be called. If they mention a spreadsheet, ask them for the file
   and read its first row: those columns are the fields, in their words. If the answer
   leaves you unsure what the main things are, ask one follow-up. Then stop asking.
3. Fetch  https://lotics.ai/presets/index.json  — complete example models, one per trade,
   each listed by slug, label and description and served at
   https://lotics.ai/presets/<slug>.json. If one is close to their trade, read that file: it
   is a worked example of a whole model, not a file to copy.
4. Run  lotics docs model  and write `model.json` from their answers alone: their words as
   table and field names, links between the things that refer to each other, and the real
   examples they gave as first rows, never invented ones. From an example, keep only the
   tables and fields their business has, in their words.
5. Then the apps. For each job they described — the work one person does on these tables,
   like taking orders or collecting payments — add one app under `apps`: one register over
   the table that job works. Which treatment each list takes — the next step refuses an app
   that leaves one out — and how to write one:
     lotics docs design
     lotics docs model/apps
   All of this is silent: do not show them the file, the findings or the commands.
6. Create everything in one command:
     lotics setup model.json --email <email>
   It checks the file before anything is created and names every problem at once: fix each
   one in `model.json` and run it again, silently. Then it creates the account and the
   workspace on Lotics's own servers — nothing is built on this machine — with the tables,
   the first rows and the apps, and ends by printing a one-time sign-in link.
   If it says the email already has an account, it prints a link and a four-character code:
   tell them to open the link, sign in if they are asked to, check that the page shows those
   four characters and press Confirm, then run the same command again. If it says this
   machine is already signed in, run it without --email. If it lists several workspaces instead of running, name
   them to the person by their names alone and let them pick one; then select it and run the
   command again.
7. Give them the link immediately — it EXPIRES IN FIFTEEN MINUTES — before you do anything
   else. If none was printed, run  lotics auth web , which emails them one, and say so.
8. Then tell them, in their own words, what they now have: each table by the name they gave
   it, each app by the job it does, and that the chat inside Lotics works on those tables —
   they can ask it there to add a field, change a view or fix a row. Offer to change anything
   now. Later additions are yours to run, not theirs to know: more tables, fields or apps is
   an edit to `model.json` and
     lotics model apply model.json
   which adds what is new and never renames or deletes; renaming goes through the chat
   or  lotics run update_table .