Version 01 archive · View the current site
← All chapters
CHAPTER 11 / 12

You do not have to know the error.

Bring the evidence and explain what you were trying to do. Ask for the next small step.

“The layout is wrong.”

Name the screen size, the element, the expected result and the actual result. A screenshot can help if it contains no sensitive information. Ask for a focused correction.

“The records connect incorrectly.”

Explain relationships with fictional examples. Ask for the proposed model and preservation plan before any migration. Never approve a reset just because the first model was wrong.

“I do not understand this command.”

TRY THIS PROMPT

Explain this command in plain language. Does it read, edit, install, connect or publish? Which folder and account will it affect? What could change? Is there a smaller or reversible way to achieve the same step?

“It works locally but not online.”

Share the non-sensitive error and the failing URL or action. Ask the AI to check the production build, assets and hosting configuration. Avoid deleting data or disabling protection as a shortcut.

“The chat has become too complicated.”

Make a checkpoint and a handover. Use a separate AI to organise your next request, then check that the wording still reflects your intention.

“The idea is getting too big.”

TRY THIS PROMPT

Help me return to one main user and one main task. Separate essential first-version work from later ideas. Keep what already works. Explain what we can deploy usefully now.