Patrick Toal
e1259688a4
Some checks failed
Build BAB Application Deployment Artifact / build (push) Failing after 2m40s
52 lines
3.1 KiB
Markdown
52 lines
3.1 KiB
Markdown
# CLAUDE.md
|
|
|
|
## Session Start
|
|
|
|
Read the latest handoff in docs/summaries/ if one exists. Load only the files that handoff references — not all summaries. If no handoff exists, ask: what is the project, what type of work, what is the target deliverable.
|
|
|
|
Before starting work, state: what you understand the project state to be, what you plan to do this session, and any open questions.
|
|
|
|
## Identity
|
|
|
|
You work with Patrick, a Solutions Architect, on the OYS Borrow a Boat (bab-app) project — a Quasar/Vue 3 app for managing a Borrow a Boat program for a Yacht Club. Backend is Appwrite.
|
|
|
|
## Project Overview
|
|
|
|
- **App**: OYS Borrow a Boat (oys_bab)
|
|
- **Stack**: Quasar (Vue 3), TypeScript, Appwrite (BaaS)
|
|
- **Purpose**: Manage a Borrow a Boat program for a Yacht Club
|
|
- **Docs**: docs/planning/ contains personas, user/role/permission model, and time-based logic
|
|
|
|
## Rules
|
|
|
|
1. Do not mix unrelated project contexts in one session.
|
|
2. Write state to disk, not conversation. After completing meaningful work, write a summary to docs/summaries/ using templates from templates/claude-templates.md. Include: decisions with rationale, exact numbers, file paths, open items.
|
|
3. Before compaction or session end, write to disk: every number, every decision with rationale, every open question, every file path, exact next action.
|
|
4. When switching work types (research → writing → review), write a handoff to docs/summaries/handoff-[date]-[topic].md and suggest a new session.
|
|
5. Do not silently resolve open questions. Mark them OPEN or ASSUMED.
|
|
6. Do not bulk-read documents. Process one at a time: read, summarize to disk, release from context before reading next. For the detailed protocol, read docs/context/processing-protocol.md.
|
|
7. Sub-agent returns must be structured, not free-form prose. Use output contracts from templates/claude-templates.md.
|
|
|
|
## Where Things Live
|
|
|
|
- templates/claude-templates.md — summary, handoff, decision, analysis, task, output contract templates (read on demand)
|
|
- docs/summaries/ — active session state (latest handoff + project brief + decision records + source summaries)
|
|
- docs/context/ — reusable domain knowledge, loaded only when relevant to the current task
|
|
- processing-protocol.md — full document processing steps
|
|
- archive-rules.md — summary lifecycle and file archival rules
|
|
- subagent-rules.md — rules for structured sub-agent outputs
|
|
- docs/planning/ — original planning documents (personas, roles/permissions, time logic)
|
|
- docs/archive/ — processed raw files. Do not read unless explicitly told.
|
|
- output/deliverables/ — final outputs
|
|
- src/ — Quasar/Vue app source
|
|
- src-pwa/ — PWA config
|
|
- appwrite.json — Appwrite project config
|
|
|
|
## Error Recovery
|
|
|
|
If context degrades or auto-compact fires unexpectedly: write current state to docs/summaries/recovery-[date].md, tell the user what may have been lost, suggest a fresh session.
|
|
|
|
## Before Delivering Output
|
|
|
|
Verify: exact numbers preserved, open questions marked OPEN, output matches what was requested (not assumed), claims backed by specific data, output consistent with stored decisions in docs/context/, summary written to disk for this session's work.
|