explaingit

cowboycodr/sitegeist

Analysis updated 2026-05-18

36HTMLAudience · researcherComplexity · 3/5LicenseSetup · easy

TLDR

A visual benchmark comparing 400 websites built by four AI model collections from the same 100 neutral briefs, to see how often their designs converge.

Mindmap

mindmap
  root((Sitegeist))
    What it does
      Compares AI generated websites
      100 neutral briefs
      4 model collections
      Gallery viewer
    Isolation rules
      No shared history
      No cross model visibility
      Strict artifact contract
    Tech stack
      SvelteKit
      Cloudflare Workers
      Node and pnpm
    Use cases
      Compare model design habits
      Audit duplicate output
      Add a new model collection
    Limits
      Narrow task only
      Exact match audits only

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Browse and compare how different AI models design a website from the same brief.

USE CASE 2

Run duplicate and consistency audits across a model's generated websites.

USE CASE 3

Study recurring visual patterns across many AI generated sites.

USE CASE 4

Add a new model or CLI tool to the benchmark using the provided workflow.

What is it built with?

SvelteKitCloudflare WorkersNode.jspnpmHTML

How does it compare?

cowboycodr/sitegeistaaaa-zhen/siri-glslicydotdev/pocket
Stars363636
LanguageHTMLHTMLHTML
Setup difficultyeasyeasyeasy
Complexity3/52/51/5
Audienceresearcherdesignerdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Just needs Node.js and pnpm to run the gallery locally.

MIT License: free to use, modify, and distribute, including commercially, as long as you keep the copyright notice.

In plain English

Sitegeist is a visual benchmark that asks a simple question: when leading coding agents get the same set of website briefs, how often do they land on the same design choices? The project contains 100 neutral website briefs and 400 finished, self-contained websites, generated by four different model collections named 5.6 Sol, Opus 4.8, Grok 4.5, and Fable 5. A gallery lets you browse every result, switch between models, and compare up to three generations side by side. What sets this benchmark apart is how each site is produced. Every generation runs in a fresh, isolated workspace. The model doing the work only sees a neutral work order, one private brief, and the rules for what counts as a valid submission. It cannot see the Sitegeist gallery, the project's git history, another model's result, earlier sites from its own batch, or any screenshots or feedback from previous attempts. Accepted sites must include their original source code, build to a plain static site with no external dependencies, and come with a self-contained poster image for the gallery. Submissions get rejected if they load resources from the internet, depend on a live network connection while running, use symbolic links, are malformed, throw errors in the browser console, or overflow the screen on mobile. The goal is not to crown a winner on taste, but to preserve the outputs and the strict boundaries under which they were made, so anyone can inspect visual quality, repeated patterns, and exact copies for themselves. To run the gallery on your own machine you need Node.js and pnpm, then install dependencies and start the dev server, after which it opens at a local address. The gallery itself is built with SvelteKit and deployed on Cloudflare Workers. The project also ships deterministic audit scripts that check for exact duplicate code or builds, duplication across different models, how much content each collection contains, and whether a finished collection is internally consistent. The README is upfront about the benchmark's limits. It measures one narrow website generation task, not overall model capability. Its duplicate checks catch identical source or output, not looser stylistic similarity. The gallery poster images are just representative screenshots, not the actual evidence, since the real sites stay viewable in full screen. It is released under the MIT License.

Copy-paste prompts

Prompt 1
Help me set up Sitegeist locally with Node.js and pnpm and run the gallery.
Prompt 2
Explain how Sitegeist isolates each model's generation attempt so results are not copied.
Prompt 3
Walk me through adding a new model collection to Sitegeist using the add-model skill.
Prompt 4
Show me how to run the cross-model duplicate audit script on two site collections.
Prompt 5
Summarize what Sitegeist's methodology can and cannot tell us about model design capability.

Frequently asked questions

What is sitegeist?

A visual benchmark comparing 400 websites built by four AI model collections from the same 100 neutral briefs, to see how often their designs converge.

What language is sitegeist written in?

Mainly HTML. The stack also includes SvelteKit, Cloudflare Workers, Node.js.

What license does sitegeist use?

MIT License: free to use, modify, and distribute, including commercially, as long as you keep the copyright notice.

How hard is sitegeist to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is sitegeist for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.