Build one useful tool.

Vibe coding means describing a digital tool in plain language and using an AI coding assistant to help create it. Start with a real teaching problem, make a small prototype, and use your judgment to test and improve it.

Choose a useful first project

Look for a recurring barrier: a representation students struggle to interpret, confusing instructions, or a way to organize evidence without supplying the reasoning. A first version should do one job and work without connecting to district systems.

For teacher-facing work, an evidence organizer or resource hub can also be a useful starting point. Avoid identifiable student information and leave interpretation and professional decisions with the educator.

Plan with PHACT

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, test, and improve

Write your brief and supply verified content and examples.
Ask your school-approved AI coding tool for the smallest useful prototype.
Test realistic scenarios using fictional or non-identifying information.
Notice what is confusing, inaccurate, inaccessible, or unnecessary.
Request one focused improvement, then check both the fix and the original behavior.
Save versions so you can return to a working copy.

Follow-up prompts you can adapt

“Make the directions clearer without removing important information.”
“Add a reset button that restores every field and result to its starting state.”
“Make every interaction usable with a keyboard and visible focus.”
“Add one optional language support while preserving the learning goal.”
“Do not add features. Fix only the issue I describe.”
“Explain the changes and how I can test them in plain language.”

Keep the human responsibilities visible

The teacher selects content, checks accuracy, interprets evidence, and chooses next steps. Students predict, reason, and explain. An organizer may arrange ideas; it should not silently decide whether reasoning is adequate.

Separate building from classroom use

The teacher can build with AI and share a finished static resource. Students do not need to prompt AI. For a first build, use no student accounts, identifying information, stored responses, or live AI calls.

Inspect what the tool actually does, including any external requests. Check school technology, privacy, accessibility, and procurement requirements before broader use.

Try it in a lesson, then examine the learning

Ask students to explain or apply the idea in a new task. Use that evidence to decide what to keep, remove, or revise. More features are useful only when they support the learning.

Write your PHACT brief · Use the testing checklist

Adapted from the supplied Human-Oriented Vibe Coding Educator Guide. This web edition uses Purpose, Human anchor, Audience, Components, Tone & constraints consistently with the PHACT framework and grade-band idea bank.