PHACT FIRST-PROTOTYPE PROMPT

Replace every bracketed item with your instructional decisions. Use general observations, not identifying student details.

P / Purpose
[What should students understand or be able to do? Name one barrier and the evidence that would show progress.]

H / Human anchor
[What does the teacher know about this class? What must students think through themselves? Make those responsibilities explicit.]

A / Audience
[Consider prior knowledge, language, reading, communication, access needs, and available devices. Build supports that everyone can use.]

C / Components
[Choose the smallest set of controls, representations, and interactions that supports the goal.]

T / Tone & constraints
[Specify clear language, accessible presentation, expected behavior, and limits on data and answers.]

BUILD REQUEST
Build a small static HTML/CSS/JavaScript prototype for the brief above. Keep the teacher in charge of instructional decisions and preserve opportunities for students to predict and explain. Use no accounts, identifying student data, persistent storage, analytics, external services, or live AI calls. Include clearly labeled controls, keyboard operation, visible focus, readable contrast, and a reset button. Changing inputs must clear any result that is no longer valid. Use only the teacher-supplied facts and examples; flag missing information rather than inventing evidence. Explain the rules, assumptions, limitations, and steps for teacher testing. Do not claim that the prototype has been verified or approved.

TEACHER-SUPPLIED EXAMPLES
[Provide verified examples and expected results, valid input ranges, and a new task to check transfer.]

After reviewing the code and trying the prototype, revise the brief and request one focused change at a time.