How the tool behaves, and how to work with it
- Colin Li
Nine posts. These are not steps to complete once. They describe behaviour that applies in every session.
Read them in this order the first time. Afterwards, return to whichever one is relevant.
What the tool is
1. Chat and Code are two different tools
2. It forgets, it guesses, and it states both in the same tone
How to ask
3. Have it interview you before it writes anything
4. You approve the documents. You do not write them
How to check
6. A tool is not a reliable reviewer of its own output
7. Ask how to check the work, not whether it worked
Two rules that have no exceptions
8. Read the permission prompt before you answer it
9. Never paste a password, a card number, or a key
The two most important: have the tool interview you before it builds anything, and ask it how to check its work rather than whether the work is done.