AI Gives You Answers.
The Stack Lets It Ship.

I'm not a developer. Please set up Infinite Leverage for me, and do as much
of it yourself as you can.

HOW TO WORK WITH ME
- I am on a Mac. Everything runs in the Terminal. There is no WSL or Ubuntu
  step for me.
- Plain English only. No jargon. Never paste a raw error at me: tell me
  what it means and what you need from me.
- Don't show me long command output. Just tell me what happened.
- One question at a time, then wait for my answer.
- Never ask me to edit a file. Tell me what to paste, and you make the change.
- If you need my permission to run something, say in one sentence what it
  does, then go ahead.
- Every time we finish one of the steps below, tell me "You are now at
  step N: <name>" and remind me to click that step under "Where are you at?"
  on The Stack page, so my progress stays up to date.
- If I say I'm lost, tell me which step I'm at, what the screen in front of
  me should look like, and point me to the setup map on The Stack page.
- If I paste this prompt into a new chat, check what is already done and
  carry on from the first step that isn't.

THE 11 STEPS
1. Mac ready, the Claude desktop app installed and signed in on a paid plan.
2. Terminal open, it ends in % or $, and git --version answers. If it offers to install the Command Line Tools, accept.
3. Code tab open, a model picked, and the folder inside code-projects.
4. Infinite Leverage installed: typing /il in the Code tab box shows il-doctor in the list.
5. GitHub, Vercel and Supabase accounts created, all with one GitHub login, and Vercel on the free Hobby plan.
6. Authorize clicked for all three CLIs: gh, vercel and supabase.
7. The project files are visible on github.com.
8. The .vercel.app address loads in the browser.
9. .env.local has the Supabase keys.
10. The contacts table exists in Supabase.
11. The contact form on the .vercel.app address writes a row to that table.

THINGS ONLY I CAN DO
You're not allowed to do these for me. When you reach one, stop, give me
click-by-click instructions, and wait for me:
- Signing in to GitHub (gh auth login)
- Creating accounts: GitHub, Supabase, Vercel, and Stripe if I need payments
- Copying keys out of those dashboards

Everything else is yours.

START HERE: THE PLUGIN (step 4)
1. Check the claude command works in the terminal (claude --version). If it
   says command not found, install Claude Code's command line with
     curl -fsSL https://claude.ai/install.sh | bash
   then check again.
2. Install the plugin:
     claude plugin marketplace add edge8-ai/infinite-leverage
     claude plugin install infiniteleverage@infiniteleverage
   If an "infiniteleverage" marketplace is already there from an older
   install, remove it first (claude plugin marketplace remove
   infiniteleverage), then add it again.
3. Run claude plugin list and confirm infiniteleverage is installed and
   enabled.
4. Skills only load when a chat starts, so this chat may not see them yet.
   Tell me to start a new chat in the Code tab, in the same folder, and paste
   this same prompt again. In the new chat, check /il-doctor (or its full
   name, /infiniteleverage:il-doctor) is found before going any further.
   Do not improvise and do not build without the skills.

THEN
1. Tell me which accounts I'll need and let me go create them. On Vercel I
   pick the free Hobby plan; I upgrade to Pro only once the site moves to
   production. Don't carry on until I say I'm ready.
2. Run /il-doctor. Fix whatever you can fix yourself. For anything you can't,
   walk me through it, then run it again until every line passes.
3. Run /il-project to build my project:
   - Call it: <PROJECT NAME>
   - Folder name: <project-name-with-dashes>
   <Describe your business in a few sentences: what it does, who it's for,
   what you want built first. Mention a website you like the look of if you
   have one. Delete this line to answer questions later instead.>
4. Set up my keys. Tell me exactly where to click to find each one, I'll
   paste the values to you, and you put them in the right file. Confirm
   afterwards that the file with my keys in it won't end up on GitHub.
5. Check that the project builds.
6. Do not put anything on GitHub until you've asked me first.

WHEN YOU'RE DONE
Tell me, in plain English: what you built, where it is on my computer, and
the three things I should try first. Keep it short.

IF YOU GET STUCK
Stop and tell me. Don't guess, don't invent a workaround, and don't tell me
something worked when it didn't.