AI tool setup

Cursor auto-indexes the open folder, including AI_CONTEXT.md. As long as you've opened the repo as your project root, the file is in Cursor's context.

1. Open Cursor.
2. File → Open Folder and pick the cloned repo (the folder with AI_CONTEXT.md at the top level).
3. Open the chat panel.

Then paste the first-prompt template. If Cursor seems to ignore the file (rare on a small repo), pin AI_CONTEXT.md in the chat manually via the paperclip icon.

Same story as Cursor. Windsurf auto-reads files in the open project, so AI_CONTEXT.md is picked up.

1. Open Windsurf.
2. File → Open and pick the cloned repo folder.
3. Start a new Cascade conversation.

Then paste the first-prompt template. Windsurf tends to ask before editing — answer "yes" the first time and it'll get into the rhythm.

Claude Code (the desktop CLI / IDE plugin) doesn't auto-read every file in your project. To make sure it reads AI_CONTEXT.md first, reference it explicitly at the start of your conversation.

1. Open the cloned repo folder in your terminal.
2. Start Claude Code (claude in your shell, or open it from your IDE).
3. In the first message, drag AI_CONTEXT.md into the chat to attach it as a file reference, or type @AI_CONTEXT.md and Claude will pick it up.

Then paste the first-prompt template below.

Cline is a VS Code extension — it sees your whole workspace, so AI_CONTEXT.md is in context as soon as you open the repo folder.

1. Open VS Code and use File → Open Folder on the cloned repo.
2. Click the Cline icon in the sidebar to open the chat.
3. In the first message, type @AI_CONTEXT.md to pin the file explicitly (Cline's recent versions auto-discover it, but pinning is foolproof).

Then paste the first-prompt template. Cline runs locally and asks for approval before each file edit — useful while you're getting comfortable; switch to auto-approve later if you want.

OpenAI's Codex CLI runs in your terminal and reads files in the working directory like Claude Code. You'll need a ChatGPT Plus / Pro / Team / Enterprise login.

1. Open the cloned repo folder in your terminal.
2. Run codex (after installing via npm install -g @openai/codex or the OpenAI installer).
3. In the first message, type @AI_CONTEXT.md to bring the file into context.

Then paste the first-prompt template. Codex defaults to ask-before-editing — exactly the safe default for a Hatchik sandbox.

Antigravity is Google's agentic IDE built around Gemini. It opens project folders like VS Code and auto-indexes the contents — AI_CONTEXT.md is in scope from the moment you open the repo.

1. Open Antigravity.
2. File → Open Folder and pick the cloned repo.
3. Open the agent panel and start a new conversation.

Then paste the first-prompt template. If Gemini seems unaware of the file, attach it explicitly via the paperclip icon — same fallback as Cursor.

If you don't have a dedicated coding tool, any browser-based AI works for small changes — you just do more copy-paste than file-editing. The loop still works.

1. Open the chat (chat.openai.com, gemini.google.com, grok.com, claude.ai, or Comet) and start a new conversation with a code-capable model.
2. Click the attach / + icon and upload AI_CONTEXT.md from your cloned repo folder.
3. In the same message, paste the first-prompt template.

None of these can run git push from inside the browser (Comet is the partial exception — it can run shell commands if you grant it access). For the others, copy edited files back into your repo yourself and run git push in your terminal — or use Hatchik's redeploy URL from AI_CONTEXT.md if you'd rather not touch a terminal at all.

I want to build [PRODUCT NAME]. The idea is: "[ONE-LINE
DESCRIPTION]". This repo is a Hatchik substrate — auth, database,
hosting and email are already wired up. The live sandbox is at
[YOUR-SANDBOX-URL] and the Supabase anon key is in AI_CONTEXT.md.
Read AI_CONTEXT.md, then help me design the first feature: a
minimal user-facing flow that proves the core value. Put new UI
under apps/web/src/product/ and new API routes under
apps/api/src/product/. Don't touch the substrate files.