Request from AI: Clearly describe the page, location, actions, and inspection methods

Replace "looking good" with actionable words. Feedback on specific issues, and understanding the scope of impact before making important changes.

Start with a specific request

"Help me build a website" doesn't specify what it's about. "Add a support button on the homepage of this blog, write 'Please have me a cup of coffee,' and after clicking it, display my payment instructions," making it easy to execute. When modifying text, provide the AI with the actual URL, original text, and new text. For example: "Replace the homepage 'Welcome to My Site' with 'My AI Website History', and keep the rest of the section. This way, both the location and the scope are clearly stated.

Make a purchase page and explain all four things

• What to sell: themes, plugins, or other files you have the right to provide, and what are they used for?
• How much: Clear pricing, set the official amount in the management interface.
• How to pay: Shows which method to use, who verifies receipt, and whether it is connected to the automatic interface.
• How to deliver: Buyers leave their email address, when and which documents will be received or how to download them.

Without clearly stating delivery, AI might just draw a "buy" button; If the payment status is not clearly stated, the page may treat the user's click as a success. These business rules must be expressed first.

A demand that can be used directly

I already have a WordPress blog. Create a small plugin: display product name, description, price, and payment code on the front end, and have buyers fill in their email to generate purchase records; You can view the records in the backend. I manually check accounts and send emails. Buyers clicking "I have paid" can only request verification; it will not be automatically marked as credited. First, list the areas to be modified and the inspection steps, then implement according to the authorized scope.

This passage provides the purpose, input, status, administrator responsibilities, and inspection methods. The first version completes it first, then considers automation and other pages.

When reporting an error, state "where, what was done, what occurred."

Good feedback: "After entering my email address on the product page and clicking submit, the page shows successful, but there is no record in the backend. This happened this afternoon, and the screenshot has covered private information. "You don't need to judge the cause first. You only need to describe what actually happened, what you expect from the results, and the prompts you see, so the AI can look up the real problem. When providing screenshots, browser errors, or logs, passwords, keys, and buyer email information are hidden.

The AI asks what evidence is needed after completion

Require it to provide the actual website, backend entry, which files or settings have been changed, and which behaviors have been verified. Then you open it yourself and click step by step. Sending only a rendering image or generating code does not guarantee the official website has been successfully installed. Before modifying important content, have the AI explain in Mandarin: "What problems does this operation solve, which websites or materials will it affect, and how to recover from failures." "If you don't understand, explain first; Don't replace key choices with "whatever you want."

Break down big tasks into checkable steps

Start by reading only to check the current situation; Reinstallation environment; Then open the blog; Then create another feature; Then check the payment and delivery. Each step leaves a verifiable result, so if an error occurs, you know where to check back. If it keeps failing, let the AI summarize the confirmed facts, mistakes, and attempts, and adjust its approach. Repeatedly reinstalling or rewriting the same page makes it harder to tell where the real improvements are.

How can you practice?

First, ask the AI to change just one sentence, add a button with a clear purpose, and finally create a form that can save your email. Check every time you open the actual page. You don't need to know how to code first, but you need to be able to clearly explain whether the results meet your requirements.