Somebody in this room is going to pitch an app, and it will be live on the internet before the session ends.
ScriptHammer is an open source Next.js template that runs real client sites. This talk is about what happens when you hand a template to someone else — and about running the project that maintains it, where most of the work is done by AI agents filing tickets, opening pull requests and getting told no.
We start with a field study. RaisedPaws.com is a pet adoption tracker that shares ScriptHammer's very first commit and went live on its own domain about ten weeks later. We'll look at what it inherited for free and what its team actually had to build.
Then we do it live. Take a suggestion from the room, fork the template, run the rebrand script across 2,872 files, sketch the wireframes and push. GitHub Pages does the rest in about six minutes. You get the repository afterwards.
Along the way, the uncomfortable part: most of the bugs I found last year were not failing tests. They were passing ones that measured nothing — including an account deletion that deleted nothing and reported success. We'll look at how agents make that failure mode more common, and the gate that now catches it.
You will leave knowing whether this template is worth forking, and with a way to tell whether your own green checks mean anything.
: 
