codexCall codex (GPT-6) through the purpose-session runner for research, web lookups, and project prose or jev questions where a project's rules say codex writes them.
dev-roundHow to work through the code to-dos of an area in three passes: build every to-do (and the findings that turn up) with its tests, running none, until none is left; then test the area (the full suite at 100% coverage, the tests checked, failures fixed at their root) and mark what passed as tested, bu
loopEngage this session's own loop and follow its law for execution, pausing, and completion. A loop is per session; its loop file sets its board and areas.
researchDeep research through codex on gpt-6-astra, like ChatGPT's or Gemini's deep research: codex asks what is unclear and plans sub-questions for the owner to approve, searches the web for each side by side, searches again to close the gaps, writes one cited report, and every citation is checked on the p
roastHave codex push back on a plan before building, a finished task, a run of tasks, or a question: codex checks the work itself and frames typed questions, jev judges the logic, codex writes its reading.
rulesThe owner's rule sets: general, dev (development), design, and the current project's own rules. Load them only when the owner calls /sijav-clauder:rules (for example /sijav-clauder:rules dev); never load them on your own. Also holds the procedure for changing any rule.
searchA plain web search through codex, on gpt-6-luna at low effort: one question, a short answer, and the links it used. For a quick fact, a current version, an API detail or a doc page. A question that needs many sources and judgement is research, a separate skill.
todoThe project board, a real SQLite database, for projects that have a .claude/todo.db. In those projects use it instead of TodoWrite: picking the next task, creating one, changing a status, or recording anything found mid-task.