Prompt Your Site — Architecture & Stack | Analytical Solutions

Live in production

Prompt Your Site

under the hood.

This is the architecture page, not the sales page. Prompt Your Site is a Next.js website product with a Claude Code onboarding wizard baked in — and the site you're reading was built with it. Below is the stack, laid out so a technical reviewer can audit it before trusting a word of it.

At a glance

API route handlers in the template repo

~30

Claude skills shipped inside every purchase

checkout & booking providers, one commerce layer

brand-trained agents the buyer keeps

What it is

A website you own, built by an agentic interview.

A non-technical owner answers a guided /wizard-setup interview and gets a fully branded Next.js site — blog, store, bookings, payments — built and deployed, with the code theirs to keep. One-time pricing, $1,000 (DIY) or $2,000 (done-for-you), and no monthly platform rent.

For us, it's one of four named products in the portfolio — its own brand, its own P&L, built on the same reusable agentic method we run across every platform we operate. For the owner, it's the fastest honest path to a site they control outright instead of renting.

The stack

The resume, in full.

Every row below traces to the shipped repo or the product dossier. Major framework versions where they matter; no marketing rounding.

Front end

Next.js 15 (App Router) with React 19, TypeScript, and Tailwind CSS 4. shadcn/ui on Radix primitives; MDX-driven content. Rendered as a static / server-component marketing site.

Middleware & services

Seven Next.js API route handlers — checkout, Stripe webhooks, contact, feedback, design-selection, gallery revalidation, and a short-link redirect. A root middleware returns 410 Gone for URLs retired during an SEO migration, and a single daily cron revalidates the gallery. Stripe webhook fan-out with each side idempotent.

Back end & data

The template site is content-driven — MDX and config, no database in the repo. The buyer portal is a separate Next.js 16 application on serverless Postgres — raw SQL over a single idempotent schema, no ORM, money kept as integer cents — with zero shared code or database between the two.

API paradigms

REST route handlers plus idempotent Stripe webhooks. Delivery is version-pinned — each purchase resolves to a dated, tagged build rather than a moving target.

Authentication

The buyer portal signs in with Auth.js v5 — OAuth via Google and Microsoft 365 (Microsoft Entra ID). The template repo itself ships no auth dependency.

Payments & commerce

Stripe embedded checkout with Stripe Tax, over a provider-agnostic commerce layer spanning 7 providers — Stripe, Square, Gumroad, Lemon Squeezy, Cal.com, Calendly, and Microsoft Bookings. Each purchase mints a license pinned to a dated build.

AI & agentic layer

A Claude Code onboarding wizard conducts /wizard-setup; ~30 skills and 5 brand-trained agents ship with every purchase and the buyer keeps them, alongside SEO and site-audit crawlers. Separate verifier agents certify "done." The buyer brings their own Claude subscription.

Infrastructure & delivery

Vercel hosting, Vercel Blob storage, and Vercel Analytics; Resend for email; Turnstile for spam protection. Every buyer gets a reproducible build cut from a dated tag.

What a technical reviewer will notice

Three things that separate this from a template dump.

Two decoupled apps

The marketing template and the buyer portal share zero code and zero database, and the Stripe webhook fan-out is idempotent on both sides. State boundaries are drawn, not hand-waved.

Version-pinned delivery

A purchase resolves to a license, the license to a dated tag, and the tag to a reproducible build. No "latest main" surprises — the buyer gets the exact code they paid for.

Dogfooded

The site selling the product was built by the product. If the method didn't hold up in production, you'd be reading a broken page instead of this one.

Verify it yourself

Don't take our word for any of it.

The product is live and public. Visit promptyoursite.com, run the onboarding yourself, and inspect the running site — this page included, since it was built the same way. Everything above is meant to be checked, not admired.

Start a conversation

Want a platform built and delivered this way?

We built, own, and operate this one — then build yours the same disciplined way and hand you the code. Tell us what you're trying to ship.