The big rewrite

.agents/skills/deduplicate-items/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: deduplicate-items
+description: Find and merge duplicate item names in the site database using the CLI. Use when the user asks to deduplicate, merge, clean up, or consolidate items — optionally filtered by tag (e.g. "headphones", "keyboard", "editor").
+---
+
+# Deduplicate Items
+
+Find variant spellings / naming inconsistencies for items in the site database and merge them into canonical names via the CLI.
+
+## Prerequisites
+
+- Working directory: the repo root (`/Users/wesbos/Dropbox/awesome-uses`)
+- Dependencies installed (`pnpm install`)
+- Local D1 SQLite database available (auto-resolved from `.wrangler/`)
+
+## Workflow
+
+### 1. List items for the target tag
+
+Paginate through **all** results — the API returns at most 100 rows per call.
+
+```bash
+pnpm site:tools:call items.list --input '{"tag": "<TAG>", "limit": 500, "offset": 0}'
+```
+
+Increment `offset` by 500 until you've fetched all rows (check the `total` field in the first response). Collect every `(item, count)` pair.
+
+### 2. Run the built-in duplicate detector
+
+```bash
+pnpm site:tools:call items.findDuplicates --input '{}'
+```
+
+This catches **case-only** differences. It does NOT catch abbreviations, missing hyphens, extra words, or typos — you must find those manually.
+
+### 3. Identify duplicate groups manually
+
+Compare the full item list for patterns like:
+
+| Pattern                         | Example                                           |
+| ------------------------------- | ------------------------------------------------- |
+| Brand prefix added/removed      | `Apple AirPods Pro` vs `AirPods Pro`              |
+| Abbreviation vs full name       | `Bose QC35` vs `Bose QuietComfort 35`             |
+| Missing/extra hyphens or spaces | `Sennheiser HD25` vs `Sennheiser HD 25`           |
+| Trailing descriptor             | `Sony WH-1000XM4 Headphones` vs `Sony WH-1000XM4` |
+| Seller prefix                   | `Linsoul KZ ZS10 Pro` vs `KZ ZS10 Pro`            |
+| Typos / transposed letters      | `Sony WF-1000MX5` vs `Sony WF-1000XM5`            |
+| Case differences                | `BeyerDynamic` vs `Beyerdynamic`                  |
+
+### 4. Present findings and ask for approval
+
+Show the user a table of proposed merges with canonical name, variants, and user counts. **Do not merge without explicit approval.**
+
+### 5. Merge via CLI
+
+For each approved group:
+
+```bash
+pnpm site:tools:call items.merge --input '{"canonicalItem": "<CANONICAL>", "sourceItems": ["<VARIANT1>", "<VARIANT2>"]}'
+```
+
+- The canonical item is the most-used or most-correct spelling.
+- Run up to 4 merge commands in parallel for speed.
+- Every merge returns `affectedPeople`, `upsertedRows`, `deletedRows` — verify each succeeds (`"ok": true`).
+
+### 6. Report results
+
+Summarize: how many groups merged, total variants consolidated, total people affected.
+
+## Choosing the canonical name
+
+Pick the name that is:
+
+1. **Most commonly used** (highest `count`)
+2. **Officially correct** (matches the manufacturer's branding)
+3. **Most specific** (e.g. `Bose QuietComfort 35 II` over `Bose QC35 II`)
+
+When the most-used name conflicts with official branding, prefer official branding.
+
+## Edge cases
+
+- **Different product variants** (e.g. wired vs wireless, different generations): do NOT merge unless they are clearly the same product with different naming.
+- **Ambiguous short names** (e.g. `Sennheiser` alone): leave as-is unless the user decides.
+- **Cross-brand confusion** (e.g. `AKG ATH-M50` — AKG doesn't make this, Audio-Technica does): flag as a data error to the user.
+
+## CLI reference
+
+| Command                                                                                       | Description                      |
+| --------------------------------------------------------------------------------------------- | -------------------------------- |
+| `pnpm site:tools:call items.list --input '{"tag":"<TAG>","limit":500,"offset":0}'`            | List items by tag (paginate)     |
+| `pnpm site:tools:call items.findDuplicates --input '{}'`                                      | Auto-detect case-only duplicates |
+| `pnpm site:tools:call items.merge --input '{"canonicalItem":"<NAME>","sourceItems":["..."]}'` | Merge variants into canonical    |
+
+Full CLI docs: `docs/site-management-toolkit.md`

.agents/skills/deduplicate-tags/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: deduplicate-tags
+description: Find and merge duplicate or overlapping tags in the site database using the CLI. Use when the user asks to deduplicate, merge, clean up, or consolidate tags — e.g. plurals, hyphen vs space variants, or synonyms like "browser" and "web browser".
+---
+
+# Deduplicate Tags
+
+Find duplicate, overlapping, or inconsistently named tags in the site database and merge them into canonical tags via the CLI.
+
+## Prerequisites
+
+- Working directory: the repo root (`/Users/wesbos/Dropbox/awesome-uses`)
+- Dependencies installed (`pnpm install`)
+- Local D1 SQLite database available (auto-resolved from `.wrangler/`)
+
+## Workflow
+
+### 1. List all tags
+
+```bash
+pnpm site:tools:call tags.list --input '{}'
+```
+
+Returns `{ total, rows: [{ tag, itemCount, personCount }] }` sorted by `itemCount` descending. No pagination needed — all rows are returned in one call.
+
+### 2. Identify duplicate groups
+
+Scan the full tag list for these patterns:
+
+| Pattern | Example |
+|---------|---------|
+| Singular vs plural | `speaker` vs `speakers` |
+| Hyphen vs space | `file-manager` vs `file manager` |
+| Trailing "s" variant | `framework` vs `frameworks` |
+| Synonym / alias | `os` vs `operating system` |
+| Verbose variant | `email-client` vs `email client` vs `mail client` vs `mail` |
+| Sub-type that should merge up | `mechanical keyboard` → `keyboard` |
+| Noun vs gerund | `linter` vs `linting` |
+| Compound overlap | `rss-reader` vs `rss reader` vs `feed-reader` vs `rss` |
+| Abbreviation | `vcs` vs `version control` |
+
+Group them into merge sets: one **target tag** and one or more **source tags**.
+
+### 3. Choose the canonical (target) tag
+
+Pick the tag that is:
+
+1. **Most commonly used** (highest `itemCount` or `personCount`)
+2. **Consistent with existing conventions** — prefer the hyphenated slug form used by the majority of tags (e.g. `email-client` over `email client`)
+3. **Concise but clear** (e.g. `os` over `operating system`, `browser` over `web browser`)
+
+### 4. Present findings and ask for approval
+
+Show the user a table of proposed merges:
+
+| # | Canonical Tag | Source Tags | Rationale |
+|---|---|---|---|
+| 1 | `browser` | `browsers`, `web browser` | Plural + synonym |
+
+**Do not merge without explicit approval.**
+
+### 5. Merge via CLI
+
+For each approved group:
+
+```bash
+pnpm site:tools:call tags.merge --input '{"targetTag": "<TARGET>", "sourceTags": ["<SRC1>", "<SRC2>"]}'
+```
+
+- Run up to 4 merge commands in parallel for speed.
+- Every merge returns `{ targetTag, sourceTags, updatedRows, mergedRefs }` — verify each succeeds (`"ok": true`).
+
+### 6. Report results
+
+Summarize: how many groups merged, total source tags eliminated, total rows updated, total refs merged.
+
+### 7. Optional: run again
+
+After the first pass, re-list tags and look for second-order duplicates that only become visible once the first batch is consolidated (e.g. `developer tool` and `development tools` may both still exist after merging other variants).
+
+## Edge cases
+
+- **Genuinely distinct sub-types**: Do NOT merge tags that represent meaningfully different categories even if names are similar. For example, `browser extension` and `vs code extension` are specific sub-types of `extension` — only merge if the user explicitly approves.
+- **Ambiguous overlap**: When two tags partially overlap (e.g. `music` vs `music streaming`), leave them separate unless the user decides.
+- **Very low-count tags** (1 item, 1 person): These are often one-off tags from a single person's page. They are good merge candidates but verify they actually match the target concept.
+- **"other" tag**: Never merge anything into or out of the `other` tag — it is a catch-all.
+
+## CLI reference
+
+| Command | Description |
+|---------|-------------|
+| `pnpm site:tools:call tags.list --input '{}'` | List all tags with item/person counts |
+| `pnpm site:tools:call tags.get --input '{"tag":"<TAG>"}'` | Get detail for one tag (items, people) |
+| `pnpm site:tools:call tags.merge --input '{"targetTag":"<T>","sourceTags":["..."]}'` | Merge source tags into target |
+| `pnpm site:tools:call tags.rename --input '{"fromTag":"<OLD>","toTag":"<NEW>"}'` | Rename a single tag |
+| `pnpm site:tools:call tags.deleteOrReplace --input '{"tag":"<TAG>","replacementTag":"<REP>"}'` | Delete tag, optionally replacing it |
+
+Full CLI docs: `docs/site-management-toolkit.md`

.agents/uses-page/SKILL.md

@@ -0,0 +1,153 @@
+# /uses Page Generator
+
+Generate a comprehensive /uses page for a developer by gathering information about their hardware, software, desk setup, and workflow through an interactive interview process.
+
+## Overview
+
+A /uses page documents a developer's current setup — the tools, hardware, software, and configurations they rely on daily. This skill guides the user through creating one by asking targeted questions, optionally running system detection, and exporting the result in their preferred format.
+
+## Process
+
+### Step 1: System Detection (Optional)
+
+Ask the user if they'd like to auto-detect their system info. If yes, run the helper script:
+
+```bash
+bash .agents/uses-page/gather-system-info.sh
+```
+
+This will output hardware model, OS, display info, and installed developer tools. Use this as a starting point for the interview.
+
+### Step 2: Interview — Hardware
+
+Ask about each section. Don't ask all at once — go section by section, confirming and expanding on each answer before moving to the next.
+
+**Computer**
+- What computer(s) do you use? (e.g. MacBook Pro 16" M4 Max, custom PC build, ThinkPad X1 Carbon)
+- CPU, RAM, storage specs if they know them
+- Do you use a laptop, desktop, or both?
+
+**Peripherals & Desk**
+- Monitor(s): brand, size, resolution (e.g. LG 27" 4K, Apple Studio Display)
+- Keyboard: brand and model (e.g. Keychron Q1, HHKB, Apple Magic Keyboard)
+- Mouse/trackpad: brand and model
+- Webcam, microphone, headphones/speakers
+- Desk: standing desk? Brand? (e.g. Uplift, IKEA Bekant)
+- Chair: brand and model (e.g. Herman Miller Aeron, Steelcase Leap)
+- Any other desk accessories (monitor arm, desk mat, cable management, lighting)
+
+**Phone & Tablet**
+- Phone: model (e.g. iPhone 16 Pro, Pixel 9)
+- Tablet: if used for development or note-taking
+
+### Step 3: Interview — Software & Development Environment
+
+**Editor & Terminal**
+- Primary code editor (e.g. VS Code, Neovim, Cursor, Zed, WebStorm)
+- Editor theme and key extensions/plugins
+- Terminal emulator (e.g. iTerm2, Warp, Ghostty, Kitty, Alacritty, Windows Terminal)
+- Shell (e.g. zsh, fish, bash, nushell) and framework (e.g. oh-my-zsh, starship prompt)
+- Font for coding (e.g. Fira Code, JetBrains Mono, MonoLisa, Dank Mono)
+
+**Browser & DevTools**
+- Primary browser for development
+- Key browser extensions
+
+**Design & Creative Tools**
+- Design tools (e.g. Figma, Sketch, Adobe CC, Affinity)
+- Image/video editing
+
+**Productivity & Workflow**
+- Note-taking (e.g. Obsidian, Notion, Apple Notes, Bear)
+- Task management (e.g. Linear, Todoist, Things, ClickUp)
+- Communication (e.g. Slack, Discord)
+- Password manager (e.g. 1Password, Bitwarden)
+- Cloud storage
+- Music/focus app (e.g. Spotify, Apple Music)
+- Window management (e.g. Raycast, Rectangle, yabai)
+- Launcher (e.g. Raycast, Alfred, Spotlight)
+
+**Development Stack**
+- Primary languages and frameworks
+- Package managers (npm, pnpm, yarn, bun)
+- Version control workflow
+- Hosting/deployment (e.g. Vercel, Cloudflare, AWS, Netlify)
+- Database preferences
+- API tools (e.g. Postman, Insomnia, httpie)
+- Docker/containers?
+
+### Step 4: Review & Follow-up
+
+After gathering initial answers:
+
+1. Summarize what you have so far in a draft format
+2. Ask follow-up questions about anything that seems incomplete:
+   - "You mentioned VS Code — do you have a specific theme or must-have extensions?"
+   - "Any dotfiles or config repos you'd like to link?"
+   - "Anything unusual or unique about your setup that people would find interesting?"
+3. Ask if there are sections they want to add:
+   - Gaming setup
+   - Home office lighting/ambiance
+   - Self-hosting / homelab
+   - Podcasting/streaming gear
+   - Photography/videography equipment
+
+### Step 5: Export
+
+Ask the user their preferred format, then generate the page:
+
+**Markdown** (most common for /uses pages):
+```markdown
+# Uses
+
+> Last updated: March 2026
+
+## Hardware
+
+### Computer
+- MacBook Pro 16" M4 Max (64GB RAM, 1TB SSD)
+
+### Desk Setup
+- Monitor: LG 27UK850 4K
+- Keyboard: Keychron Q1 with Gateron Brown switches
+...
+
+## Software
+
+### Editor
+- VS Code with the Vitesse theme
+- Key extensions: ESLint, Prettier, GitHub Copilot
+...
+```
+
+**HTML** — A styled, standalone HTML page with sections and anchors.
+
+**JSX/React** — A React component with semantic markup, ready to drop into a Next.js/Remix/Astro site.
+
+**Rich Text** — Formatted text suitable for pasting into a CMS or Google Doc.
+
+## Tips for a Great /uses Page
+
+- Be specific: "MacBook Pro 16" M4 Max" is better than "MacBook"
+- Include why you chose things when interesting: "I switched to Neovim for the modal editing speed"
+- Link to products/tools where possible
+- Update it periodically — setups change!
+- Add a personal touch: what makes YOUR setup unique?
+- Photos of your desk setup are a huge plus (mention this to the user)
+
+## Common Sections from Existing /uses Pages
+
+Based on analysis of hundreds of developer /uses pages, the most common sections are:
+
+1. **Computer/Laptop** — nearly universal
+2. **Code Editor** — VS Code dominates, but Neovim, Cursor, and Zed are rising
+3. **Terminal** — iTerm2, Warp, Ghostty, Kitty are popular
+4. **Browser** — Chrome, Firefox, Arc, Brave
+5. **Keyboard** — mechanical keyboards are very popular in the community
+6. **Monitor** — ultrawide and 4K are common
+7. **Desk & Chair** — standing desks and ergonomic chairs
+8. **Headphones** — Sony WH-1000XM series, AirPods Pro, Audio-Technica
+9. **Hosting** — Vercel, Cloudflare, Netlify, AWS
+10. **Frameworks** — React, Next.js, Svelte, Vue, Astro
+11. **Fonts** — Fira Code, JetBrains Mono, MonoLisa
+12. **Themes** — One Dark Pro, Dracula, Catppuccin, Vitesse