type: spec
topic: Club 33 website design/UI/UX
date: 2026-05-24
owner: Arthur
status: ready-for-Claude-bots
source_inspiration:
- ConductScience tracker / lab-freezers analysis by Merlin
- Club 33 voice note from S
- Instagram/booking/current-site reconnaissance
Club 33 — Design, UI, and UX Specification
0. Executive direction
Build **Club 33** as a premium men’s grooming brand, not just a barber appointment page.
Chosen direction: **Executive Noir + Booking First**
1. ConductScience patterns to adapt
Read from Merlin’s ConductScience tracker, especially `/lab-freezers` analysis.
A. Editorial big-type hero
ConductScience uses large declarative headlines with a terminal period and accent glyph treatment.
Club 33 adaptation:
B. Floating recommendation/spec card
ConductScience’s freezer page uses a “recommended path” spec card to make the page feel configured.
Club 33 adaptation:
C. Mixed-unit stats bar
ConductScience uses asymmetric metrics: classes, tools, temperature range, quote turnaround.
Club 33 adaptation:
D. Multi-step spec builder
ConductScience asks questions before recommending equipment.
Club 33 adaptation:
Create a “Build your grooming ritual” chooser:
1. What do you need? haircut / beard / both / spa
2. Occasion? work / event / date / maintenance
3. Time available? 30 / 60 / 90+ min
4. Add-ons? facial / massage / manicure / pedicure
5. Preference? fastest available / master barber / private suite
Output: recommended service package + compatible barbers + first available times.
E. Real-world scenarios
ConductScience uses “Core facility / Single-PI lab / Cell bank.”
Club 33 adaptation:
F. Numbered product/service cards
ConductScience uses 01–05 cards and a configuration path.
Club 33 adaptation:
Use numbered cards:
01 Essential Cut
02 Beard Ritual
03 Executive Ritual
04 Private Grooming Suite
05 Spa Add-ons
2. Site architecture
Primary pages
1. `/` — homepage / executive brand + booking chooser
2. `/servicios/` — all services and packages
3. `/barberos/` — barber/specialist profiles
4. `/reservar/` — booking flow
5. `/experiencias/` — premium/private packages
6. `/ubicaciones/` — current + future multi-location structure
7. `/reviews/` — reviews by barber and service
8. `/blog/` — SEO education
SEO landing pages
3. Homepage anatomy
Section 1 — Nav
Section 2 — Hero
- Primary: “Reservar experiencia”
- Secondary: “Ver servicios” or Instagram
Section 3 — Mixed stats strip
Section 4 — Build your ritual
Interactive wizard / spec builder.
Section 5 — Packages
Numbered service cards.
Section 6 — Barber compatibility
Card grid per barber.
Each barber card must show:
Section 7 — Scenarios
Each scenario recommends packages.
Section 8 — Reviews
Section 9 — Location + contact
4. Visual system
Palette
Typography
Components
5. Booking UX rules
Booking flow
1. Choose experience/service.
2. Show only compatible barbers.
3. Choose date/time.
4. Collect name, phone/WhatsApp, email optional.
5. Confirm.
Critical rule
Do **not** let the visitor pick a barber who cannot do the selected service/add-ons.
Data model
Service:
Barber:
Location:
6. Bilingual requirements
Spanish-first, English available.
Spanish tone:
English tone:
7. Claude bot instructions
Claude bots should produce:
1. A homepage design using this spec.
2. A service/package page.
3. A barber profile grid with compatibility logic.
4. A booking-flow wireframe.
5. Mobile state for all above.
Do not copy ConductScience visually. Copy the **patterns**:
8. Arthur implementation
Arthur’s live preview is here: