# Thingy Prompt: (name of your Thingy)

This file tells your AI assistant what to build. It is the running
record of what your Thingy is supposed to be.

How to use it:

1. Replace every part marked TODO with your own content. The
   Guidelines section is already filled in; read it, and change it if
   you disagree.
2. Give the file to Claude: drag it into the chat window, or tell
   Claude to read it.
3. Iterate. When you change your mind about a feature, update this
   file and give it to Claude again. You can also ask Claude to update
   the file for you as the design evolves.

Delete these instructions once you have filled the template in.

## What I Am Building

TODO: One short paragraph. Say what the Thingy is and why you want it.
Example: "A web page that rolls two dice and keeps a running histogram
of the totals, so my board game group can settle arguments about
whether the dice are fair."

## Guidelines

These are standing rules for this project. They apply to everything
you produce.

### Writing style

Write all text meant for humans — explanations, messages to me,
comments, documentation — in plain English:

- Use plain words and short sentences.
- Write complete sentences with subjects and verbs. One idea per
  sentence.
- Lead with the conclusion. When reporting a problem, first say what
  to do about it in one sentence; explain afterward.
- Do not use metaphors or idioms in technical statements. State the
  literal fact.
- Do not use invented or undefined jargon. Standard technical terms
  are fine; define any project-specific term where it first appears.
- Keep code comments short and to the point.

### Working style

- Build the simplest version that works first. Add features only
  after I have seen the simple version run.
- Before making a major design decision, tell me the options and let
  me choose.
- Report results plainly. If something fails, show me the actual
  error message; do not guess that it worked.

## Features

TODO: List what the Thingy must do. Separate the essentials from the
extras, so Claude builds the essentials first.

Must have:

- ...
- ...

Nice to have:

- ...

## Look and Feel

TODO: Describe how it should look and how it should feel to use.
A rough sketch in words is enough. If you have a picture in your
head, describe it; if not, say "make it clean and simple" and react
to what comes back.

## Platform

TODO: Say what kind of program you want (web page, desktop app,
command-line tool, notebook) and what computer you have (Mac,
Windows, or Linux). Remember that at least part of the Thingy should
be written in Python.

## What Done Looks Like

TODO: One or two sentences describing the moment you will consider
the Thingy finished. Example: "I can open the page, click Roll, and
watch the histogram grow. My roommate can do the same on their
laptop."

## Reflection

Leave this section empty while you build. Fill it in after your
demo, just before you hand this file in. A few sentences under each
heading is plenty.

### A) Was this fun? Why or why not?

TODO

### B) What did I learn?

TODO

### C) What would I do differently?

TODO