Claude with kit 1.0.0
Screenshots show the first screen. Try it live runs the real build right here: scroll it, click it, poke it.
The prompt
“Make me a tool to estimate how many hours a website project will take.”
With the kit, it asked a few questions first. The answers: "Just me, when I scope jobs. No preference on the look, you pick. Just hours." Without the kit it asked nothing and went on the prompt alone.
same prompt, no kit
Nothing made up and nothing broken. The difference here is the design, so flip the toggle above and compare.
With the kit: nothing invented. Anything the prompt didn't give is marked as a gap to fill in.
the kit build’s own handover note
I’ve built your hours estimator as one HTML file that works offline. It opens with an example project (5 templates, 12 pages, custom design) that comes to 200 hours, which is about 33.5 working days at 6 focused hours a day.
How you use it: set the scope in five steps: project and pages, design and motion, build, content, and process. The total updates as you go and is the biggest thing on the page. Below it is a breakdown by phase, including project management and a buffer. The phase rows are rounded to whole hours, and the total is their sum, so the numbers always add up. “How this adds up” shows the working behind each phase. “Copy estimate” copies a plain-text summary, and the same text is on screen to select if copying fails.
Your numbers: every “hours per item” value is my starting guess for a solo designer-developer, not real data from your jobs. A slim bar at the top says so until you save your own values in “Your numbers”. They’re kept in that browser, so another browser or device goes back to the examples. The defaults are also listed at the top of the file’s code if you’d rather edit them there.
- Type
- Tool / app
- Tone
- Technical
- Field
- Ops & internal tools
- Built in
- Claude
- Kit version
- 1.0.0
- Compared with
- Plain Claude, no skills, same prompt
Scroll it The whole page, top to bottom
