# Editorial landing page for a hive mind > A Swiss-modernist landing page on ivory paper for CHORUS, a made-up collective where you keep your identity but share everyone else's mind, with a network of generated portraits. Codex named and built it from one short prompt and a one-line follow-up. - Kind: Website - Page: https://meetreference.com/v/editorial-landing-page-hive-mind/ - Ready-to-use agent handoff: https://meetreference.com/v/editorial-landing-page-hive-mind/agent.txt - Exact prompt as plain text: https://meetreference.com/v/editorial-landing-page-hive-mind/prompt.txt - Authorship: Not stated - Made with: Codex - Model: not stated - Built with: HTML and CSS, Plain JavaScript - Services: OpenAI image generation - Skills or plugins: frontend-design, Uncodixify, frontend-from-generated-image, Codex imagegen skill - Style: Landing pages; editorial, swiss modernist, ivory paper, vermilion, condensed type, portrait collage, network diagram - Shared by Adam Holter in GitHub, Jul 9, 2026: https://github.com/adamholter/hive-mind-landing-page - Prompt fidelity: Verbatim. This is the complete prompt exactly as the creator published it. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. Requirements reported by the source: The frontend-design, Uncodixify, and frontend-from-generated-image skills (the last is in the repo); Image generation the agent can call, such as Codex's imagegen skill. ## Recreating this website These are the creator's published instructions, unedited. To adapt it: Rewrite the perks ("one day a week from 9 to 5", "pay 5% on income") for your own made-up organization, and keep "You come up with the name." so the agent names and brands it. ## Prompts ### 1. Prompt ```text Generate a landing page as a marketing page for joining our Hive Mind. The unique perks of our Hive Mind is that you still get your individual identity. You just pretty much have access to everyone else's mind. And you do get some objectives, but you only work for the Hive Mind one day a week from 9 to 5. You also need to pay 5% on income. In exchange, you get access to a wide network of professionals and opportunities. You come up with the name. ``` ### 2. Follow-up ```text A quick interruption: don't delegate this to Antigravity or anything. That instruction doesn't apply for this test. ``` ## What it looks like Written by Reference from the recording frames, not by the creator. Three stills: the CHORUS hero on desktop, the same hero on a phone, and the agent's generated full-page mockup. A ring of black-and-white portraits linked by red lines fills the right side. - Color: Ivory paper with black type; vermilion for the button, the network's hub, and the stats; thin blue technical marks. - Type: Tall condensed sans in all caps for the wordmark and headline ("KEEP YOUR NAME. GAIN EVERYONE ELSE'S MIND."), a serif subhead, and tiny uppercase annotations. - Framing: The headline is stacked on the left and the portraits sit in a circular network diagram on the right. On the phone the headline stacks over a faded network. The mockup adds a stats band below the hero: 1 DAY / WEEK, 9–5, 5% OF INCOME. - Structure: Desktop first screen, phone first screen, then the generated reference mockup the build started from. Storyboard of the images: https://meetreference.com/media/editorial-landing-page-hive-mind/storyboard.webp - Image 1: https://meetreference.com/media/editorial-landing-page-hive-mind/f1.webp - Image 2: https://meetreference.com/media/editorial-landing-page-hive-mind/f2.webp - Image 3: https://meetreference.com/media/editorial-landing-page-hive-mind/f3.webp ## How it was made, per the creator - Notes: The first turn was interrupted while Codex got ready to hand the work to Antigravity; the follow-up told it not to. Codex then generated a full-page UI mockup and the portrait-network hero art with image generation (it wrote both image prompts itself; they're in PROMPTS.md), built a static site with no dependencies, and checked it in headless Chromium at desktop and phone sizes. The README credits the skills for much of the look. The model isn't named. There's no hosted copy, so this entry shows the repo's desktop and phone screenshots and the generated mockup. > This landing page was built by Codex from one short prompt. > (Adam Holter) ## Links - Watch: https://github.com/adamholter/hive-mind-landing-page - Original post: https://github.com/adamholter/hive-mind-landing-page - Prompts, including the agent's image prompts: https://github.com/adamholter/hive-mind-landing-page/blob/main/PROMPTS.md - Build trace: https://github.com/adamholter/hive-mind-landing-page/blob/main/TRACE.md