Caluru

Start here

You don’t need to know how to code to work on Caluru. You work by talking to Claude. This project contains instructions that Claude reads automatically, so it already knows what Caluru is, the rules, and how to keep everything tidy and saved on GitHub.

One-time setup

You need:

1. A Mac with Xcode (free in the Mac App Store) — to build and try the iPhone app.
2. The Claude desktop app, with this Caluru folder opened in its Code tab, on that same Mac. That way Claude can build the app and run the checks itself. (If you use Claude somewhere else and it doesn’t seem to know the project, start with: “Read CLAUDE.md first.”)
3. Access to the GitHub repository — ask the owner to invite you.
4. The private keys (Supabase, RevenueCat, OpenAI) — the owner sends them to you privately. Claude will create the file they go in (Config.xcconfig) and tell you where to paste each one. Never paste them into the chat.
5. Optional: access to Apple’s App Store Connect (only if you’ll publish new versions) and to Supabase (the database) — ask the owner.

Then just say: “Check the project and set me up.” Claude will check everything and guide you through anything missing, one step at a time.

How to ask for things

Describe what you want the way you’d tell a person. You can write in Spanish or English.

• “On the recipe screen, make the photo bigger and the title bold.”
• “Add a button to the shopping list to send it by WhatsApp.”
• “The Plan tab crashes when I open Sunday. Fix it.”
• “Explain how the weekly plan is calculated.”
• “Change the paywall text to mention the 7-day trial.”

What Claude will do:

1. Repeat back what it understood and ask you to confirm.
2. Build it on a separate copy, so the main version stays safe.
3. Tell you exactly how to try it in Xcode.
4. When you say “it works, save it”, it saves the change, writes it in the changelog and uploads it to GitHub.

Useful phrases

Say	What happens
“Check the project”	Health check: is everything saved, up to date and working?
“Save it” / “Guárdalo”	Saves the finished change and uploads it to GitHub
“Undo that”	Takes back the last change, safely
“What did we do last time?”	Summary from the changelog
“Show me what’s still pending”	Lists unfinished work
“Remember that we decided…”	Writes the decision into docs/DECISIONS.md
“Explain it simpler”	Claude re-explains with no technical words
“Release a new version”	Step-by-step App Store / TestFlight release

Golden rules

• One thing at a time. Finish and save one change before starting the next.
• Try it before you say “save it”.
• Read warnings carefully. If Claude says something affects payments, users’ data or the live database, it will ask you to confirm. If you’re unsure, say “explain it simpler” or “let’s not do that yet”.
• Don’t move, rename or delete files by hand. Ask Claude.
• Start each session the same way: “Check the project.” It takes a minute and catches problems early.
• Never share keys or passwords in the chat, even if you think Claude needs them. Claude will always tell you which file to put them in instead.

Where things are

• docs/CHANGELOG.md — everything that has changed, in plain words.
• docs/DECISIONS.md — product decisions and ideas being discussed.
• CLAUDE.md — Claude’s instructions (you don’t need to read it).