Adam’s AI Instructions
繁體中文 · English complete instruction · English guide · Traditional Chinese complete instruction · Traditional Chinese guide
Once an AI can enter your project or workspace—read files, edit files, use tools, or prepare something for release—the question is no longer only whether its answers sound good. You need to know what it looked at, why it took an action, and how you can check the result.
This complete global instruction gives that kind of AI agent a way to work. Put it where your tool applies lasting instructions to a project or workspace. The agent first understands the task and the rules already in place, then gets on with the work. Small jobs stay simple. Work involving data, secrets, publication, or several connected changes comes with a clear account of the risk, outcome, and way to check it.
It is for Claude Code, OpenAI Codex, Cursor, Antigravity, and similar AI agents that can work inside a workspace you have authorized. Ordinary web chat is outside this project’s scope.
Ask an agent to update a README and it should not edit on sight. It first looks for the existing style, the relevant rules, and a result it can read back afterwards. Then it changes only what is needed.
Ask it to research, organize information, or prepare a release and it separates verified facts from open questions and from choices that really need you. Deletion, overwrite, public release, access changes, and spending still wait for your final confirmation.
This does not turn every small task into a process. A clear, reversible fix can be completed directly. Extra checking is for work where an error would be harder to undo or would affect more than one thing.
In common tools, that place is usually called:
| Tool | Project instruction location |
|---|---|
| Claude Code | CLAUDE.md |
| OpenAI Codex | AGENTS.md |
| Cursor | AGENTS.md or Project Rules |
| Antigravity | Workspace Rule |
To see how the agent responds in four common situations, open the English guide or Traditional Chinese guide.
The instruction does not replace your tool’s permissions, sandbox, version control, or backups. Having a prompt does not mean a system is already safe.
Public release, payment, pushing, deletion, access changes, and other irreversible actions still need your clear confirmation. The point is to help the agent make those decisions easier to see before you make them.
When the agent cannot safely begin, it now explains the reason, what has been checked, and the practical next step more clearly. Important work still gets the necessary gap checks, while small work stays direct. See what changed
These instructions work on their own. They govern how an agent judges, changes, and checks work in the current task.
For work that continues across several conversations or agents, Agent Handoff Kit can preserve the current state, handoff, and closeout information. For a longer project that needs to move from ideas through research and validation into a plan, see Innovation Loop. They are useful additions when you need them, not prerequisites for using these instructions.
This project is licensed under the MIT License. If your experience differs from the guide, share the tool name, instruction location, and a reproducible scenario. Do not include secrets or private file content.