Anticode Open builder

Product

How Anticode builds a site

You write one sentence and answer three quick questions. Five agents, each with one job, turn that into a page that follows a single design system, passes a design lint and a security scan, and exports as code you own.

Updated · By the Anticode team

The build, step by step

Every build follows the same order, and you can watch it happen in the build log. Nothing reaches the preview until the last agent has signed it off.

  1. You describe it. One sentence, such as “A booking site for my barbershop called Reid’s Barbers”. Then three taps: the kind of site (landing page, online store, booking app, dashboard or portfolio), a design direction, and the must-haves you need, like a booking calendar or a contact form.
  2. Architect turns the sentence into a spec: the pages, the sections, the data each section needs and the must-haves you ticked.
  3. Designer picks one of seven design systems and holds the build to its type, colour and spacing. One font family per site, one action colour, radius assigned by role.
  4. Builder writes plain, readable HTML and CSS. The page it ships contains no scripts at all.
  5. Critic runs a design lint on the finished page and flags generic AI tells: the purple gradient, emoji used as icons, stock phrases and six more. The design engine is written to avoid them in the first place, so the lint is a check, not a clean-up.
  6. Sentinel scans the exact HTML that is about to open: the Content-Security-Policy, forms, links, images and anything that looks like a secret. You see the result in the build report, and if a check fails, the page can't be published until it's fixed.

Seven design systems, one font each

Most AI builders start every site from the same defaults and let you restyle afterwards. Anticode starts from a complete system instead, so the type scale, palette and shapes agree with each other from the first section.

The design directions the Designer agent can choose from
DirectionTypefaceCharacterSuits
EditorialNewsreaderInk on paperBarbershops, restaurants, coffee roasters, writers
TechnicalIBM Plex SansAmber on graphiteSoftware products, clinics, developer tools
LuxuryCormorant GaramondChampagne on blackCeramics, photographers, boutiques
PlayfulFredokaCobalt and sunflowerStudios, bakeries, family businesses
BrutalistArchivoBlack rules on concreteStudios, galleries, anything that should feel loud
OrganicFrauncesSage and clay, soft serifCeramics, wellness, florists, food
SwissInter TightOne red on a strict gridDesign studios, architects, conferences, consultancies

You can switch direction at any time, and you can tune individual colour tokens. The checks still run on whatever you end up with.

The Critic's design lint

The Critic runs nine checks on every build, each aimed at a habit that makes AI-generated sites look alike. They are explained one by one, with what to do instead, in why so many AI websites look the same.

  • No purple-to-blue gradient
  • No emoji used as icons
  • No stock AI phrases such as “revolutionize” or “unlock your potential”
  • One font family
  • No default ease timing curves
  • A hero sized to its content, not forced to the full screen height
  • Cards that don't all lift on hover
  • Shape that follows role, with radius assigned per component type
  • Body text of at least 16px

Sentinel's security checks

Sentinel runs twelve checks on the HTML that ships. The same rules that matter once a page is public run again on the server when you publish, so a modified browser can't skip them. Each check is explained in the AI website security checklist.

What you can take with you

One HTML file
The page as a single, self-contained HTML file with its CSS inline. Host it anywhere that serves static files.
A Next.js app
A standard Next.js (App Router) project with TypeScript, Postgres through Prisma and Zod. Bookings, contact messages, newsletter sign-ups and email sign-in links have server routes; owners and admins get an admin area with two-factor sign-in and role-based access. No Anticode runtime is included.
The project file
Every project is one documented JSON file, anticode.json, with a public JSON Schema. Coding agents and the Anticode CLI can read and edit it, and the open builder picks up the change.

Preview builds and model-written builds

The builder on the homepage lays out preview builds with Anticode's design engine right in your browser, with no account and nothing to install. Signing in adds builds written by a frontier model, which follow the same design systems and pass through the same Critic and Sentinel checks.