Quick answer
A good brief names the website, approved environment, desired visitor behavior, and a measurable acceptance check. It also identifies what the assistant may inspect or change. This gives it a concrete task and helps prevent unrelated edits or a deployment to the wrong account.
Apply this guidance to your website task
Before you start
Collect a current URL, relevant screenshot or error, the CMS/framework, and the location of a safe development copy. Remove passwords, private keys, personal customer data, and unrelated project information from the material you share.
What to do
- Describe the observed problem and expected result, including the page, device width, browser, and steps that reproduce it.
- Name the permitted local folder or staging domain, the live target if a later deployment is intended, and any exclusions such as checkout, billing, email, or other sites.
- Ask for an initial read-only inspection and a small proposed change. State any business facts, approved copy, design reference, or compatibility constraint.
- Define verification: the affected interaction, mobile behavior, relevant automated check, and rollback requirement. Authorize publication separately when the result is reviewable.
Check the result
The assistant should be able to repeat the target, scope, and success criteria before editing. Review the resulting diff against that brief, not just the appearance of a single screenshot.
If something does not work
If the brief exposes several unrelated problems, separate them into tasks with their own evidence and tests. Keep a short decision log so a later session can continue accurately.
For instructions you want a coding tool to reuse across sessions, use the AGENTS.md and CLAUDE.md project guide. Keep the task brief and persistent project rules distinct, and verify the loaded files before the first edit.
Related help
- Prepare a useful brief for a new website
- Review an AI-generated website change before deployment
- Share website errors with an AI assistant without exposing secrets
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
Task guidance and related-help review: November 1, 2026.
AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.
