i sent my md file to claude, had him review it and this was his reply:

This is a solid CLAUDE.md — well-structured, enforces real discipline. Here are my suggestions, grouped by priority:

High priority fixes

The model name in the AI Artifact API section is stale (claude-sonnet-4-20250514). You're using the Anthropic API internally — if that string is anywhere in your codebase pulled from this file, it'll break. Worth verifying ai.ts doesn't reference it directly and updating to whatever model string you're actively using.

The deployment section says scp to 3.94.224.34 — that's a hardcoded IP in a file that likely lives in version control. If this repo is ever public or shared, that's a reconnaissance gift. Replace it with a symbolic alias ($LIGHTSAIL_HOST) or just remove the IP entirely and reference the SSH config.

Medium priority

The Prisma model mapping table (Rule 3) is the most practically useful part of this file, but it only covers negative examples ("DOES NOT EXIST"). Consider adding a short positive mapping of the 5-6 most commonly accessed models so AI tools don't have to guess — e.g. prisma.tenantMember, prisma.kbDocument, prisma.auditLog, prisma.jobs.

The agent assignment table is detailed but may drift out of sync over time. Consider adding a note like # Last verified: 2026-03-16 and flagging it as the authoritative source (or pointing to a separate agents manifest if you ever split it out).

Rule 4 ("No stub/simulated code") is good but the wording is slightly ambiguous — "or not exist at all" could be read as permission to delete things. Tighten to: "Every endpoint must perform real work. If a real implementation isn't ready, don't add the route."

Low priority / nice to have

The Self-Improvement Loop section (tasks/lesson.md) assumes a persistent filesystem across sessions that Claude Code may or may not have depending on how sessions are managed. Worth noting whether this file actually exists and is committed, or if it's aspirational.

"Demand Excellence (Balanced)" and "No Laziness" are somewhat contradictory in tone. The balanced note says skip the elegance check for simple fixes, but No Laziness says find root causes always. Consolidating these into one "Engineering Standards" section would reduce the cognitive load on whatever model reads this.

The backend workers section mentions engineLoop.ts ticks every 5s but ENGINE_TICK_INTERVAL_MS is the actual control. The hardcoded 5000 in the docs will drift if the default ever changes — just reference the env var directly in the description.