A $15K event-site rebuild, a $900 Upwork win, and a $500 friend rescue. Three different price points, the same OS underneath: scrape, build, ship, reflect. The skills at the end are yours to fork.
The event has been running 14 years. Roughly 1,000 attendees, 100 vendors, three days, sells out the top sponsor tier every year. The website went down the week after the show. That is the gap I was hired to close.
Click to open live
Someone who "dabbles in websites" on the side. Did not even quote a price. Pricing strategy: vibes.
A company that says they build websites for a living. Their own site reads like a scam supplement page you'd land on from a malicious Facebook ad. If your shop window looks like that, your work looks like that.
"I kind of thought you'd have a mock-up but I didn't know it would be in depth. That tells me, okay, they get it."
The bid stack: scrape every fresh job, score the fit, build a working MVP before the proposal goes out, send a 4-minute Loom from the actual product. Every Upwork application I send has a clickable, working site at the URL.
Apify pulls every fresh posting matching ~25 keywords on a 3-hour cron.
Sonnet 4.6 scores each one against my fit profile. Top scorers get a Pharallax structural read enriched in.
Results land in a Google Sheet I open with morning coffee. I spend more time bidding than searching.
If you ship an example site as part of an Upwork bid, the nav routes, the buttons scroll, the form posts to a real endpoint. A static mockup reads as I made this in Canva yesterday. A working MVP reads as this person can ship. There is no in-between.
Tell the client up front in the DM: the stock photos are pulled from Pexels, swap any of them for your real assets. Removes the "this looks fake" objection without pretending you have access to their real library.
A few dollars in Connects to fund the bid. A working MVP in 90 minutes. One signed retainer back.
A friend got burned by an agency. Roughly $15K paid for a fancy front end and a broken back end. She came back with a salvage job. I quoted $500 because the gig was friend pricing and the real currency was the warm intros that follow.
The Comet browser agent ran the recon, the audit, the broken collection URL scan, the Google indexing check. I orchestrated and reviewed. The cost of the audit was an afternoon and a few cents in tokens.
Phase 1 had not even shipped before she was asking about the Substack import, the branded sending domain, three Klaviyo flows, and the seasonal product launch. The $500 gig is a doorway, not the deal.
People in your existing network already trust you. Inner-sphere does not mean lazy. It means the conversion is faster, the lifetime value is higher, and the work compounds through warm intros instead of cold ones.
Pretty homepage. Three of four collection URLs broken. Product pages dropped from page 1 of Google after a re-crawl. Klaviyo on the free tier hitting the 250-contact ceiling. The audit took an hour. The client knew within a day she had paid for surface, not function.
$500 today. Warm intros tomorrow. The friendship pays the delta back, and usually more.
Each of these is a Markdown file Claude reads when I type the slash command. To make any of them yours: replace my prompts with yours, point it at your stack, swap my taste constitution for whatever you want. The "Make it yours" block on each card tells you exactly what to fill in.
/pilot was built from Jack's BLAST framework. Credit where credit is due.
~/.claude/skills/ and run the customize prompt to make them yours.
Spawn a battle-tested project from a brain dump. Scrapes inspo URLs, anchors design seeds to known-good shipped work, scaffolds copy and components, builds, validates with screenshots, and hardens before deploy.
One brief, one shipped site, zero handoffs.
a deployed URL you can text to the client.
Drop your own brief. The skill answers: what do you sell? Who buys it? Three sites you respect? Two you can't stand? Your one-line promise?
Run a binary visual review on any HTML file or URL. Ten pass/fail evaluations plus a 34-principle constitution sweep. Reports a scored table with specific violations and an optional auto-fix.
The receipts on whether your build looks AI-generated.
a one-page audit you can hand to a client or a freelancer.
Paste a screenshot of a site you love and let Claude infer your taste constitution. Or write the rules yourself in plain English.
Spawn a team of researchers in parallel, each attacking your strategic question from a different angle. Findings get synthesized, stress-tested by a critic, and run through a second pass if confidence is too low.
One question, multiple lenses, hardened synthesis.
ranked plays with confidence levels, ready to act on.
Open with your question and three constraints. The lenses adapt to your industry.
Autonomous commit-to-production pipeline. Detects branch strategy, build command, and deploy method automatically. Works in any project with a git repo, or with bsync-only personal tooling.
Deploy without thinking about it.
a deployed URL and a paper trail of what changed.
Wire your deploy command into package.json. The skill reads the script and runs it. No config files to learn.
The counterpart to /ship. Ship flushes code to production. Reflect flushes knowledge to memory. Captures wins, lessons, journal entries, and cross-project patterns at the end of any meaningful session.
Make every session compound the next one.
a session that taught the next one.
Define your own categories. Match memory to how you actually think, not how someone told you to.
If any of this lands, the skills are yours to fork. Pull them, replace my prompts with yours, and run the same loop on your work. I'm always around to compare notes.