# Extension Browse Page Redesign Brief You are designing **one** mockup of the swamp.club Extensions browse page. Your output is a single self-contained `.html` file viewable in a browser by `file://` (no build step). Other agents are exploring different directions in parallel — make your design distinct. ## The problem with today's page Today's `/extensions` page (see `islands/ExtensionBrowser.tsx`) shows a 3-column grid of cards. Each card crams in: - Name (cyan, broken across line because of `break-all`) - 2-line description - 4 platform pills (cyan) - 2–3 label pills (purple) - 1–3 content-type pills (amber) - Version string - Score ring overlapping the bottom-right Above the grid is a multi-row filter strip with **Platform**, **Created** date presets, and **Content Type** as separate chip groups, plus a separate sort dropdown. The result: each card is a confetti of colored chips, and the filter area takes ~25% of the viewport before any results appear. The home page (`islands/LandingPageCyberpunk.tsx`, components in `components/landing/`) is much calmer — numbered section headers (`01 BUILDING BLOCKS`, `02 WHAT CHANGES`, `03 HOW IT WORKS`), thin separators, mostly black surfaces with single-color text. Color is used sparingly for emphasis. The extensions page should feel like it lives in the same product. ## Goals 1. **Convey similar information more concisely.** A user scanning the page should be able to identify what an extension does, what it runs on, and how good it is — without parsing four colors of pills. 2. **Offer the same or different filtering.** You can keep platform / content type / label / date / search / sort, OR you can argue for a different model (faceted, search-only, category-driven, JTBD, etc.). Whatever you pick, make filter changes feel low-cost. 3. **Reduce visual noise.** Borrow the home page's restraint: thin rules, numbered headers, sparing color, mostly mono and Chakra Petch type. Keep cyberpunk identity but stop shouting. ## Design constraints - **Standalone HTML.** Inline `