Global rules apply. Communication style + Agent Directory routing live in
~/.claude/CLAUDE.md— read that first. This project participates in the directory; use/send-toto ask peers.
MemPalace wing: keepsimple (protocol lives in ~/.claude/CLAUDE.md).
Human-readable agent guidelines live in AGENTS.md next to this file; this file is the machine-facing version. See AGENTS.md for repo conventions, build/test commands, and contribution rules.
Repo is indexed by CodeGraph (MCP codegraph, registered globally). Use it FIRST when you have a symbol name: codegraph_search, codegraph_callers/callees, codegraph_context, codegraph_impact, codegraph_files. Grep/Glob only when query is conceptual or CodeGraph returned nothing. Index lags writes ~500ms.
When writing copy that ships to users (microcopy, page headings, marketing blurbs, articles, error messages):
- First-person, direct, no filler.
- Em-dashes and semicolons over staccato fragments — let sentences breathe; reserve short fragments for deliberate punctuation, never as default rhythm.
- Cross-disciplinary framing welcome when it actually fits (behavioral science × product × longevity × AI).
- Sparse profanity is fine when it lands; default to clean.
- No AI-isms — no "let me know if…", no "happy to help", no preamble before the answer.
- Reference piece: "The Rise of the Choice Architect" (article on keepsimple.io). Match its register.
The 100+ cognitive biases in UX Core are the product of 5+ years of curation and are referenced by Duke, Harvard, MIT, Google, Yandex, Amazon, and others.
- Never fabricate bias names, slugs, citation indices, or source URLs.
- If you need structured bias data, pull from
/uxcore-api(see AGENTS.md → Public data API). Don't scrape, don't paraphrase from memory. - Schema changes to UX Core data require explicit approval.
When you find yourself stuck > 10 minutes on a problem and figure it out, write a brief drawer in your wing — chronology + fix. Next-session-you won't waste the same 10 minutes. Same when a deployment/config decision is non-obvious — capture why alongside what.