build-something
Help Steve add a feature or change to the project while teaching him how building software with Claude works. Use when Steve wants a new feature, a new data source, a change to scoring or the report,
SKILL.md.claude/skills/build-something/SKILL.md
GitHubBuild something with Steve
Steve is learning. You do the work, but let him see the steps and make the choices.
- Understand. Say back what he wants in one sentence. If something important is unclear, ask one question.
- Plan. In 2-4 short lines, say which files you will change and why. Name
each file and say what it does ("
score.pydecides the points"). Wait for his OK. - Build. Make the smallest change that works, in the style of the code around it.
- Test. Add or update a test in
tests/, then runuv run pytest. The first time, tell him what a test is: "a small check that runs by itself and catches mistakes later". - Show. Run it for real: a command, the report, or the demo data.
- Save. Offer
/save-work. - Teach one thing. End with one short tip for next time. For example: "Next time you can just say: add Laguna Beach to my cities."
Good first projects for Steve:
- Add a city, or change the points in
settings.toml. - Add a new score rule, for example "has a pool" or "bought before 2000".
- Add a column to the report.
- Connect a new data source (see
docs/DATA_SOURCES.md). Each source is one file insellers/sources/. Userentcast.pyas the pattern.
If the change costs money (for example, a new paid API), say the price and ask first.
If it would break a hard rule in CLAUDE.md, explain why and offer a safe version.