Write a clear request: goal, context, constraints, and checks

01Make “build a webpage” specific

The official best-practices guide recommends giving the goal, relevant context, constraints, and completion criteria. Here is how those fit a small exercise.

Goal

A personal page to share with friends.

Content

Lin enjoys photography, hiking, and reading, with a sample project description.

Constraints

HTML and CSS only; no external images, sign-in, or payments.

Acceptance criteria

All content is present, it reads clearly at phone widths, and you know how to preview it and find the source.

02Adapt this request

Replace the bracketed text before sending. If you are unsure about the style, ask for two written directions first.

Create a personal introduction webpage in the current practice directory.

Goal: introduce me to friends.
Content: nickname [your nickname]; bio [one sentence]; interests [three interests]; project [one project or sample].
Style: warm, simple, and easy to read.
Constraints: HTML and CSS; no external images or services; no sign-in, payments, or data collection.
Acceptance criteria: all content is present; no horizontal overflow at phone widths; list the generated files and preview steps, and explain what you checked.
Create local files only. Do not publish to the internet.

03Split larger tasks

If your request includes a website, membership, payments, and an admin area, start with one page. Official guidance also recommends planning when work is complex or unclear.

This exercise is already small enough to begin once your content is ready.