@gurupanguji

Tahoe Labs Parody Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Build a new /labs/ index page and a Tahoe parody page at /labs/is-it-time-to-upgrade-to-tahoe-yet/ with Tahoe and Sequoia visual modes, a giant NOPE switch, a hand-curated reading list, and a bottom-of-page fake Software Update trap that flips the page back into Tahoe mode.

Architecture: Add two standalone Jekyll HTML pages, keep the parody page self-contained, and drive the Tahoe versus Sequoia switch with a single top-level mode attribute plus page-scoped CSS variables and minimal JavaScript. Use hand-authored content in the page rather than a data layer, and keep Phase 2 automation out of scope.

Tech Stack: Jekyll, HTML, CSS, vanilla JavaScript, existing site header/footer patterns

---

File Map

• Create: labs/index.html
  • Labs landing page with a short intro and a single project card for the Tahoe parody page.
• Create: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
  • Standalone parody page with Tahoe and Sequoia modes, curated links, and the fake Software Update panel.
• Optional Create: assets/images/labs/
  • Only if implementation needs local image assets beyond pure HTML/CSS rendering.
• Optional Modify: assets/css/style.css
  • Only if one or two shared utilities are needed and keeping them global is cleaner than duplicating them locally.
• Test via local rendering
  • Jekyll build or serve, then visual/manual interaction checks.

Task 1: Create the /labs/ landing page

Files:

• Create: labs/index.html

• Reference: _layouts/, assets/css/style.css

• Step 1: Inspect existing standalone section pages for shared structure

Run:

sed -n '1,220p' about/index.html
sed -n '1,220p' reviews/index.html

Expected:

• Clear patterns for header, footer, dot-grid, and route-level page structure.

• Step 2: Write the landing page markup

Create labs/index.html with:

• front matter if needed for Jekyll processing
• dot-grid background
• standard header
• short Labs framing copy
• one strong card linking to /labs/is-it-time-to-upgrade-to-tahoe-yet/

• standard footer

• Step 3: Add page-local styles for the Labs index

Implement minimal styling directly in labs/index.html or a tightly scoped style block:

• preserve the site’s visual language
• make the page feel slightly more experimental than the standard indexes

• keep mobile layout clean

• Step 4: Manually review route semantics

Check:

• the route is exactly /labs/
• the card link points to /labs/is-it-time-to-upgrade-to-tahoe-yet/

• no relative-path mistakes are introduced

• Step 5: Commit the landing page

git add labs/index.html
git commit -m "Add Labs landing page"

Task 2: Scaffold the parody page structure

Files:

• Create: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Step 1: Write the basic page skeleton

Create labs/is-it-time-to-upgrade-to-tahoe-yet/index.html with:

• standard site shell
• one root wrapper for page mode, for example data-mode="tahoe"
• named sections for:
  • hero
  • Tahoe evidence wall
  • reading list
  • Sequoia relief framing
  • bottom Software Update trap
• Step 2: Hard-code current version values

Set:

• Tahoe 26.4
• Sequoia 15.7.5

Expected:

• version numbers appear in the hero and in the Software Update panel where appropriate

• Step 3: Add placeholder hand-curated links

Insert stub content blocks for:

• From this site
• Elsewhere

Expected:

• structure exists before styling or final curation is refined

• Step 4: Add semantic hooks for mode-driven styling

Include class names or data attributes for:

• Tahoe-only visual jokes
• Sequoia-clean state surfaces
• main NOPE action

• bottom Upgrade Now action

• Step 5: Commit the scaffold

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Scaffold Tahoe parody page"

Task 3: Implement Tahoe mode visual language

Files:

• Modify: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Step 1: Add failing visual acceptance checklist in comments or working notes

Document the expected Tahoe-mode cues before styling:

• inconsistent radii
• reduced contrast
• overused translucent surfaces
• layered cards/windows
• visible joke labels

Expected:

• a clear styling checklist exists before implementation drifts

• Step 2: Add Tahoe-mode CSS variables

Define variables for:

• surface colors
• text contrast
• glass/blur effects
• radius sizes

• highlight colors

• Step 3: Style the hero in Tahoe mode

Implement:

• page title
• large NOPE
• Tahoe and Sequoia version callouts

• fake feature labels such as Liquid Glass++ and Contrast Optional

• Step 4: Style the Tahoe evidence wall

Create 2 to 3 fake windows/cards that visibly demonstrate:

• divergent corner radii
• low contrast

• excessive layering

• Step 5: Review Tahoe mode on desktop and mobile

Run:

bundle exec jekyll build

Expected:

• build succeeds

• Tahoe mode reads as intentionally bad but still usable

• Step 6: Commit Tahoe-mode styling

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Style Tahoe mode for parody page"

Task 4: Implement Sequoia mode visual language

Files:

• Modify: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Step 1: Add Sequoia-mode CSS variables

Define cleaner values for:

• radii
• contrast
• surfaces
• accent colors

• spacing feel where necessary

• Step 2: Map the root mode attribute to the Sequoia visual state

Implement CSS selectors so that:

• Tahoe mode remains default
• Sequoia mode fully cleans up the page

• no Tahoe-only artifacts remain after the mode switch

• Step 3: Style the Sequoia relief sections

Ensure:

• the hero becomes coherent
• the evidence wall becomes calmer rather than disappearing awkwardly

• the reading list remains legible and attractive

• Step 4: Manually verify before/after legibility

Expected:

• the difference is immediate

• Sequoia mode feels like relief rather than just “slightly different theme”

• Step 5: Commit Sequoia-mode styling

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Add Sequoia relief mode"

Task 5: Add interaction logic

Files:

• Modify: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Step 1: Write the minimal interaction script

Implement vanilla JS to:

• switch from Tahoe to Sequoia when NOPE is clicked

• switch from Sequoia back to Tahoe when Upgrade Now is clicked

• Step 2: Ensure controls are keyboard accessible

Use real buttons or button-like semantics so:

• NOPE is focusable and activatable by keyboard

• Upgrade Now is focusable and activatable by keyboard

• Step 3: Test the interaction manually

Expected:

• page loads in Tahoe mode
• clicking NOPE switches the whole page to Sequoia mode

• clicking Upgrade Now switches the whole page back to Tahoe mode

• Step 4: Commit the interaction logic

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Add Tahoe and Sequoia mode switching"

Task 6: Finalize curated content

Files:

• Modify: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Step 1: Replace placeholder internal links with curated site links

Add hand-picked links from gurupanguji posts with one-line rationale blurbs.

• Step 2: Add curated external links

Add a small external section with one-line rationale blurbs.

• Step 3: Review link formatting and source correctness

Check:

• URLs are correct
• labels are readable

• no source lines accidentally use markdown shapes that could trigger table parsing

• Step 4: Commit curated content

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Curate Tahoe parody reading list"

Task 7: Build the Software Update punchline

Files:

• Modify: labs/is-it-time-to-upgrade-to-tahoe-yet/index.html

• Optional Create: assets/images/labs/* if a local asset is strictly needed

• Step 1: Recreate a high-quality Sequoia-style Software Update panel

Implement the bottom panel with:

• installed Sequoia state
• offered Tahoe upgrade
• version values

• system-settings-inspired layout

• Step 2: Integrate the Upgrade Now action

Ensure the button:

• is visually convincing in Sequoia mode

• returns the page to Tahoe mode

• Step 3: Review the punchline in scroll context

Expected:

• the panel reads as the page’s final joke

• the loop back to Tahoe mode feels intentional and immediate

• Step 4: Commit the Software Update panel

git add labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Add parody Software Update panel"

Task 8: Verify end-to-end behavior

Files:

• Review only

• Step 1: Run a clean Jekyll build

Run:

bundle exec jekyll build

Expected:

• successful build

• Step 2: Manually verify both routes

Check:

• /labs/

• /labs/is-it-time-to-upgrade-to-tahoe-yet/

• Step 3: Verify interaction loop

Check:

• Tahoe mode is default
• NOPE flips to Sequoia mode

• Upgrade Now flips back to Tahoe mode

• Step 4: Verify responsive layout

Check:

• desktop

• mobile-width viewport

• Step 5: Inspect for visual regressions

Check:

• header/footer consistency
• readable content in both modes

• intentional, not accidental, corner-radius inconsistency in Tahoe mode

• Step 6: Commit final verification fixes if needed

git add labs/index.html labs/is-it-time-to-upgrade-to-tahoe-yet/index.html
git commit -m "Polish Tahoe labs parody page"

Task 9: Prepare PR

Files:

• Review only

• Step 1: Review final diff

Run:

git status --short
git diff --stat main...HEAD

• Step 2: Push the branch

Run:

git push -u origin <branch-name>

• Step 3: Open the PR

Include:

• /labs/ landing page
• parody page
• interaction summary
• manual verification notes
• explicit mention that version automation remains Phase 2 and is tracked by issue #135