CLAUDE.md
The same mobile project rules in the filename Claude-based tools expect.
CLAUDE.md mirrors AGENTS.md. It exists because different coding assistants
look for different instruction filenames.
For this kit it should communicate the same facts and guardrails:
- Expo SDK 57 and the pinned native package versions are the source of truth.
- Uniwind, not NativeWind, owns styling.
- Product changes start by reading
DESIGN.md,DESIGN-DARK.md, andFEATURES.md. - Provider work starts by reading the matching
agent-skills/file. - Mock mode, integration seams, localization, themes, accessibility, and verification remain intact.
- An implementation guide is not permission to deploy or submit.
If Claude appears to ignore a convention, start a fresh project chat from the kit root and send:
Read CLAUDE.md completely before continuing. Identify the skill triggered by my
request and follow it. Do not change production services outside the repository
without asking me first.When you update a project-wide rule, make the same edit in AGENTS.md and
GEMINI.md so behavior does not depend on which tool opens the folder.