Read CLAUDE.md first.

Build the AI Friday homepage as a shotgun house.

The page is one long vertical scroll, and every section is a room, in the order you'd actually walk through one from the street:

• Front room: the invitation. Next meetup date, place, RSVP. This is the first thing you see through the front door.
• Second room: what AI Friday is.
• Third room: what people are building.
• Fourth room: what you'll walk away with.
• Kitchen, at the very back: the Slack. That's where the real conversation happens, and it's the last room in the house.
• Back step: footer.

Doorways are the section transitions. Scrolling should feel like walking through the house, not paging through a website. Go literal: illustrate the architecture, the thresholds, the changing light as you move deeper in. This is the bold version and I want to see it. But the structure must still work if the illustration were removed: the narrow single column, the sequence of rooms, and the sense of arriving at the kitchen should survive on their own.

Seed-string decisions: exact palette, type pairing, how the light changes room to room, wall texture, the rhythm of the doorways. Imagery to generate: doorframes, floorboards, wall texture, the view out the back door. Consider layering images with subtle depth or parallax so the rooms feel physical.

Break the rules of what a homepage looks like, but it still has to work as a homepage.

Follow this procedure: 1. Generate a long, random alphanumeric string using a shell script. Use it as inspiration for every decision the brief doesn't already make. Look beyond the surface for subpatterns, special numbers, anything that inspires you. Don't reveal the string in the design. 2. Write DESIGN-NOTE.md defining the creative direction before writing any code. 3. Generate the imagery with the Codex CLI as described in CLAUDE.md. Do not fake textures, light, or surfaces with CSS gradients, box shadows, or filters. 4. Build it. Verify frame-by-frame in the browser at mobile and desktop widths. 5. Screenshot, write NOTES.md, and stop.

The first three seconds should say: you're invited, this is happening, it's here.

Read CLAUDE.md first.

Build the AI Friday homepage as a front porch on a warm, lively evening.

Not a party. A porch where a few people are already sitting, someone's laughing, there's music coming from somewhere down the block, and there's an empty chair waiting for you. Golden hour tipping into blue hour. The whole page is that scene, and the interface is hospitality: the RSVP is "pull up a chair," the Slack is "come by anytime," the meetup is something you're invited to, not something you register for.

Local detail to build around: haint blue, the pale blue that porch ceilings are painted across the city. Make it the primary color. It's distinctive and quiet and locals will recognize it without a single cliché. Pair it with the warm colors of evening light, wood, and whatever is in people's glasses.

The imagery must be photographic or painterly. No vector illustration, no flat icons. The porch should feel like a real place with real light. Lively means people, movement, warmth. It does not mean a crowd, beads, or a bar.

Generate the hero image first and let it dictate the palette and composition of everything below it. Generate supporting imagery for the other sections only where it adds warmth; empty space is fine on a porch. The page needs a real system beneath the scene: consistent type, spacing, and components that carry the same warmth without the photo doing all the work.

Seed-string decisions: secondary palette, type pairing, exact time of evening, style of the house, what's on the table, how the sections are arranged on or around the porch.

Follow this procedure: 1. Generate a long, random alphanumeric string using a shell script. Use it as inspiration for every decision the brief doesn't already make. Look beyond the surface for subpatterns, special numbers, anything that inspires you. Don't reveal the string in the design. 2. Write DESIGN-NOTE.md defining the creative direction before writing any code. 3. Generate the imagery with the Codex CLI as described in CLAUDE.md. Do not fake textures, light, or surfaces with CSS gradients, box shadows, or filters. 4. Build it. Verify frame-by-frame in the browser at mobile and desktop widths. 5. Screenshot, write NOTES.md, and stop.

The first three seconds should say: you're invited, this is happening, it's here.

Read CLAUDE.md first.

Build the AI Friday homepage using hand-painted shop signage as the type system.

The vernacular is New Orleans corner store, po-boy shop, laundromat, neighborhood grocery: enamel color on wood or brick, lettering done by a sign painter, a drop shadow that was painted not rendered, "COLD DRINKS" and "OPEN" and hand-lettered price boards. It is NOT Western saloon, NOT rustic farmhouse, NOT hipster café. If it starts to feel like a coffee shop chalkboard, it's wrong.

Signage is for headlines only. One big painted sign is the hero: the next meetup, painted like it's hanging over a shop door. Each section header is a smaller painted sign. The month's schedule reads like a menu board. Member projects are the "specials." Everything else, body copy, buttons, form fields, footer, is set in a clean, quiet sans-serif with plenty of air. The signs are the personality; the rest of the page gets out of their way. Lettering the whole page would be exhausting; don't.

This direction lives or dies on texture. Every painted surface must be generated: the sign boards, the painted lettering, the wear at the edges, the wood or brick behind it. A display font with a CSS text-shadow will look like a template and is not acceptable. Generate the signs as images, or generate the surfaces and composite live text over them if the copy needs to stay editable; explain which you chose and why in DESIGN-NOTE.md. Generate the hero sign first and let it set the palette.

Seed-string decisions: the enamel palette, sign shapes, surface material, the sans-serif pairing, layout rhythm.

Follow this procedure: 1. Generate a long, random alphanumeric string using a shell script. Use it as inspiration for every decision the brief doesn't already make. Look beyond the surface for subpatterns, special numbers, anything that inspires you. Don't reveal the string in the design. 2. Write DESIGN-NOTE.md defining the creative direction before writing any code. 3. Generate the imagery with the Codex CLI as described in CLAUDE.md. Do not fake textures, light, or surfaces with CSS gradients, box shadows, or filters. 4. Build it. Verify frame-by-frame in the browser at mobile and desktop widths. 5. Screenshot, write NOTES.md, and stop.

The first three seconds should say: you're invited, this is happening, it's here.

Read CLAUDE.md first.

Build the AI Friday homepage combining three ideas into one design. This is the ambitious one and it may not work. Try it anyway.

Structure: a shotgun house. One long vertical scroll where each section is a room in the order you'd walk through one: front room (the invitation), middle rooms (what AI Friday is, what people are building, what you'll walk away with), kitchen at the back (the Slack), back step (footer). Doorways are the transitions. Scrolling should feel like walking through the house.

Scene: the front room is a front porch on a warm, lively evening. Golden hour into blue hour, a few people already there, an empty chair, music from down the block. The RSVP is "pull up a chair." Haint blue, the pale blue of the city's porch ceilings, is the primary color. As you move deeper into the house the light changes and the scene gives way to the rooms.

Type: hand-painted shop signage for headlines only. Corner store, po-boy shop, laundromat vernacular; not saloon, not farmhouse, not café. One big painted sign at the front announces the next meetup. Each room's header is a smaller sign. Everything else is a clean, quiet sans-serif.

The risk here is clutter: three ideas fighting for attention. Resolve it by giving each idea one job. The house is the structure and nothing else. The porch is the feeling and lives mostly in the first screen. The signs are the voice and appear only as headers. If any of them tries to do more than its job, cut it back. Explain in DESIGN-NOTE.md how the three hand off to each other, and in NOTES.md what fought with what.

Imagery to generate: the porch scene, the architectural surfaces, the painted signs.

Follow this procedure: 1. Generate a long, random alphanumeric string using a shell script. Use it as inspiration for every decision the brief doesn't already make. Look beyond the surface for subpatterns, special numbers, anything that inspires you. Don't reveal the string in the design. 2. Write DESIGN-NOTE.md defining the creative direction before writing any code. 3. Generate the imagery with the Codex CLI as described in CLAUDE.md. Do not fake textures, light, or surfaces with CSS gradients, box shadows, or filters. 4. Build it. Verify frame-by-frame in the browser at mobile and desktop widths. 5. Screenshot, write NOTES.md, and stop.

The first three seconds should say: you're invited, this is happening, it's here.