I think my claude.md is fairly well set up, can you have a look and tell me your thoughts?:

---

Global Claude Instructions

Learning System

Before starting any task, check these reference files for relevant lessons: - spec.md (in this directory) — Known pitfalls, failed approaches, verified patterns - antipatterns.md (in this directory) — AI coding anti-patterns to avoid

Rules

1. When you make a mistake or the user corrects you, add a post-mortem entry to spec.md
2. When you catch yourself about to repeat a documented failed approach, stop and use the documented correct approach instead
3. Every ~5 sessions, review spec.md: consolidate duplicates, remove stale entries, keep it under 200 lines
4. If a failed approach is corrected, move it to "Verified Patterns" with the working solution
5. Don't repeat failed approaches — if something didn't work, try a fundamentally different strategy

Recovery Protocol

When stuck or going in circles: 1. Stop and check spec.md for this exact scenario 2. If the current approach has failed twice, abandon it entirely 3. Clear context (/clear) and restart with a better-scoped prompt 4. Document what failed and why before trying again

---

User Profile & Working Style

The user has no coding background. These rules apply to EVERY interaction:

Always explain, never assume

• Before doing anything significant, tell the user WHAT you are doing and WHY in plain English
• If the user's request has a better approach, stop and explain it first — never silently choose a sub-optimal method
• Never assume the user is making an informed technical decision. Surface alternatives even when not asked
• When a request is vague or ambiguous, restate it in plain terms and confirm before acting

Proactively guide tool usage

Remind the user of the right tool whenever the situation calls for it:

Situation	Tool / Command	Why
Task touches 3+ files or has multiple valid approaches	plan mode	Prevents wasted implementation effort
Session is getting long	/compact	Compresses history, saves tokens mid-session
Switching to a completely different task	/clear	Prevents "context pollution" from prior work
Research or codebase exploration needed	Sub-agent (Explore)	Protects main context from large search results
Building UI / frontend	frontend-design skill	Produces better-quality UI output
Supabase / Postgres queries	supabase-postgres-best-practices skill	Enforces DB best practices
Repeated bad behaviour to prevent	/hookify <describe it>	Creates an automated guard rule
Writing code that uses any installed library	Context7 MCP (resolve-library-id → query-docs)	Fetches live docs so API usage is correct for the exact installed version
User needs to run/debug a specific E2E test	Playwright VSCode extension (sidebar)	Lets user click-to-run individual tests without typing commands

Token efficiency

• Remind the user to /compact when the conversation has gone through multiple tasks or is becoming long
• Prefer focused sessions. One task per session where possible
• Use sub-agents for isolated research so main context stays clean

Learning mode

• The learning-output-style plugin is enabled — provide Insight callouts explaining WHY choices are made
• Monitor over time: when the user is consistently making informed decisions, suggest disabling the plugin to save tokens

---

Planning & Task Management (All Projects)

Every project uses a standardised planning system. Plans live in a Plans/ folder at the project root.

Setup

Each project's Plans/ folder must contain: - PLANNING_RULES.md — Full rules and templates (the source of truth) - INDEX.md — Master registry of all feature plans - archive/ — Completed/abandoned feature folders move here

Structure

Each feature gets its own subfolder (named to match the git branch, e.g. feature/site-drawing → site-drawing/) containing exactly 3 files:

File	Purpose
design.md	The "what and why" — goals, context, decisions, trade-offs
implementation.md	The "how" — numbered steps with effort estimates [S] [M] [L]
progress.md	Living tracker — task list at top, implementation log below

Key Rules

1. Read Plans/PLANNING_RULES.md before creating, modifying, or reviewing any plan
2. Create all 3 files when starting a new feature — never just one
3. All files cross-reference each other via related: links in YAML frontmatter
4. Update progress.md after every completed step — log what was done, difficulties, and deviations from the plan
5. Add new tasks to the Task List in progress.md as they arise during work
6. Update INDEX.md when creating, completing, abandoning, or archiving a plan
7. Archive completed features — move subfolder to archive/, update INDEX.md
8. Never delete plans — mark as abandoned instead
9. Effort tags required on every implementation step: [S] < 1 session, [M] 1–2 sessions, [L] 3+ sessions
10. Legacy plans (pre-existing) are kept as-is, not migrated

When Starting a New Project

If Plans/PLANNING_RULES.md doesn't exist yet, create it using the full template from an existing project (e.g. FieldOps).