Notes for your AI

Every new AI chat starts with a blank memory. Instead of explaining your project again and again, you can write it down once in a notes file the AI reads automatically.

What are notes for your AI?

Imagine a new team member joins your project every morning. You'd give them a welcome sheet: "We use these tools. We follow these rules. Please don't touch this folder." That's exactly what these notes are.

An instruction file is a short document of lasting rules for your AI. Different tools call it different names:

• Claude Code reads a file called CLAUDE.md in your project folder at the start of every session.
• Claude, ChatGPT, and Gemini let you add project instructions or custom instructions in their settings or project pages.
• AI app builders like Lovable usually have a knowledge or project settings area for the same purpose.

The names change, but the idea is the same: rules written once, followed every time.

Why they keep AI consistent

Without notes, the AI might use one style on Monday and a different one on Tuesday. It might add a new library you didn't want, or forget a safety rule.

What to put in your notes

• Project summary — one or two sentences, plus a pointer to your PRD.
• Tech choices — the framework, database, and styling you use.
• Rules — guardrails that always apply.
• Style — design and writing preferences.
• How to work with you — "explain changes simply", "ask before big changes".

A notes template

Copy this into a CLAUDE.md file, or paste it into your tool's project instructions.

# Project notes for AI

## About this project
[One or two sentences about the app.]
Full plan: see docs/PRD.md

## Tech choices
- [Framework, e.g. Next.js]
- [Styling, e.g. Tailwind CSS]
- [Database, e.g. Supabase]

## Rules
- Make small changes, one feature at a time.
- Don't change files that aren't related to the task.
- Don't add new packages without asking me first.
- Never put secret keys in frontend code. Use .env.local.
- Never commit .env or .env.local.

## Style
- [Design style, e.g. clean, calm, lots of white space]
- [Colors, fonts]
- Use simple, friendly words in the app's text.

## Working with me
- I'm a beginner. Explain what you changed in plain English.
- If something is unclear, ask me before you guess.

Let's break this down:

• "See docs/PRD.md" points the AI to the bigger plan instead of repeating it.
• The rules are short, one per line, and easy to check.
• "I'm a beginner" changes how the AI explains everything to you.

Keep your notes up to date

Notes work best when they're short and current. When you notice the AI making the same mistake twice, add a rule.

You keep using blue buttons, but our design uses green.
Add a rule about this to CLAUDE.md so you remember next time.

Common mistakes

• Writing pages and pages of rules. Keep notes short, so the AI can follow every one.
• Copying the whole PRD into the notes. Point to it instead.
• Vague rules like "write good code". Be specific: "use Tailwind for all styling".
• Never updating the notes when your tech or plans change.

What's next?

You now have all the documents you need. Next, let's put everything together and turn an app idea into a clear, step-by-step build plan.