CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Role & Responsibilities
Your role is to analyze marketing requirements, delegate tasks to appropriate
BEFORE attempting fixes
- **TDD**: write the failing test first, then minimal code to pass
- **Codereview**: verify feedback technically before implementing
### 7. Architectural Invariants
Before adding endpoints, services, DB tables
engine is wrong, add a deterministic `test/repro-model-*.test.ts` that fails
before changing runtime code; if the specification is wrong, correct the model
with evidence. Never weaken an invariant to make
test:sandbox:sdk` passes every official SDK in isolated containers;
review `artifacts/test-sandbox-sdk/ /summary.md`, not only the exit
code.
5. The repository-wide `bun run test:sandbox` gate is also green
Extra workflows | — | Morning Briefing, Weekly Report, Google Reviews, Instagram Posting, Memory Consolidation |
dmo-claw has its own VPS, DB, and workflows. Code changes to core agent logic should be made
squash-merge is fine — that one is generated by GitHub, not by Claude Code.
## Style
- **No `Generated by Claude` / `Drafted by AI` markers** in source files, docs, or PR bodies
path. |
| `onto_map` | To generate a mapping config from data schema + loaded ontology for review |
| `onto_ossie_import` | To compile an Apache Ossie (incubating, formerly Open Semantic Interchange) ontology document
ES2022, **Module**: NodeNext, **Strict**: true
- **Root tsconfig.json**: Server code (src/ excluding src/client)
- **tsconfig.client.json**: Browser/client code
- Two separate `--noEmit` checks in `npm run typecheck`
- Packages use their own tsconfig extending
plugins you actually modified
No build step required. Changes take effect on Claude Code restart.
### Plugin Development Skills (ALWAYS USE)
When creating or modifying plugin components, **ALWAYS** use the `plugin
history cleaner and easier to review, revert, or cherry-pick individual changes.
## Schema Note
`.claude/settings.json` is validated against Claude Code's bundled JSON schema. The schema's `propertyNames` enum
CLAUDE.md
Codex will review your code from three dimensions: maintainability, boundary conditions, and regression risk, and the quality of your code will determine whether the system can go live. Please
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.