Consult Claude

Codex briefs Claude on the problem, proposed design, and reasoning. Claude reads the current checkout and returns its judgment, alternatives, and objections. Codex owns implementation and verification; when Claude needs a test, benchmark, or experiment, it requests that evidence from Codex.

Make the design legible

Supply the desired outcome, genuine constraints, actual and proposed API code, representative callsites, relevant implementation excerpts with source paths, and your engineering reasoning and unresolved questions. Use an ASCII diagram when it clarifies ownership, lifecycle, or data flow. Distinguish observed facts, proposals, assumptions, and preferences. Give enough concrete evidence to judge the decision immediately; Claude can read further to verify your account.