Follow a web request from your browser to a server and back — the complete journey explained simply.
"Help me trace this page load like a web request investigator.
1. Explain the request path from URL to rendered page
2. Tell me which stages are DNS, network, server processing, and browser rendering
3. Based on this symptom, identify the most likely failing stage
4. Tell me what I should inspect in DevTools or logs to confirm it
5. Do not jump to code changes before explaining the likely bottleneck
Symptom: [describe the bug or slowdown]."Prompt FAQ
Follow a web request from your browser to a server and back — the complete journey explained simply. Use it when you need a safer starting point than a blank prompt and you want the agent to stay inside explicit constraints.
No. Treat it as a safe starter. Replace the task, files, constraints, and verification details with your actual context before you run it.
Read the diff, run the checks, and stop after one reviewable step. If you need deeper context, open the lesson that explains the reasoning behind the prompt.
Understand the two halves of every web application using a restaurant analogy that makes it click.
Open prompt pageUnderstand how HTML provides structure and CSS provides style — the visual foundation of every web page.
Open prompt pageWhat JavaScript does, why TypeScript exists, and where you'll see them in every web project you build.
Open prompt page