CrownCode AI

A website builder under Higgins Digital that guides a business through a structured intake, generates a complete website package with Claude, and supports targeted revisions before deployment.

Live public site

My role

Designed and built the intake wizard, generation and revision flows, the package presentation, and the server-side Claude integration.

A crown linked to a sequence of generated website screens.

The problem

People who need a website often struggle to turn their business, content, and brand preferences into a brief a developer, or a model, can act on. A single open-ended prompt produces something fast, but rarely something they can review and refine.

My contribution

I designed and built the full flow: the landing page, the six-step intake wizard, the Claude generation and revision engine in server-side API routes, and the results experience with exports and a deployment guide.

What I built

CrownCode collects structured requirements first (Business Basics, Brand Direction, Website Structure, Content Details, Build Preferences, and Final Review), with local auto-save so a refresh never loses answers. Each generation returns a structured package rather than raw text, and a revision step changes only what the user asks for.

  • A package with project name, brand summary, strategy, sitemap, design system, page copy, file tree, code files, README, and a deployment guide.
  • Collapsible result sections, per-file copy buttons, and a full-project JSON export.
  • A plain-English GitHub and Vercel deployment guide for non-technical users.
  • A guided revision workflow for copy, layout, branding, and deployment readiness.

How it works

Validated input reaches Claude only through server routes, and revisions are scoped to the requested change.

  1. Structured intake wizard
  2. Validated server API route
  3. Anthropic Claude generation
  4. Structured website package
  5. Scoped revision → export and deploy guide
CrownCode intake wizard on step one, Business Basics, with fields for business name, industry, and target customer.
Step one of the six-step intake wizard. Answers auto-save locally so a refresh never loses them.

Key decisions

Collect structure before generating.

A guided intake produces a far more reviewable result than an unconstrained first prompt.

Keep credentials on the server.

The Claude integration runs in server-side routes with validated request bodies, length limits, and server-only error logging.

Preserve what the user didn't ask to change.

Revisions target the requested change and keep the rest of the package stable.

Outcomes & evidence

CrownCode is live at crowncode.higginsd.com and demonstrates a guided path from business information to a website draft with supporting strategy, files, and deployment guidance.

Scope & limits

Generated sites still need human review before production. CrownCode does not claim that every generated site is automatically secure, accessible, or ready to ship.

What I learned

Structured requirements and controlled revision make generated work much easier to review.

Built with

Next.jsTypeScriptTailwind CSSAnthropic Claude APIlucide-reactVercel

More projects

All projects