The playbook
AI Website Building: Template and Field Guide
This AI website building template turns a broad task into a record another person can use. It captures prompt, page, expected behavior, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
A useful prompt names the audience, offer, pages, brand rules, required interactions, and the source of factual content. Ask for a working confirmation and error state for forms. Inspect the resulting implementation instead of assuming every visible control is connected.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| prompt | Record the prompt associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| page | Record the page associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| expected behavior | Record the expected behavior associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| test result | Record the test result associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with prompt. Use the same reference throughout the record so notes are not attached to the wrong item. Then describe audience offer page structure and brand rules. This establishes the information required before the worksheet becomes a request for action.
Next, review generated content and interactions page by page. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as treating a convincing preview as proof the whole website works, rather than a broad instruction to “improve performance.”
Finally, test responsive behavior accessibility and real form destinations. Put run actual visitor journeys and correct unsupported claims or actions in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Treating a convincing preview as proof the whole website works |
| Action | Run actual visitor journeys and correct unsupported claims or actions |
| First check | Describe audience offer page structure and brand rules |
| Follow-up check | Test responsive behavior accessibility and real form destinations |
| Outcome to define | verified visitor journeys |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If page changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep verified visitor journeys connected to the item so the team can later assess whether the action was useful.
Keep the page’s main task visible when adding helpful detail. Supporting information should reduce uncertainty at the decision point. If a section introduces a second unrelated offer, decide whether it belongs on another page.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now