diff --git a/.claude/skills/product-area/SKILL.md b/.claude/skills/product-area/SKILL.md
new file mode 100644
index 0000000..3bfadc8
--- /dev/null
+++ b/.claude/skills/product-area/SKILL.md
@@ -0,0 +1,122 @@
+---
+name: Product Area
+description: This skill should be used when the user asks to "add a product area", "create a product area", "new product area", "add area to docs", "create area page", or mentions adding a new area to docs/areas/. Creates the area markdown document with SVG banner and registers the area in project configuration if it does not already exist.
+---
+
+# Product Area Creation
+
+Create new product-area documents in `docs/areas/` with an SVG banner, shields.io badge, and project configuration registration. Each product area represents a top-level category of product functionality (e.g., Workspaces, Coding Standards, Developer Tools).
+
+## Workflow
+
+### Step 1: Load Existing Product Areas
+
+Read `scripts/conf/project.json` and extract the `Product Area` field options to get the current list of registered areas. Also read `scripts/lib/product-area-colors.ts` to get the `PRODUCT_AREA_COLORS` map and `PRODUCT_AREAS` record.
+
+### Step 2: Gather Information
+
+Collect the following from the user:
+
+| Field | Required | Notes |
+| --- | --- | --- |
+| Area Title | Yes | Human-readable name (e.g., "Workspaces") |
+| Emoji | Yes | Single emoji for the area identifier |
+| Description | Yes | One-sentence description of the area |
+| Color | Yes | One of the `PRODUCT_AREA_COLORS` keys (BLUE, CYAN, PURPLE, GREEN, ORANGE, PINK, GRAY, YELLOW, RED) |
+| Overview | Yes | 1-2 paragraphs for the Overview section |
+| Features | Recommended | Feature list, optionally grouped by category |
+| FAQ | Optional | Question-and-answer pairs |
+
+Ask the user for any missing fields. Present the available colors from `PRODUCT_AREA_COLORS` as options.
+
+### Step 3: Check if Area Exists in Project Config
+
+Derive the area identifier as `<emoji> <kebab-case-label>` (e.g., `🔧 agent-setup`). Search the `Product Area` options in `scripts/conf/project.json` for a match.
+
+- If the area already exists, skip to Step 5
+- If the area does not exist, proceed to Step 4
+
+### Step 4: Register the Product Area
+
+When the area is new, update three files:
+
+**4a. Update `scripts/conf/project.json`**
+
+Add a new entry to the `fields[].options` array for the `Product Area` field:
+
+```json
+{
+  "name": "<emoji> <kebab-case-label>",
+  "description": "<description>",
+  "color": "<COLOR_NAME>"
+}
+```
+
+**4b. Update `scripts/lib/product-area-colors.ts`**
+
+Add a new entry to the `PRODUCT_AREAS` record:
+
+```typescript
+"<emoji> <kebab-case-label>": {
+  name: "<emoji> <kebab-case-label>",
+  emoji: "<emoji>",
+  label: "<Human Label>",
+  color: PRODUCT_AREA_COLORS.<COLOR_NAME>,
+},
+```
+
+**4c. Run lint and format**
+
+After editing TypeScript files, run `pnpm lint:fix` and `pnpm format` to ensure consistency.
+
+### Step 5: Create the SVG Banner
+
+Use the **SVG Banner** skill to create the banner SVG at `docs/areas/<area-name>.svg`. The banner should:
+
+- Use a single-pane or split-pane layout appropriate to the area content
+- Include the area title and a short subtitle in the title bar
+- Show representative CLI output or feature highlights as panel content
+- Follow the Catppuccin Mocha theme and inline-attribute conventions from the SVG Banner skill
+
+Reference `docs/areas/workspaces.svg` as an example of a completed area banner.
+
+### Step 6: Create the Area Document
+
+Write the markdown file to `docs/areas/<area-name>.md` using the template in `references/area-template.md`. Include:
+
+- Centered `<div align="center">` block containing the SVG banner, H1 title, and shields.io product-area badge (color and label from Step 2/4) — all grouped together under the banner
+- Overview section (required)
+- Features section with content from Step 2
+- FAQ section if provided
+- Any additional sections the user requests
+
+### Step 7: Confirm
+
+Display a summary of all changes:
+
+- Area document path (`docs/areas/<area-name>.md`)
+- SVG banner path (`docs/areas/<area-name>.svg`)
+- Whether project config was updated (new area) or already existed
+- Product area badge preview
+
+## File Locations
+
+| File | Purpose |
+| --- | --- |
+| `docs/areas/<name>.md` | Product area document |
+| `docs/areas/<name>.svg` | SVG banner asset |
+| `scripts/conf/project.json` | Product area registration |
+| `scripts/lib/product-area-colors.ts` | Product area color/label mapping |
+
+## Additional Resources
+
+### Reference Files
+
+- **`references/area-template.md`** — Complete markdown template with badge format and section guidelines
+
+### Examples
+
+Working product areas in the repository:
+
+- **`docs/areas/workspaces.md`** — Full product area document with all sections
+- **`docs/areas/workspaces.svg`** — Split pane SVG banner example
diff --git a/.claude/skills/product-area/references/area-template.md b/.claude/skills/product-area/references/area-template.md
new file mode 100644
index 0000000..a69e14f
--- /dev/null
+++ b/.claude/skills/product-area/references/area-template.md
@@ -0,0 +1,97 @@
+# Product Area Template
+
+This is the reference template for product-area documents in `docs/areas/`. Adapt sections as needed per area — the Overview is required, all others are optional.
+
+## File Structure
+
+Each product area consists of two files in `docs/areas/`:
+
+```
+docs/areas/
+├── <area-name>.md    # Product area document
+└── <area-name>.svg   # SVG banner (Catppuccin Mocha terminal style)
+```
+
+The `<area-name>` is the kebab-case version of the area title (e.g., "Workspaces" becomes `workspaces`).
+
+## Markdown Template
+
+```markdown
+<div align="center">
+
+<img src="./<area-name>.svg" alt="<Area Title> Banner" width="100%" />
+
+# <Area Title>
+
+![<Product Area Label>](https://img.shields.io/badge/<Encoded Label>-<hex color>?style=flat-square)
+
+</div>
+
+## Overview
+
+<1-2 paragraphs describing the product area: what it is, why it exists, and who it serves.>
+
+## Features
+
+### <Category Name>
+
+- **<Feature name>** - <one-line description of the feature>
+- **<Feature name>** - <one-line description of the feature>
+
+### <Category Name>
+
+- **<Feature name>** - <one-line description of the feature>
+
+---
+
+## FAQ
+
+### <Question?>
+
+<Answer — 1-3 paragraphs.>
+
+### <Question?>
+
+<Answer — 1-3 paragraphs.>
+```
+
+## Product Area Badge
+
+Each area doc includes a shields.io badge below the H1 title. The badge color and label come from `scripts/conf/project.json` (Product Area field options) and `scripts/lib/product-area-colors.ts`.
+
+Badge format: `![<Label>](https://img.shields.io/badge/<URL-encoded Label>-<hex color>?style=flat-square)` — hex color without the `#` prefix
+
+Available colors from `PRODUCT_AREA_COLORS`:
+
+| Color Name | Hex | Example Usage |
+| --- | --- | --- |
+| BLUE | 0969da | agent-setup |
+| CYAN | 1f6feb | agent-sandbox |
+| PURPLE | 8250df | coding-standards |
+| GREEN | 1a7f37 | gg-workflow |
+| ORANGE | d4660b | developer-tools |
+| PINK | d15593 | context-integration |
+| GRAY | 6e7781 | documentation |
+| YELLOW | bf8700 | skills-agents |
+| RED | cf222e | platform |
+
+Use `encodeURIComponent` logic for the label in the URL (spaces become `%20`, `&` becomes `%26`, etc.).
+
+## Section Guidelines
+
+| Section | Required | Notes |
+| --- | --- | --- |
+| Banner + Title | Yes | SVG banner centered above the H1 title |
+| Product Area Badge | Yes | shields.io badge matching project.json color |
+| Overview | Yes | 1-2 paragraphs, no bullet lists |
+| Features | Recommended | Group by category with H3 headings, or use a flat list |
+| FAQ | Optional | Question-and-answer pairs addressing common concerns |
+| Additional sections | Optional | Add as needed (e.g., Architecture, API, Integrations) |
+
+## Writing Style
+
+- Write for a technical audience familiar with developer tools
+- Lead with the value proposition in the Overview
+- Feature descriptions should be concise — one line per feature, bold name + dash + description
+- FAQ answers should be direct and substantive, not marketing fluff
+- Use present tense throughout
diff --git a/.claude/skills/svg-banner/SKILL.md b/.claude/skills/svg-banner/SKILL.md
new file mode 100644
index 0000000..078bc30
--- /dev/null
+++ b/.claude/skills/svg-banner/SKILL.md
@@ -0,0 +1,138 @@
+---
+name: SVG Banner
+description: This skill should be used when the user asks to "create an SVG banner", "make a terminal SVG", "generate a banner image", "create a workspace SVG", "make a split pane SVG", "design a CLI screenshot SVG", or mentions creating SVG assets for README files or documentation. Provides templates and guidance for creating Catppuccin Mocha-themed terminal-style SVG banners.
+---
+
+# SVG Banner Creation
+
+Create terminal-style SVG banners using the Catppuccin Mocha color palette. These banners simulate a macOS terminal window and are used as visual assets in README files and documentation.
+
+## Layout Options
+
+Three layout types are available:
+
+| Layout | Description | Example |
+| --- | --- | --- |
+| **Single pane** | One full-width content panel | Product overview, ASCII art hero |
+| **Split pane** | Two side-by-side vertical panels | Comparing features, before/after |
+| **Split pane + bottom** | Two vertical panels with a bottom CLI bar | Split content with shared terminal |
+
+## PNG Compatibility
+
+All SVGs must be convertible to PNG via tools like `rsvg-convert`, `sharp`, Inkscape, or Puppeteer. To ensure this:
+
+- **Always set explicit `width` and `height`** on the `<svg>` element (not just `viewBox`)
+- **Use inline attributes instead of CSS classes** — apply `fill`, `font-family`, and `font-size` directly on each `<text>` and `<tspan>` element. Do NOT use a `<style>` block or CSS classes, as many PNG converters ignore them
+- **Use system-available monospace fonts** — the font stack `'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace` works well as a fallback chain
+- **Avoid external resources** — no `<image>`, `<use>`, `xlink:href`, or external font imports
+
+## Core Structure
+
+Every SVG banner follows this skeleton:
+
+1. **Outer frame** — rounded `<rect>` with `fill="#1e1e2e"` (Mocha base)
+2. **Title bar** — `<rect>` with `fill="#181825"` (Mocha mantle) + three traffic-light circles
+3. **Title text** — centered dim text in the title bar
+4. **Content area** — title/subtitle block, then layout-specific panels
+5. **Dividers** — `<line>` elements with `stroke="#313244"` (Mocha surface0)
+
+## Color Palette (Catppuccin Mocha)
+
+| Class | Hex | Usage |
+| --- | --- | --- |
+| `.brand` | `#a78bfa` | Brand/accent text, command flags |
+| `.dim` | `#6c7086` | Muted labels, comments, prompts |
+| `.st` | `#a6e3a1` | Success checkmarks, "running" |
+| `.tx` | `#cdd6f4` | Primary body text |
+| `.op` | `#9399b2` | Failure marks, operators |
+| `.prompt` | `#89b4fa` | Shell prompt `~`, links |
+| `.warn` | `#f9e2af` | Warnings, activity dots |
+| `.fn` | `#89b4fa` | Function names, paths, URLs |
+| `.peach` | `#fab387` | Status dots |
+
+Background colors:
+
+| Element | Hex | Catppuccin name |
+| --- | --- | --- |
+| Main background | `#1e1e2e` | Base |
+| Title bar / tabs | `#181825` | Mantle |
+| Dividers | `#313244` | Surface0 |
+| Input borders | `#45475a` | Surface1 |
+| Traffic light red | `#f38ba8` | Red |
+| Traffic light yellow | `#f9e2af` | Yellow |
+| Traffic light green | `#a6e3a1` | Green |
+
+## Dimensions & Spacing
+
+| Property | Value |
+| --- | --- |
+| Width | `1120` |
+| Default height (single/split) | `510`-`520` |
+| Height with bottom pane | `620`-`680` (adjust to content) |
+| Corner radius | `rx="10" ry="10"` |
+| Title bar height | `36` |
+| Content x-padding | `18` (left panel), `578` (right panel) |
+| Line spacing | `16`-`22` between text lines |
+| Divider inset | `x1="16"` to `x2="1104"` |
+| Vertical divider x | `560` (center) |
+| Horizontal bottom divider y | Varies — placed above bottom pane |
+
+## Building a Banner
+
+### Step 1: Determine Layout
+
+Ask the user which layout to use (single, split, or split + bottom) and what content belongs in each panel. Gather:
+
+- Title bar label (centered in macOS-style bar)
+- Title and subtitle (shown below title bar, above panels)
+- Content for each panel (typically CLI output, code, or tool UI)
+- Tab labels for each panel (e.g., "terminal", "claude code", "remote")
+
+### Step 2: Assemble the SVG
+
+Start from the shared boilerplate in `references/svg-template.md`. Select the appropriate layout section and populate with content.
+
+Key rules:
+
+- Use `xml:space="preserve"` on any `<text>` element that has leading whitespace
+- Use `&#x2713;` for checkmarks, `&#x2588;` for cursor block, `&#x25CF;` for status dot, `&#x2192;` for arrow
+- Apply `fill` and `font-family`/`font-size` as inline attributes on every `<text>` and `<tspan>` — never use CSS classes
+- Tab labels use `<rect>` with `fill="#181825"` + `<text>` with inline font styling
+- Indent continuation lines by increasing the `x` attribute (usually +8 per indent level)
+- The shared monospace font stack is: `font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace"`
+
+### Step 3: Size the SVG
+
+Calculate height based on content:
+
+- Title bar: 36px
+- Title + subtitle area: ~60px
+- Horizontal divider: ~16px gap
+- Each text line: ~16-22px
+- Bottom pane (if used): ~80-100px
+- Bottom padding: ~10px
+
+Set `viewBox="0 0 1120 <height>"` and match the outer `<rect>` height.
+
+### Step 4: Validate
+
+- Confirm `<svg>` has both `width`, `height`, and `viewBox` attributes
+- Confirm no `<style>` block or `class` attributes exist — all styling is inline
+- Confirm all `<tspan>` tags are closed
+- Confirm `xml:space="preserve"` is on lines with leading spaces
+- Confirm no raw `<`, `>`, or `&` in text content (use entities)
+- Confirm traffic lights are at `cx="20"`, `cx="40"`, `cx="60"`, `cy="18"`
+- Confirm viewBox height matches outer rect height and the `height` attribute
+
+## Additional Resources
+
+### Reference Files
+
+- **`references/svg-template.md`** — Complete SVG boilerplate for all three layouts with inline comments
+
+### Examples
+
+Working SVGs in the repository:
+
+- **`.github/assets/banner.svg`** — Split pane layout (terminal + Claude Code UI)
+- **`.github/assets/workspace.svg`** — Split pane layout (containerized + remote)
diff --git a/.claude/skills/svg-banner/references/svg-template.md b/.claude/skills/svg-banner/references/svg-template.md
new file mode 100644
index 0000000..9c28cd3
--- /dev/null
+++ b/.claude/skills/svg-banner/references/svg-template.md
@@ -0,0 +1,287 @@
+# SVG Banner Templates
+
+Complete boilerplate for each layout type. All templates use inline attributes (no CSS `<style>` block) to ensure reliable PNG conversion via `rsvg-convert`, `sharp`, Inkscape, Puppeteer, etc.
+
+## Inline Style Constants
+
+Instead of CSS classes, apply these inline attributes directly on each element:
+
+### Font Attributes
+
+Shorthand references used in templates below:
+
+| Ref | Inline attributes |
+| --- | --- |
+| `FONT` | `font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace"` |
+| `CODE` | `FONT font-size="12"` |
+| `TAB_FONT` | `FONT font-size="11" fill="#cdd6f4"` |
+| `TITLE_FONT` | `FONT font-size="14"` |
+| `SUBTITLE_FONT` | `FONT font-size="12"` |
+
+### Fill Colors
+
+Apply via `fill="..."` on `<text>` or `<tspan>` elements:
+
+| Name | Hex | Usage |
+| --- | --- | --- |
+| brand | `#a78bfa` | Brand/accent text, command flags |
+| dim | `#6c7086` | Muted labels, comments, `$ ` prompts |
+| st (green) | `#a6e3a1` | Success checkmarks, "running" |
+| tx (text) | `#cdd6f4` | Primary body text |
+| op | `#9399b2` | Failure marks, operators |
+| prompt | `#89b4fa` | Shell prompt `~`, links |
+| warn | `#f9e2af` | Warnings, activity dots |
+| fn | `#89b4fa` | Function names, paths, URLs |
+| peach | `#fab387` | Status dots |
+
+## Shared Title Bar
+
+Every SVG uses this title bar. Replace `<HEIGHT>` with the outer rect height:
+
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" width="1120" height="<HEIGHT>" viewBox="0 0 1120 <HEIGHT>">
+
+  <!-- Background -->
+  <rect width="1120" height="<HEIGHT>" rx="10" ry="10" fill="#1e1e2e" />
+  <rect width="1120" height="36" rx="10" ry="10" fill="#181825" />
+  <rect y="26" width="1120" height="10" fill="#181825" />
+  <circle cx="20" cy="18" r="6" fill="#f38ba8" />
+  <circle cx="40" cy="18" r="6" fill="#f9e2af" />
+  <circle cx="60" cy="18" r="6" fill="#a6e3a1" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" fill="#6c7086" x="560" y="22" text-anchor="middle"><TITLE_BAR_LABEL></text>
+```
+
+Notes:
+- The `<svg>` tag must have all three: `width`, `height`, and `viewBox`
+- The second `<rect>` (height 36) is the title bar background
+- The third `<rect>` (y=26, height 10) fills the gap between the rounded title bar and the content area
+- Traffic light circles are always at y=18, spaced 20px apart starting at x=20
+
+## Shared Title & Subtitle
+
+Placed below the title bar, centered:
+
+```xml
+  <!-- Title -->
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="14" fill="#a78bfa" x="560" y="62" text-anchor="middle"><TITLE></text>
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" fill="#6c7086" x="560" y="80" text-anchor="middle"><SUBTITLE></text>
+```
+
+If using ASCII art instead, use a `<g transform="translate(560, 58)">` group with multiple `<text>` lines at `text-anchor="middle"`. Each `<text>` line still needs inline `font-family`, `font-size`, and `fill`.
+
+## Layout: Single Pane
+
+Full-width content area below the title block. No vertical divider.
+
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" width="1120" height="<HEIGHT>" viewBox="0 0 1120 <HEIGHT>">
+  <!-- [shared title bar] -->
+  <!-- [shared title & subtitle] -->
+
+  <!-- Horizontal divider -->
+  <line x1="16" y1="96" x2="1104" y2="96" stroke="#313244" stroke-width="1" />
+
+  <!-- Tab label -->
+  <rect x="4" y="104" width="80" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="18" y="120"><TAB_LABEL></text>
+
+  <!-- Content lines starting at y ~148 -->
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="148">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4"><COMMAND></tspan>
+  </text>
+  <!-- ... more content lines, incrementing y by 16-22 ... -->
+
+  <!-- Cursor line (last line) -->
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<LAST_Y>">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4">&#x2588;</tspan>
+  </text>
+</svg>
+```
+
+## Layout: Split Pane
+
+Two side-by-side panels divided at x=560.
+
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" width="1120" height="<HEIGHT>" viewBox="0 0 1120 <HEIGHT>">
+  <!-- [shared title bar] -->
+  <!-- [shared title & subtitle] -->
+
+  <!-- Horizontal divider -->
+  <line x1="16" y1="96" x2="1104" y2="96" stroke="#313244" stroke-width="1" />
+  <!-- Vertical divider -->
+  <line x1="560" y1="96" x2="560" y2="<BOTTOM>" stroke="#313244" stroke-width="1" />
+
+  <!-- LEFT PANEL -->
+  <rect x="4" y="104" width="<TAB_WIDTH>" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="14" y="120"><LEFT_TAB></text>
+
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="152">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4"><COMMAND></tspan>
+  </text>
+  <!-- ... left panel content ... -->
+
+  <!-- RIGHT PANEL -->
+  <rect x="564" y="104" width="<TAB_WIDTH>" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="578" y="120"><RIGHT_TAB></text>
+
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="578" y="152">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4"><COMMAND></tspan>
+  </text>
+  <!-- ... right panel content ... -->
+</svg>
+```
+
+Key coordinates for split pane:
+- Left panel: `x="18"` for content, `x="4"` for tab rect, `x="14"` for tab text
+- Right panel: `x="578"` for content, `x="564"` for tab rect, `x="578"` for tab text
+- Vertical divider: `x1="560"`, running from horizontal divider y to near bottom
+
+## Layout: Split Pane + Bottom Pane
+
+Two side-by-side panels with a shared bottom CLI bar.
+
+```xml
+<svg xmlns="http://www.w3.org/2000/svg" width="1120" height="<HEIGHT>" viewBox="0 0 1120 <HEIGHT>">
+  <!-- [shared title bar] -->
+  <!-- [shared title & subtitle] -->
+
+  <!-- Horizontal divider (below title) -->
+  <line x1="16" y1="96" x2="1104" y2="96" stroke="#313244" stroke-width="1" />
+  <!-- Vertical divider (between left/right panels, stops at bottom pane) -->
+  <line x1="560" y1="96" x2="560" y2="<BOTTOM_PANE_Y>" stroke="#313244" stroke-width="1" />
+
+  <!-- LEFT PANEL -->
+  <rect x="4" y="104" width="<TAB_WIDTH>" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="14" y="120"><LEFT_TAB></text>
+
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="152">
+    <!-- ... left panel content ... -->
+  </text>
+
+  <!-- RIGHT PANEL -->
+  <rect x="564" y="104" width="<TAB_WIDTH>" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="578" y="120"><RIGHT_TAB></text>
+
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="578" y="152">
+    <!-- ... right panel content ... -->
+  </text>
+
+  <!-- BOTTOM PANE DIVIDER -->
+  <line x1="16" y1="<BOTTOM_PANE_Y>" x2="1104" y2="<BOTTOM_PANE_Y>" stroke="#313244" stroke-width="1" />
+
+  <!-- Bottom pane tab -->
+  <rect x="4" y="<BOTTOM_PANE_Y + 8>" width="80" height="24" rx="4" ry="4" fill="#181825" />
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="11" fill="#cdd6f4" x="18" y="<BOTTOM_PANE_Y + 24>"><BOTTOM_TAB></text>
+
+  <!-- Bottom pane content (full width) -->
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<BOTTOM_PANE_Y + 48>">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4"><COMMAND></tspan>
+  </text>
+  <!-- ... more bottom pane lines ... -->
+
+  <!-- Cursor line -->
+  <text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<LAST_Y>">
+    <tspan fill="#89b4fa">~</tspan>
+    <tspan fill="#6c7086"> $ </tspan>
+    <tspan fill="#cdd6f4">&#x2588;</tspan>
+  </text>
+</svg>
+```
+
+Key coordinates for bottom pane:
+- `<BOTTOM_PANE_Y>`: The y-coordinate where the bottom horizontal divider sits (typically after the tallest panel content ends, e.g. `420`-`460`)
+- Bottom pane content uses full width: `x="18"` (same as left panel)
+- The vertical divider between left/right panels stops at `<BOTTOM_PANE_Y>`, not at the SVG bottom
+
+## Content Patterns
+
+All patterns use inline attributes. The `font-family` and `font-size` are inherited from the parent `<text>` element, so `<tspan>` only needs `fill`.
+
+### CLI Output Line (success)
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>" xml:space="preserve"><tspan fill="#a6e3a1">  &#x2713;</tspan><tspan fill="#cdd6f4"> <message></tspan></text>
+```
+
+### CLI Output Line (warning)
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>" xml:space="preserve"><tspan fill="#f9e2af">  &#x26A0;</tspan><tspan fill="#cdd6f4"> <message></tspan></text>
+```
+
+### CLI Output Line (failure)
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>"><tspan fill="#9399b2">  &#x2717;</tspan><tspan fill="#cdd6f4"> <message></tspan></text>
+```
+
+### Status Line
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>"><tspan fill="#fab387">  &#x25CF;</tspan><tspan fill="#cdd6f4"> <label> </tspan><tspan fill="#a6e3a1">running</tspan><tspan fill="#6c7086"> (<detail>)</tspan></text>
+```
+
+### Dim Commentary
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" fill="#6c7086" x="18" y="<Y>">  <message></text>
+```
+
+### Shell Prompt with Command
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>"><tspan fill="#89b4fa">~</tspan><tspan fill="#6c7086"> $ </tspan><tspan fill="#cdd6f4"><command></tspan><tspan fill="#a78bfa"> <flag></tspan></text>
+```
+
+### Key-Value Metadata
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="18" y="<Y>" xml:space="preserve"><tspan fill="#6c7086">    <key>: </tspan><tspan fill="#cdd6f4"><value></tspan></text>
+```
+
+### Tool Activity Dot (Claude Code style)
+
+```xml
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" x="578" y="<Y>"><tspan fill="#f9e2af">&#x25CF;</tspan><tspan fill="#cdd6f4"> <ToolName></tspan><tspan fill="#6c7086">(<argument>)</tspan></text>
+```
+
+### Input Box (bottom of a panel)
+
+```xml
+<line x1="<X1>" y1="<Y>" x2="<X2>" y2="<Y>" stroke="#45475a" stroke-width="1" />
+<text font-family="'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace" font-size="12" fill="#cdd6f4" x="<X_TEXT>" y="<Y + 16>">&gt; &#x2588;</text>
+<line x1="<X1>" y1="<Y + 24>" x2="<X2>" y2="<Y + 24>" stroke="#45475a" stroke-width="1" />
+```
+
+## XML Entity Reference
+
+| Character | Entity | Usage |
+| --- | --- | --- |
+| Checkmark | `&#x2713;` | Success indicators |
+| Block cursor | `&#x2588;` | Active cursor |
+| Filled circle | `&#x25CF;` | Status/activity dots |
+| Right arrow | `&#x2192;` | "Go to" indicators |
+| Warning | `&#x26A0;` | Warning indicators |
+| Ballot X | `&#x2717;` | Failure indicators |
+
+## Tab Width Calculation
+
+Tab widths are calculated based on the label length. Approximate at ~8px per character + 16px padding:
+
+| Label | Characters | Width |
+| --- | --- | --- |
+| "terminal" | 8 | 80 |
+| "remote" | 6 | 80 |
+| "containerized" | 13 | 110 |
+| "claude code" | 11 | 100 |
diff --git a/docs/areas/workspaces.md b/docs/areas/workspaces.md
new file mode 100644
index 0000000..f2706d9
--- /dev/null
+++ b/docs/areas/workspaces.md
@@ -0,0 +1,124 @@
+<div align="center">
+
+<img src="./workspaces.svg" alt="Workspaces Banner" width="100%" />
+
+</div>
+
+# Workspaces
+
+## Overview
+
+Workspaces give your developers and AI agents a fully isolated, pre-configured development environment that is ready to use in seconds. No manual wiring, no maintenance, no security gaps.
+
+You shouldn't have to spend engineering time building and maintaining a secure dev environment for agents. Workspaces handle isolation, networking, auditing, tooling, and deployment out of the box. Your team ships faster, your agents operate safely, and your security team gets full visibility without any of it getting in the developer's way.
+
+Workspaces scale from a single developer running agents locally to enterprise teams with strict compliance requirements running on their own hardware. Security is always on by default, regardless of how you deploy.
+
+## Features
+
+### Environment & Isolation
+
+- **Full container/pod isolation** - each Workspace runs in its own sandboxed environment, completely separate from your host machine and other Workspaces
+- **Local sandbox deployment** - run and test code inside the Workspace without any manual setup or external deployment targets
+- **Authenticated preview URLs** - each Workspace can expose authenticated URLs for testing frontends, APIs, and services running inside the environment
+- **Automated setup** - each Workspace automatically runs your setup steps on creation (dependency installs, database migrations, seed data, file copies) so it's ready to use immediately
+- **Clean environment per session** - no state bleeds between Workspaces; every environment starts from a known, reproducible baseline
+- **Blast radius containment** - if an agent misbehaves or a dependency is compromised, the damage is contained to that Workspace and can't spread
+- **Configurable lifecycle** - Workspaces are ephemeral by default, but can be configured for persistence, session restore, or automatic reboot on failure
+
+### Security & Network Controls
+
+- **Prebuilt network controls** - network access is locked down by default; no outbound calls are made unless explicitly allowed
+- **Team-managed domain allowlists** - teams can pre-approve specific domains their agents are permitted to reach
+- **Platform pre-approved list** - a curated set of safe, commonly needed domains is included out of the box
+- **Full autonomy mode** - agents operate with broad permissions inside the Workspace while the environment's network and isolation controls keep everything contained; agents move fast, nothing leaks out
+- **Full machine-level audit logging** - every action taken inside a Workspace is logged at the infrastructure layer, always on, with no developer instrumentation required
+- **Credential & secret isolation** - environment variables and secrets are scoped to their Workspace and cannot leak across environments or be accessed by parallel agents
+
+### Access & Tooling
+
+- **VS Code extension** - create, manage, and connect to Workspaces directly from your editor
+- **Joggr app & web console** - manage and access Workspaces from the native Joggr application or web console
+- **Native, pre-wired tooling** - editors, terminals, language servers, and deployment targets are configured to work together from day one
+- **No glue code** - your sandbox, container, and repo are already connected; no custom wiring required
+- **Language and stack agnostic** - Workspaces support any language, framework, or monorepo structure
+- **Long-term platform maintenance** - integrations are maintained by the platform, not your team; no keeping up with upstream changes or broken setups after upgrades
+
+### Infrastructure as Code
+
+- **Workspace configuration as code** - define Workspace templates, resource limits, network policies, and tooling in version-controlled configuration files
+- **Reproducible environments** - every Workspace is created from a declared configuration, eliminating drift and snowflake setups
+- **Team and role management** - access controls and Workspace policies are defined in code and managed through a centralized console
+
+### Enterprise & Self-Hosted
+
+- **Run on your own hardware** - enterprise teams can deploy Workspaces on their own infrastructure, not a shared cloud environment
+- **Data residency control** - keep all code, secrets, and agent activity within your own network boundary
+- **Compliance-ready by default** - audit logs, network controls, and isolation are all in place without requiring custom security configuration
+- **Configurable resource limits** - CPU, memory, and disk are configurable per Workspace to match workload requirements
+- **Centralized console** - manage Workspaces, policies, and access across your organization from a single control plane
+
+### Agent-Specific Capabilities
+
+- **Designed for concurrent agents** - run multiple agents in parallel Workspaces with full isolation between them; no cross-contamination of state or credentials
+- **Agent action auditing** - know exactly what every agent did, in which Workspace, and when; critical for debugging, compliance, and trust
+- **Controlled autonomy** - agents can be given broad permissions to operate freely within a Workspace while remaining completely contained by the environment's security controls
+- **Reproducible agent environments** - every agent run starts from the same baseline, making agent behavior consistent and debuggable
+
+---
+
+## FAQ
+
+### How are Workspaces different from `--worktree` or existing worktree managers?
+
+Worktree managers give you multiple working copies of a repo. Workspaces give you a full, reproducible development environment with container isolation, automated setup, integrated tooling, and security on by default. A worktree is a directory. A Workspace is everything you need to start working, securely, from the moment it's created.
+
+### Does adding security controls mean a worse developer experience?
+
+No. Workspaces treat security as infrastructure, not workflow overhead. Network controls, action auditing, and isolation are on by default and handled by the platform. Developers and agents get full autonomy within the sandbox because the guardrails are at the infrastructure level, not in their way.
+
+Devs get the speed and freedom they want. Security teams get the controls and visibility they need.
+
+### Can I run agents in Workspaces without worrying about unsafe network calls?
+
+Yes. Network access is deny-by-default at the Workspace level. Teams pre-approve a domain allowlist, and the platform includes a curated set of commonly needed domains out of the box. Everything outside the allowlist is blocked.
+
+Agents can operate with broad autonomy while remaining fully contained by the network controls.
+
+### What is full autonomy mode?
+
+Full autonomy mode lets agents operate with broad permissions inside a Workspace without any manual approval steps. The agent can read, write, execute, and deploy freely within the environment. This is safe because the Workspace's network controls, credential isolation, and audit logging remain enforced at the infrastructure level regardless of what the agent does inside.
+
+### How do Workspaces help with security auditing and compliance?
+
+Every action taken inside a Workspace is logged at the machine level. You get a full audit trail of what any agent or developer did, when, and in which Workspace. All activity within the Workspace falls inside the audit boundary, and developers never have to instrument anything themselves. Logging happens at the infrastructure layer and is always on.
+
+### How are secrets provisioned into a Workspace?
+
+Secrets and credentials are injected into the Workspace environment at creation time, scoped to that Workspace only. They are not exposed to other environments or parallel agents. Secret provisioning is configured as part of the Workspace definition in code.
+
+### What happens when a Workspace crashes or an agent hangs?
+
+Workspaces handle failures based on your configuration. A crashed Workspace can be set to automatically reboot or restart cleanly from the baseline. A hanging agent can be terminated, with the Workspace restored to its last known state or restarted fresh. The specific behavior is defined in your Workspace configuration.
+
+### How do I manage Workspace access across teams and roles?
+
+Workspace policies, access controls, and role assignments are defined in version-controlled configuration files alongside your Workspace templates. The centralized console provides visibility into who has access to what and lets you manage policies across your organization. Changes to access are versioned and auditable like any other infrastructure change.
+
+### Why not just set this up myself with Docker, scripts, and a worktree manager?
+
+You can, but then you're responsible for maintaining it indefinitely.
+
+Rolling your own setup means building and maintaining isolation, networking, sandboxing, auditing, tooling integration, and deployment pipelines. Every time your stack evolves, every time agent behavior changes, every time a new developer joins, you're on the hook.
+
+DIY setups rarely get security right consistently. Network controls get misconfigured. Audit logging gets skipped. Credential scoping gets overlooked. Getting this right at the infrastructure level is genuinely hard.
+
+Workspaces handle all of this as an actively maintained solution so you get a secure agent dev environment without the ongoing engineering and security overhead.
+
+### Does this work for enterprise teams with strict infrastructure requirements?
+
+Yes. Enterprise teams can run Workspaces on their own hardware with full data residency control. Audit logs, network controls, isolation, and resource limits are all configurable. Whether your requirements include air-gapped networks, data sovereignty, or specific compliance frameworks, Workspaces are designed to run within your infrastructure constraints.
+
+### What does "natively integrated tooling" mean in practice?
+
+It means your editors, terminals, language servers, and deployment targets are built into the Workspace and configured to work together from day one. You don't need to connect your sandbox to your container to your repo manually. It's already wired up and ready to use.
diff --git a/docs/areas/workspaces.svg b/docs/areas/workspaces.svg
new file mode 100644
index 0000000..895b2ac
--- /dev/null
+++ b/docs/areas/workspaces.svg
@@ -0,0 +1,91 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1120 520">
+  <defs>
+    <style>
+      .text { font-family: 'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace; }
+      .code { font-family: 'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace; font-size: 12px; }
+      .tab { font-family: 'SF Mono', 'Fira Code', 'JetBrains Mono', Consolas, monospace; font-size: 11px; fill: #cdd6f4; }
+      .brand { fill: #a78bfa; }
+      .dim { fill: #6c7086; }
+      .st { fill: #a6e3a1; }
+      .tx { fill: #cdd6f4; }
+      .op { fill: #9399b2; }
+      .prompt { fill: #89b4fa; }
+      .warn { fill: #f9e2af; }
+      .fn { fill: #89b4fa; }
+      .peach { fill: #fab387; }
+    </style>
+  </defs>
+
+  <!-- Background -->
+  <rect width="1120" height="520" rx="10" ry="10" fill="#1e1e2e" />
+  <rect width="1120" height="36" rx="10" ry="10" fill="#181825" />
+  <rect y="26" width="1120" height="10" fill="#181825" />
+  <circle cx="20" cy="18" r="6" fill="#f38ba8" />
+  <circle cx="40" cy="18" r="6" fill="#f9e2af" />
+  <circle cx="60" cy="18" r="6" fill="#a6e3a1" />
+  <text class="text dim" font-size="12" x="560" y="22" text-anchor="middle">jog workspace</text>
+
+  <!-- Title -->
+  <text class="text brand" font-size="14" x="560" y="62" text-anchor="middle">jog workspace</text>
+  <text class="text dim" font-size="12" x="560" y="80" text-anchor="middle">create, manage, and attach to isolated dev environments</text>
+
+  <!-- Horizontal divider -->
+  <line x1="16" y1="96" x2="1104" y2="96" stroke="#313244" stroke-width="1" />
+  <!-- Vertical divider -->
+  <line x1="560" y1="96" x2="560" y2="510" stroke="#313244" stroke-width="1" />
+
+  <!-- Left panel: Containerized workspace -->
+  <rect x="4" y="104" width="110" height="24" rx="4" ry="4" fill="#181825" />
+  <text class="tab" x="14" y="120">containerized</text>
+
+  <text class="code" x="18" y="152"><tspan class="prompt">~</tspan><tspan class="dim"> $ </tspan><tspan class="tx">jog workspace create</tspan><tspan class="brand"> --container</tspan></text>
+  <text class="code" x="18" y="176"><tspan class="dim">  Resolving workspace config...</tspan></text>
+  <text class="code" x="18" y="198" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Found .joggr/workspace.yml</tspan></text>
+  <text class="code" x="18" y="214" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Pulled image </tspan><tspan class="fn">joggr/workspace:latest</tspan></text>
+
+  <text class="code" x="18" y="238"><tspan class="dim">  Building container...</tspan></text>
+  <text class="code" x="18" y="260" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Mounted repo at </tspan><tspan class="fn">/workspace</tspan></text>
+  <text class="code" x="18" y="276" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Installed toolchain (node, pnpm)</tspan></text>
+  <text class="code" x="18" y="292" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Injected agent context</tspan></text>
+  <text class="code" x="18" y="308" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Applied CLAUDE.md + rules</tspan></text>
+
+  <text class="code" x="18" y="332"><tspan class="dim">  Running setup hooks...</tspan></text>
+  <text class="code" x="18" y="354" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> pnpm install </tspan><tspan class="dim">(2.1s)</tspan></text>
+  <text class="code" x="18" y="370" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> db:migrate </tspan><tspan class="dim">(0.8s)</tspan></text>
+  <text class="code" x="18" y="386" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> seed:dev </tspan><tspan class="dim">(1.3s)</tspan></text>
+
+  <text class="code" x="18" y="414"><tspan class="peach">  &#x25CF;</tspan><tspan class="tx"> Container </tspan><tspan class="st">running</tspan><tspan class="dim"> (docker://jog-abc123)</tspan></text>
+  <text class="code" x="18" y="434" xml:space="preserve"><tspan class="dim">    ports: </tspan><tspan class="tx">3000, 5432, 6379</tspan></text>
+  <text class="code" x="18" y="454" xml:space="preserve"><tspan class="dim">    agents: </tspan><tspan class="tx">claude-code, cursor</tspan></text>
+
+  <text class="code" x="18" y="482"><tspan class="dim">  Workspace ready </tspan><tspan class="fn">&#x2192;</tspan><tspan class="tx"> jog workspace shell</tspan></text>
+  <text class="code" x="18" y="504"><tspan class="prompt">~</tspan><tspan class="dim"> $ </tspan><tspan class="tx">&#x2588;</tspan></text>
+
+  <!-- Right panel: Remote workspace -->
+  <rect x="564" y="104" width="80" height="24" rx="4" ry="4" fill="#181825" />
+  <text class="tab" x="578" y="120">remote</text>
+
+  <text class="code" x="578" y="152"><tspan class="prompt">~</tspan><tspan class="dim"> $ </tspan><tspan class="tx">jog workspace create</tspan><tspan class="brand"> --remote</tspan></text>
+  <text class="code" x="578" y="176"><tspan class="dim">  Resolving workspace config...</tspan></text>
+  <text class="code" x="578" y="198" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Found .joggr/workspace.yml</tspan></text>
+  <text class="code" x="578" y="214" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Authenticated with joggr.gg</tspan></text>
+
+  <text class="code" x="578" y="238"><tspan class="dim">  Provisioning remote instance...</tspan></text>
+  <text class="code" x="578" y="260" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Region </tspan><tspan class="fn">us-east-1</tspan><tspan class="dim"> (auto-detected)</tspan></text>
+  <text class="code" x="578" y="276" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Instance </tspan><tspan class="fn">dev-md</tspan><tspan class="dim"> (8 vCPU, 16 GB)</tspan></text>
+  <text class="code" x="578" y="292" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Cloned repo + checked out </tspan><tspan class="fn">main</tspan></text>
+  <text class="code" x="578" y="308" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> Synced agent context + secrets</tspan></text>
+
+  <text class="code" x="578" y="332"><tspan class="dim">  Running setup hooks...</tspan></text>
+  <text class="code" x="578" y="354" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> pnpm install </tspan><tspan class="dim">(1.4s)</tspan></text>
+  <text class="code" x="578" y="370" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> db:migrate </tspan><tspan class="dim">(0.5s)</tspan></text>
+  <text class="code" x="578" y="386" xml:space="preserve"><tspan class="st">  &#x2713;</tspan><tspan class="tx"> seed:dev </tspan><tspan class="dim">(0.9s)</tspan></text>
+
+  <text class="code" x="578" y="414"><tspan class="peach">  &#x25CF;</tspan><tspan class="tx"> Remote </tspan><tspan class="st">running</tspan><tspan class="dim"> (ssh://jog-xyz789.joggr.gg)</tspan></text>
+  <text class="code" x="578" y="434" xml:space="preserve"><tspan class="dim">    url: </tspan><tspan class="fn">https://jog-xyz789.joggr.gg</tspan></text>
+  <text class="code" x="578" y="454" xml:space="preserve"><tspan class="dim">    agents: </tspan><tspan class="tx">claude-code, cursor</tspan></text>
+
+  <text class="code" x="578" y="482"><tspan class="dim">  Workspace ready </tspan><tspan class="fn">&#x2192;</tspan><tspan class="tx"> jog workspace attach</tspan></text>
+  <text class="code" x="578" y="504"><tspan class="prompt">~</tspan><tspan class="dim"> $ </tspan><tspan class="tx">&#x2588;</tspan></text>
+
+</svg>
\ No newline at end of file