The Feedback Loop and Other Ways to Run
Goal — Practice the look-feedback-change loop, and understand that different things run in different ways.
By the end — A worked loop of directed improvements, and the ability to tell apart the three ways software runs.
1Run the loop deliberately
Look at your site and name one thing you would improve as a designer. Tell Claude the change in plain terms. Watch the browser update. Judge the result. Repeat.
This loop — look, feedback, change, look — is how real interfaces get good. The seeing is the skill, not the typing.
2Understand: not everything runs the same way
Your site runs through a Node dev server. Other things run differently, and it helps to recognize which is which — because how something runs tells you how to view it and give feedback on it.
3Node dev server
Modern web projects, like yours, run with a dev server you start with a command. It serves on a localhost port with live reload.
4Python-hosted
Some tools are built in Python and run their own small server. A 3D model viewer or a data tool might start with a Python command and open on its own localhost port.
5Static file
The simplest case: a single HTML file with no server at all. You just open the file in a browser. No localhost, no port.
6Know which you are looking at
Ask Claude to place your project among the three, so recognizing the shape becomes automatic.
For this project, which of these three is it, and how would that change if it were a plain HTML file or a Python tool?Recap — You ran the look-feedback-change loop by hand, and learned to tell a Node dev server, a Python-hosted tool, and a static file apart.