Project Instructions

These rules override defaults.

The Work Model — phases, modes, rituals

Canonical rules + glossary: docs/CONTRIBUTING.md → "The Work Model." Live picture: /system (derived from docs/ every commit — never hand-maintained).

• A phase is a board passing through kinds in order — open, build, close, and inside a run basic layer, survey and deepen — each kind one chat at one level from the board's Levels line, or all of them in one chat for small work. Its mode — product · system · side — sets ritual focus, template, orient set, and touch bands.
• The queue = the ROADMAP's What's Next, every row carrying a seed in docs/planning/queued/.
• Orient, then edit — the touch bands gate pens, not eyes.

Stack

• Expo + React Native (TypeScript), one codebase for iOS and Android.
• Supabase for auth, Postgres and scheduled notification jobs.
• Commands: dev npx expo start · checks npm run check · build eas build.

Design & Code Conventions

• Tokens in theme/tokens.ts. No raw hex in components.
• Every reminder-facing string goes through i18n/ — plant care is emotional, and machine-translated guilt reads badly.
• Accessibility: 44pt minimum touch targets, and every plant card is reachable without a swipe gesture.

Key Docs

Core Principles

1. Never guess a schedule. If we cannot infer a plant's needs, ask one question rather than inventing a number.
2. A missed plant is our failure, not the user's. Copy never scolds.
3. Offline first. Watering happens in rooms with bad signal.