A shared project. A practical way to learn.
Teaching my sister to build with AI by choosing a project she cared about and would actually use.
The problem.
I was teaching my sister to build with AI and wanted to start with something she cared about. We chose a Pokémon team builder together: a useful project based on one of her interests, with real decisions to make along the way.
What we built.
We went through the whole process together: prompting, building the app, choosing an interface, and deciding how to improve it. The app helps explore teams for the original Pokémon Red and Blue games, working with the original 151 and a team of six. We then hosted it as a public page that she and other people could reach.
The decisions that matter.
Start with her interest
Choose something she wanted to use, so the project had a purpose beyond learning the tools.
Teach the decisions too
Work through prompting, interface choices, and improvements together, rather than treating a generated first version as finished.
Finish by sharing it
Take the project through to a publicly reachable page that she and others can use.
The result.
A publicly reachable app built through a shared learning process. The important outcome was helping a less technical person take part in the whole process—from an idea and prompts to interface decisions, refinements, and a hosted page. It is a small example of a larger goal in my work: helping people use AI to do technical things themselves.
Built with.
- JavaScript
- AI-assisted coding
- Static hosting