Give your AI a clear starting point.

Use the prompt below in Codex, Claude Code, or Cursor. You complete account and payment steps in your browser; your agent resumes the installation.

Node.js ≥22.20.0 · pnpm 10.33.2 · Compatibility

Starter purchases and hosted installation are not open yet. Lite is available now.

Open an empty project folder, an unchanged Lite checkout, or your existing Autotomy project.
Paste the setup prompt. Complete sign-in and any purchase yourself when the CLI opens your browser.
Let your agent finish installation, run the checks, and show you the result before building your first feature.

Set up Autotomy in this project. Inspect the current directory, Git status, and node --version first. Autotomy requires Node.js 22.20.0 or newer; if it is older, stop and help me update Node before running the CLI. Preserve all existing work and secrets. Run npx autotomy doctor --json to inspect compatibility, then npx autotomy install for an Autotomy or unchanged Lite checkout; use npx autotomy init <new-directory> for a new project. If the CLI requests authentication or a purchase, show me its browser link and let me complete it myself, then resume the command. Never ask me to paste credentials into chat. Do not bypass compatibility or verification failures, overwrite conflicting files, or subscribe on my behalf. Follow the installed project instructions, report any required hook approval, run npx autotomy check, and show me how to start the app from its expo directory.

npx autotomy install

Use Node.js 22.20 or newer and the package-manager version recorded in the release. Installation and premium commands need a network connection. Native builds also need the matching iOS or Android toolchain.

Lite · Free

Clone the free Expo shell. No account or payment required.

Autotomy Lite · GitHub ↗Explore Lite setup →

git clone https://github.com/LabLambWorks/autotomy-lite.git

Node.js ≥22.20.0 · pnpm 10.33.2 · Compatibility

Full support starts with Autotomy projects. Other Expo repositories receive compatibility findings without automatic restructuring. Modified Lite files produce conflicts rather than silent overwrites.

Compatibility

Codex, Claude Code, and Cursor receive their supported integrations. Your coding tool may require you to trust hooks. Hooks provide feedback; they do not automatically repair source.

Your app source stays on your machine. Autotomy accounts and subscriptions belong to the developer toolkit; they do not add login or payments to your app.

Prompts for the next change

Build one feature

Add <feature> as a cohesive slice in this Autotomy project. Read AGENTS.md and expo/docs/SLICE_ARCHETYPES.md first. Preserve architecture boundaries, explicit error handling, and existing work. Do not modify generated theme CSS directly. Run npx autotomy check, fix failures without weakening gates, and summarize the change and verification evidence.

Repair audit findings

Run npx autotomy audit --json in this Autotomy project. If Pro access is needed, show me the account link and wait for me to complete the browser step. Review each finding's evidence and repair instructions. Fix confirmed issues in bounded changes, preserve unrelated work, and never disable a check to make it pass. Run npx autotomy check and repeat the audit. Report unresolved or unassessed areas explicitly.

Plan an Expo upgrade

Help upgrade this Autotomy project to Expo SDK 58. Start with Git status and npx autotomy upgrade expo --to 58 --json. Read the returned compatibility evidence and blockers. If the target is unsupported or the recipe is blocked, stop and explain; do not invent a migration. Otherwise present the plan and affected files before changing dependencies or source. Preserve customer edits and native configuration, follow official release guidance, and run the prescribed verification including npx autotomy check. Report failures and recovery steps without weakening checks.