Brief the work.
Build carefully.
Verify the result.

Separate a generated suggestion from a tool action, then turn a small contact-form request into something you can inspect and verify.

Replace “improve this form” with a bounded goal, relevant context, allowed files, acceptance checks, and explicit reasons to stop and ask.

Build a compact project handoff without confusing the current context, durable instructions, model training, and a summary of earlier work.

Use a claim ledger and a data boundary to decide what can be checked locally, what may be shared, and which actions require a separate approval.

Choose the current official setup for your environment, open a disposable project, and verify a read-only contact-form inspection before allowing edits.

Turn verified project facts into concise Claude Code instructions, keeping durable rules separate from one-off tasks and permission enforcement.

Improve one contact-form behavior with a scoped plan, a failing acceptance check, a small patch, and an independent review of the resulting diff.

Identify your current Codex environment, inspect a disposable repository, and verify the returned file inventory before authorizing a modification.

Describe verified project facts, commands, and approval boundaries for Codex, then check how root and nested guidance apply to the next task.

Choose the smallest extension for a repeatable workflow, and identify what it can read, execute, or send before adding it to a project.

Separate working-file isolation from security and hosted execution, then choose a workspace with an explicit plan for setup, review, and cleanup.

Choose reusable guidance, a connector, bounded delegation, or a scheduled check based on the task’s real need and the access each option requires.

Transfer a bounded project state with files, evidence, limitations, and a next action instead of assuming two agents share conversation history.

Split independent work with named file owners, dependency gates, a shared budget, and an integration review that catches cross-task assumptions.

Combine a regression check, diff inspection, browser behavior, and explicit limits so a passing command cannot hide an incomplete contact-form change.