Rabbithole

LLM-powered dynamic website generator — documentation

Example: ACAPA

American Competitive Apple Picking Association — a fictional early-2000s sports governing body, generated entirely by Rabbithole

Live site: acapa.isarabbithole.com  |  Source / seed: see seed prompt below

1. Overview

ACAPA (American Competitive Apple Picking Association) is one of the flagship demonstration sites built with Rabbithole. The premise: a fictional governing body for competitive apple picking as a recognized sport, with the look and feel of an official association website circa 2001–2004 — complete with garish colors, Comic Sans, nested tables, hit counters, and a deep bureaucratic lore.

The goal was twofold: (1) stress-test Rabbithole's ability to maintain coherent fictional lore across many independently-generated pages, and (2) demonstrate that the seed prompt's design instructions can propagate consistently even to deeply-nested subpages the generator has never "seen" before.

The site ultimately grew to over 40 generated pages spanning athlete profiles, rulebook sections, event archives, a hall of fame, regional chapter listings, and a disciplinary tribunal case log — all cohering around the same fictional universe.

2. Design Goals

The aesthetic was deliberately retro-ugly. The brief called for:

Every page prompt included the full color and layout specification so that subpages generated months later (from a cold cache) would still render with the correct look. See the seed prompt for the exact wording used.

3. The Seed Prompt

The following is the seed prompt supplied to Rabbithole for the ACAPA homepage (acapa.isarabbithole.com/):

4. Lore Consistency Across Pages

The central challenge of a site like ACAPA is coherence: does the Hall of Fame page mention the same champion as the Rankings page? Does the Rulebook cite the correct amendment number for the Branson Incident? Does Commissioner Pottsworth's name stay spelled consistently (it's easy for a model to produce "Potsworth" or "Pottworth" if the name isn't in the prompt)?

Rabbithole addresses this through prompt forwarding: every link a page generates includes a prompt that must encode the full lore context. The ACAPA design used a dedicated "lore block" — a fixed chunk of text describing the universe — that was copy-pasted verbatim into every subpage prompt. This produced excellent consistency: across 40+ pages, the character names, amendment references, and headquarters address were consistent in approximately 94% of generated pages.

The ~6% inconsistency cases fell into two categories:

1. Name drift: Commissioner Pottsworth's middle initial occasionally dropped ("Gerald Pottsworth" instead of "Gerald T. Pottsworth III"). This was fixed in a second pass by adding "always use the full name including 'III'" to the lore block.
2. Year drift: Darlene Kowalczyk's championship years were occasionally wrong (e.g., 1999, 2003 instead of 1999, 2002) when a prompt was summarized rather than copied verbatim.

Lesson: For fictional lore with specific numbers, names, and dates, verbatim copying of the lore block is more reliable than paraphrasing it. See ACAPA prompt engineering notes for a deeper analysis.

5. Notable Characters & Lore

6. Pages Generated

Below is a representative selection of the pages Rabbithole generated for the ACAPA site, along with notes on how well each page honored the design and lore constraints.

7. What Worked

7.1 The retro design propagated exceptionally well

Of all the design choices, the "garish early-2000s aesthetic" was the most reliably reproduced. Comic Sans, the yellow background (#ffff99), and the table-based layout appeared consistently across virtually every page. This is likely because these are strong, memorable, and unambiguous instructions — there's no interpretation needed.

7.2 Bureaucratic tone emerged naturally

The prompt asked for "hyper-formal bureaucratic prose" and the model delivered. The Rulebook page generated section numbering such as "Article IV, Section 3, Paragraph (c)(ii)" without being asked for specific numbering schemes. The Tribunal page produced formal case identifiers (e.g., "ACAPA Disciplinary Case No. 2019-MO-0047") entirely on its own.

7.3 Character elaboration beyond the prompt

When the model is given a named character with a few facts, it fills in plausible gaps consistently. Darlene Kowalczyk's Traverse City, MI birthplace, Pottsworth's 1993 3rd-place finish, and Huffington's eventual reinstatement in 2022 were all invented by the model — and then propagated correctly when they appeared in later page prompts that referenced the earlier page's output.

7.4 The rival organization (NAAPA) created organic tension

Introducing a named rival with a brief description ("considered illegitimate") was sufficient for the model to construct an entire implied backstory. Multiple pages referenced NAAPA without prompting, in ways that felt narratively consistent.

8. What Didn't Work

8.1 Deep subpage design drift

Pages more than 2–3 link-hops from the homepage tended to drift toward cleaner, more modern design. By the time a page like /chapters/new-england/history.html was generated from a brief prompt summary, the full design spec had been partially lost. The fix is to always include the complete design spec in every prompt, not just a summary like "same style as the rest of the site."

8.2 Real-world fact bleeding

The Cortland apple history page mixed actual historical facts about the Cortland apple (a real New York variety) with fictional ACAPA lore. This produced an interesting but confusing page where it was unclear what was "real" and what was fictional. For purely fictional sites, avoid naming real-world entities that the model has strong knowledge of.

8.3 Link graph gaps

Some generated pages linked to URLs that were never requested (e.g., the model invented /merchandise.html on its own without it being in the original sitemap). These stubs are generated on-demand when first visited, but they may lack lore context because no explicit prompt was written for them. Always review generated link mappings and add context to unexpected URLs before they go live.

8.4 The hit counter

The seed prompt asked for a "fake hit counter showing visits in the 40,000–200,000 range." The model reliably generated a static number, but it chose numbers like exactly 100,000 or 150,000 — suspiciously round. Real early-2000s hit counters had irregular numbers. A better prompt would specify something like "a specific irregular number such as 84,217."

9. Lessons Learned

The ACAPA experiment produced several generalizable guidelines for building coherent fictional sites with Rabbithole:

1. Every prompt is a complete brief. Never rely on the generator "knowing" anything about the rest of the site. Paste the full design spec and lore block into every single prompt, verbatim.
2. Named specifics anchor lore. Vague instructions ("there is a famous champion") drift; specific ones ("Darlene Kowalczyk, 4x champion, 1999/2002/2006/2011") stay stable. Use names, years, amendment numbers, and addresses wherever possible.
3. Short prompts produce short memory. If a prompt for a subpage is only 2–3 sentences, the generator will invent most of the page's content and may contradict the main site's lore. Longer prompts with the full lore block produce much more faithful results.
4. Rivalries and conflicts generate organic content. A named rival or a past controversy gives the model something to react to. The Branson Incident and NAAPA rivalry produced the most entertaining pages on the site with minimal additional prompting.
5. Design constraints should be machine-readable, not aesthetic. "Ugly retro design" is less reliable than "background-color: #ffff99; font-family: Comic Sans MS." Hex codes and explicit property names propagate better than adjectives.
6. Review the link graph early. Unexpected URLs generated by the model (like /merchandise.html) will be visited by real users. Add explicit lore context to those stubs before they accumulate traffic.

For more on prompt strategy for fictional sites, see the ACAPA Prompt Engineering Deep Dive and the general Web Tools & Research documentation.

See also: All Examples  ·  Example: Procedural News Site  ·  Example: Fictional Encyclopedia  ·  Rabbithole Architecture  ·  Configuration Reference