A slow screen is not always a performance problem first; it may be gathering information no one needs.
The practical check
Start with the decision the person needs to make, then measure whether the page is doing unnecessary work.
Where AI fits
AI can match each requested datum to the user question and identify expensive work that does not change the decision.
The human decision
People define what the screen must answer and what evidence makes it reliable.
The lesson
Speed improves when a page stops answering questions no one came to ask.
The Build Log companion examines expensive work that does not change the user’s decision.
AI Skills
Use this lesson with the AI assistant you already use
Use this to prepare a reviewable next step without changing any system.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI agent
LESSON: Audit a slow work screen
WHAT TO SHARE:
A de-identified description of the work, current evidence, and the decision you are considering.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Start with the decision the person needs to make, then measure whether the page is doing unnecessary work.
3. Identify the narrowest useful next review step.
RETURN:
A short table with the evidence, uncertainty, human-owned decision, and next action.
BOUNDARY: Do not change records, contact anyone, route work, publish content, or act in an external system. A person must review the evidence and approve every consequential step.
