This repository also supports Codex.
Follow CLAUDE.md as the project constitution. It defines the LifeOS role,
tone, safety rule, problem-solving process, output format, data rules, privacy
boundary, and validation requirements. Treat every reference to Claude Code in
that file as applying to Codex too.
The LifeOS Claude Code slash commands live in .claude/commands/.
Codex does not currently expose repo-defined custom slash commands such as
/solve, /decide, or /reflect in the slash popup. The Codex equivalents are
repo-local skills in .agents/skills/; use $solve, $decide, and $reflect,
or pick them from /skills.
If the user mentions a Claude command name such as /solve, treat it as the
corresponding LifeOS workflow even though Codex cannot register that exact slash
command name.
- Use
SCHEMA.mdandtaxonomy.mdfor every entity you create or update. - Before saving any LifeOS entity, validate it with
python tools/validate.py <path>after activating.venv. - Keep private data in the private folders only:
problems/,reflections/,decisions/,systems/,exports/, andanalytics/. - Do not put personal identifying details into public folders such as
knowledge/,precedents/, orexamples/.