SMARTER USAGE · INMC
Give the task a finish line.
Name the outcome, the relevant input and what must stay unchanged. Start with one deliverable you can check.
USE INCodex or Claude Code
Before you start
- The observed problem and the expected behavior.
- A relevant file, screenshot or reproduction.
How to use it
- Describe the issue in one sentence.
- Name what must stay unchanged and ask for a small fix.
- Agree on one check before expanding the work.
ILLUSTRATIVE EXAMPLE
Make it concrete.
A checkout button stops responding. Investigate its event handler first; keep payment behavior and visual styling unchanged.
Check the result
- The proposed fix addresses the reported symptom.
- The agreed check covers the original failure.
- Unrelated files and features remain outside the scope.
Go to the source.
INMC example. A clearer scope can reduce avoidable rework; no fixed usage saving is promised.
Claude Code · Best practices ↗Codex · Official plan usage guide ↗INMC walkthrough reviewed: 2026-10-09. Examples are original INMC adaptations. Availability varies by account and version.