create-agentic-app 1.1.52 → 1.1.54

package/template/.claude/commands/publish-to-github.md

@@ -1,304 +0,0 @@
----
-description: Publish a feature from /specs to GitHub Issues and Projects
----
-
-# Publish Feature to GitHub
-
-This command publishes a feature from the /specs folder to GitHub, creating:
-
-- An Epic issue containing the full requirements
-- Phase issues for each phase in the implementation plan (with task checklists)
-- A GitHub Project to track progress
-- Labels for organization
-- A `github.md` file in the specs folder with all references
-
-## Prerequisites
-
-- The GitHub CLI (`gh`) must be authenticated: `gh auth status`
-- The GitHub CLI must have project scopes: Token scopes should include `project` and `read:project`. If missing, run: `gh auth refresh -s project,read:project`
-- A feature folder must exist in /specs with `requirements.md` and `implementation-plan.md`
-
-## Instructions
-
-### 1. Identify the Feature
-
-Look for the feature folder attached to the conversation or specified by the user.
-The folder should be at `/specs/{feature-name}/` and contain:
-
-- `requirements.md` - Feature requirements
-- `implementation-plan.md` - Task breakdown with phases
-
-If no folder is specified, ask the user which feature to publish.
-
-### 2. Extract Feature Information
-
-- **Feature name**: Use the folder name (e.g., `answer-scoring`)
-- **Feature title**: Parse the main heading from `requirements.md`
-- **Phases**: Parse all phases from `implementation-plan.md`, including phase title, description, and task checklists
-
-### 3. Get Repository Information
-
-Run: `gh repo view --json nameWithOwner,owner -q '.nameWithOwner + " " + .owner.login'`
-
-This returns both values, e.g., `leonvanzyl/json-anything leonvanzyl`
-
-Store the results as:
-
-- `{repository}` - Full repo name (e.g., `leonvanzyl/json-anything`)
-- `{owner}` - Repository owner (e.g., `leonvanzyl`)
-
-### 4. Create Labels (if they don't exist)
-
-```bash
-gh label create "epic" --color "7057ff" --description "Feature epic" 2>/dev/null || true
-gh label create "feature/{feature-name}" --color "0E8A16" --description "Feature: {feature-title}" 2>/dev/null || true
-gh label create "phase-1" --color "C5DEF5" --description "Phase 1 tasks" 2>/dev/null || true
-gh label create "phase-2" --color "BFD4F2" --description "Phase 2 tasks" 2>/dev/null || true
-gh label create "phase-3" --color "A2C4E0" --description "Phase 3 tasks" 2>/dev/null || true
-```
-
-### 5. Create the Epic Issue
-
-Create an Epic issue with the full requirements:
-
-```bash
-gh issue create \
-  --title "Epic: {Feature Title}" \
-  --label "epic" \
-  --label "feature/{feature-name}" \
-  --body-file specs/{feature-name}/requirements.md
-```
-
-Capture the issue number from the output (e.g., `#100`).
-
-### 6. Create Phase Issues
-
-For each phase in the implementation plan, create an issue containing all tasks for that phase:
-
-**Issue body template:**
-
-```markdown
-## Context
-
-Part of Epic: #{epic-number}
-
-## Overview
-
-{Phase description/focus from implementation plan}
-
-## Tasks
-
-{Copy the full task checklist from the implementation plan for this phase, preserving markdown checkboxes}
-
-## Technical Details
-
-[Copy the full technical details section from the implementation plan for this phase]
-
-## Acceptance Criteria
-
-- [ ] All tasks in this phase completed
-- [ ] Code passes lint and typecheck
-- [ ] Changes follow project conventions
-```
-
-**Command:**
-
-```bash
-gh issue create \
-  --title "Phase {n}: {Phase Title}" \
-  --label "feature/{feature-name}" \
-  --label "phase-{n}" \
-  --body "{issue-body}"
-```
-
-Capture each phase issue number for linking.
-
-### 6a. Handle Complex Phases (Optional)
-
-If a phase meets any of these criteria, consider breaking out individual tasks as separate issues:
-
-- Phase has **more than 15 tasks**
-- A task has **nested sub-tasks** (indented checkboxes)
-- A task is marked with `[complex]` in the implementation plan
-
-**For complex phases:**
-
-1. Create the phase issue as normal (it becomes the parent)
-2. For each complex task, create a separate task issue:
-
-```bash
-gh issue create \
-  --title "{Task description}" \
-  --label "feature/{feature-name}" \
-  --label "phase-{n}" \
-  --body "## Context
-
-Part of Phase: #{phase-issue-number}
-Part of Epic: #{epic-number}
-
-## Task
-
-{Task description with any sub-tasks}
-
-## Acceptance Criteria
-
-- [ ] Implementation complete
-- [ ] Code passes lint and typecheck
-- [ ] Changes follow project conventions"
-```
-
-3. Update the phase issue to replace the task checkbox with a linked issue reference:
-
-**Before:**
-
-```markdown
-- [ ] Create complex authentication system [complex]
-```
-
-**After:**
-
-```markdown
-- [ ] #{task-issue-number} Create complex authentication system
-```
-
-This way the phase issue still tracks all work, but complex tasks get their own issue for detailed discussion and tracking.
-
-### 7. Update Epic with Phase List
-
-Edit the Epic issue to include a list linking all phase issues:
-
-```bash
-gh issue edit {epic-number} --body "{original-body}
-
----
-
-## Phases
-
-- [ ] #{phase-1-number} Phase 1: {Phase 1 Title}
-- [ ] #{phase-2-number} Phase 2: {Phase 2 Title}
-- [ ] #{phase-3-number} Phase 3: {Phase 3 Title}
-...
-"
-```
-
-### 8. Create GitHub Project and Link to Repository
-
-Create the project under the repository owner:
-
-```bash
-gh project create --title "Feature: {Feature Title}" --owner {owner}
-```
-
-Note: If the project already exists or the user prefers to use an existing project, skip this step. You can list projects with: `gh project list --owner {owner}`
-
-Capture the project number from the output (you may need to run `gh project list --owner {owner}` to get it).
-
-Then link the project to the repository so it appears in the repo's Projects tab:
-
-```bash
-gh project link {project-number} --owner {owner} --repo {repository}
-```
-
-### 9. Add Issues to Project
-
-```bash
-gh project item-add {project-number} --owner {owner} --url "https://github.com/{repository}/issues/{epic-number}"
-gh project item-add {project-number} --owner {owner} --url "https://github.com/{repository}/issues/{phase-1-number}"
-# ... repeat for all phase issues
-# ... also add any complex task issues that were broken out
-```
-
-### 10. Create github.md
-
-Create `specs/{feature-name}/github.md` with all the GitHub references:
-
-```markdown
----
-feature_name: { feature-name }
-feature_title: { Feature Title }
-repository: { repository }
-epic_issue: { epic-number }
-project_number: { project-number }
-labels:
-  - epic
-  - feature/{feature-name}
-published_at: { current-date }
----
-
-# GitHub References
-
-This feature has been published to GitHub.
-
-## Links
-
-- [Epic Issue](https://github.com/{repository}/issues/{epic-number})
-- [Project Board](https://github.com/users/{owner}/projects/{project-number}) (also linked to repository)
-
-## Phase Issues
-
-| #          | Title                    | Tasks | Status |
-| ---------- | ------------------------ | ----- | ------ |
-| #{phase-1} | Phase 1: {Phase 1 Title} | {n}   | Open   |
-| #{phase-2} | Phase 2: {Phase 2 Title} | {n}   | Open   |
-| ...        | ...                      | ...   | ...    |
-
-## Complex Task Issues (if any)
-
-| #         | Title        | Phase | Status |
-| --------- | ------------ | ----- | ------ |
-| #{task-1} | {Task title} | 1     | Open   |
-| ...       | ...          | ...   | ...    |
-
-_(Omit this section if no complex tasks were broken out)_
-
-## Labels
-
-- `epic` - Feature epic marker
-- `feature/{feature-name}` - Feature-specific label
-- `phase-1`, `phase-2`, `phase-3` - Phase markers
-```
-
-### 11. Report Summary
-
-After completion, report:
-
-- Epic issue URL
-- Number of phase issues created
-- Number of complex task issues created (if any)
-- Total number of tasks across all phases
-- Project board URL
-- Location of github.md file
-
-Example output:
-
-```
-Feature "{Feature Title}" published to GitHub!
-
-Epic: https://github.com/{repository}/issues/{epic-number}
-Project: https://github.com/users/{owner}/projects/{project-number} (linked to repo)
-Phases created: 4
-Complex task issues: 2 (optional, only if any were created)
-Total tasks: 46
-
-The github.md file has been created at specs/{feature-name}/github.md
-
-To continue implementing, drag the specs/{feature-name}/ folder into a new conversation
-and say "continue with this feature" or use /continue-feature.
-```
-
-## Error Handling
-
-- If `gh auth status` fails, inform user to run `gh auth login`
-- If project creation fails with "missing required scopes [project read:project]", inform user to run `gh auth refresh -s project,read:project`
-- If the feature folder doesn't exist, ask user to run `/create-feature` first
-- If labels/issues fail to create, report the error and continue with remaining items
-- If github.md already exists, ask user if they want to overwrite or update it
-
-## Notes
-
-- Each phase issue contains the full task checklist from the implementation plan
-- Tasks within a phase issue can be checked off as they're completed
-- Phases should be executed sequentially (Phase 1 → Phase 2 → Phase 3, etc.)
-- The Epic provides a high-level view with links to all phase issues
-- Use the `[complex]` marker in implementation plans to flag tasks that need their own issue
-- When breaking out complex tasks, the phase issue remains the parent tracker

package/template/.claude/skills/brainstorming/SKILL.md

@@ -1,164 +0,0 @@
----
-name: brainstorming
-description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
----
-
-# Brainstorming Ideas Into Designs
-
-Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
-
-Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
-
-<HARD-GATE>
-Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
-</HARD-GATE>
-
-## Anti-Pattern: "This Is Too Simple To Need A Design"
-
-Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
-
-## Checklist
-
-You MUST create a task for each of these items and complete them in order:
-
-1. **Explore project context** — check files, docs, recent commits
-2. **Offer visual companion** (if topic will involve visual questions) — this is its own message, not combined with a clarifying question. See the Visual Companion section below.
-3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
-4. **Propose 2-3 approaches** — with trade-offs and your recommendation
-5. **Present design** — in sections scaled to their complexity, get user approval after each section
-6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit
-7. **Spec self-review** — quick inline check for placeholders, contradictions, ambiguity, scope (see below)
-8. **User reviews written spec** — ask user to review the spec file before proceeding
-9. **Transition to implementation** — invoke writing-plans skill to create implementation plan
-
-## Process Flow
-
-```dot
-digraph brainstorming {
-    "Explore project context" [shape=box];
-    "Visual questions ahead?" [shape=diamond];
-    "Offer Visual Companion\n(own message, no other content)" [shape=box];
-    "Ask clarifying questions" [shape=box];
-    "Propose 2-3 approaches" [shape=box];
-    "Present design sections" [shape=box];
-    "User approves design?" [shape=diamond];
-    "Write design doc" [shape=box];
-    "Spec self-review\n(fix inline)" [shape=box];
-    "User reviews spec?" [shape=diamond];
-    "Invoke writing-plans skill" [shape=doublecircle];
-
-    "Explore project context" -> "Visual questions ahead?";
-    "Visual questions ahead?" -> "Offer Visual Companion\n(own message, no other content)" [label="yes"];
-    "Visual questions ahead?" -> "Ask clarifying questions" [label="no"];
-    "Offer Visual Companion\n(own message, no other content)" -> "Ask clarifying questions";
-    "Ask clarifying questions" -> "Propose 2-3 approaches";
-    "Propose 2-3 approaches" -> "Present design sections";
-    "Present design sections" -> "User approves design?";
-    "User approves design?" -> "Present design sections" [label="no, revise"];
-    "User approves design?" -> "Write design doc" [label="yes"];
-    "Write design doc" -> "Spec self-review\n(fix inline)";
-    "Spec self-review\n(fix inline)" -> "User reviews spec?";
-    "User reviews spec?" -> "Write design doc" [label="changes requested"];
-    "User reviews spec?" -> "Invoke writing-plans skill" [label="approved"];
-}
-```
-
-**The terminal state is invoking writing-plans.** Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.
-
-## The Process
-
-**Understanding the idea:**
-
-- Check out the current project state first (files, docs, recent commits)
-- Before asking detailed questions, assess scope: if the request describes multiple independent subsystems (e.g., "build a platform with chat, file storage, billing, and analytics"), flag this immediately. Don't spend questions refining details of a project that needs to be decomposed first.
-- If the project is too large for a single spec, help the user decompose into sub-projects: what are the independent pieces, how do they relate, what order should they be built? Then brainstorm the first sub-project through the normal design flow. Each sub-project gets its own spec → plan → implementation cycle.
-- For appropriately-scoped projects, ask questions one at a time to refine the idea
-- Prefer multiple choice questions when possible, but open-ended is fine too
-- Only one question per message - if a topic needs more exploration, break it into multiple questions
-- Focus on understanding: purpose, constraints, success criteria
-
-**Exploring approaches:**
-
-- Propose 2-3 different approaches with trade-offs
-- Present options conversationally with your recommendation and reasoning
-- Lead with your recommended option and explain why
-
-**Presenting the design:**
-
-- Once you believe you understand what you're building, present the design
-- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
-- Ask after each section whether it looks right so far
-- Cover: architecture, components, data flow, error handling, testing
-- Be ready to go back and clarify if something doesn't make sense
-
-**Design for isolation and clarity:**
-
-- Break the system into smaller units that each have one clear purpose, communicate through well-defined interfaces, and can be understood and tested independently
-- For each unit, you should be able to answer: what does it do, how do you use it, and what does it depend on?
-- Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work.
-- Smaller, well-bounded units are also easier for you to work with - you reason better about code you can hold in context at once, and your edits are more reliable when files are focused. When a file grows large, that's often a signal that it's doing too much.
-
-**Working in existing codebases:**
-
-- Explore the current structure before proposing changes. Follow existing patterns.
-- Where existing code has problems that affect the work (e.g., a file that's grown too large, unclear boundaries, tangled responsibilities), include targeted improvements as part of the design - the way a good developer improves code they're working in.
-- Don't propose unrelated refactoring. Stay focused on what serves the current goal.
-
-## After the Design
-
-**Documentation:**
-
-- Write the validated design (spec) to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
-  - (User preferences for spec location override this default)
-- Use elements-of-style:writing-clearly-and-concisely skill if available
-- Commit the design document to git
-
-**Spec Self-Review:**
-After writing the spec document, look at it with fresh eyes:
-
-1. **Placeholder scan:** Any "TBD", "TODO", incomplete sections, or vague requirements? Fix them.
-2. **Internal consistency:** Do any sections contradict each other? Does the architecture match the feature descriptions?
-3. **Scope check:** Is this focused enough for a single implementation plan, or does it need decomposition?
-4. **Ambiguity check:** Could any requirement be interpreted two different ways? If so, pick one and make it explicit.
-
-Fix any issues inline. No need to re-review — just fix and move on.
-
-**User Review Gate:**
-After the spec review loop passes, ask the user to review the written spec before proceeding:
-
-> "Spec written and committed to `<path>`. Please review it and let me know if you want to make any changes before we start writing out the implementation plan."
-
-Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves.
-
-**Implementation:**
-
-- Invoke the writing-plans skill to create a detailed implementation plan
-- Do NOT invoke any other skill. writing-plans is the next step.
-
-## Key Principles
-
-- **One question at a time** - Don't overwhelm with multiple questions
-- **Multiple choice preferred** - Easier to answer than open-ended when possible
-- **YAGNI ruthlessly** - Remove unnecessary features from all designs
-- **Explore alternatives** - Always propose 2-3 approaches before settling
-- **Incremental validation** - Present design, get approval before moving on
-- **Be flexible** - Go back and clarify when something doesn't make sense
-
-## Visual Companion
-
-A browser-based companion for showing mockups, diagrams, and visual options during brainstorming. Available as a tool — not a mode. Accepting the companion means it's available for questions that benefit from visual treatment; it does NOT mean every question goes through the browser.
-
-**Offering the companion:** When you anticipate that upcoming questions will involve visual content (mockups, layouts, diagrams), offer it once for consent:
-> "Some of what we're working on might be easier to explain if I can show it to you in a web browser. I can put together mockups, diagrams, comparisons, and other visuals as we go. This feature is still new and can be token-intensive. Want to try it? (Requires opening a local URL)"
-
-**This offer MUST be its own message.** Do not combine it with clarifying questions, context summaries, or any other content. The message should contain ONLY the offer above and nothing else. Wait for the user's response before continuing. If they decline, proceed with text-only brainstorming.
-
-**Per-question decision:** Even after the user accepts, decide FOR EACH QUESTION whether to use the browser or the terminal. The test: **would the user understand this better by seeing it than reading it?**
-
-- **Use the browser** for content that IS visual — mockups, wireframes, layout comparisons, architecture diagrams, side-by-side visual designs
-- **Use the terminal** for content that is text — requirements questions, conceptual choices, tradeoff lists, A/B/C/D text options, scope decisions
-
-A question about a UI topic is not automatically a visual question. "What does personality mean in this context?" is a conceptual question — use the terminal. "Which wizard layout works better?" is a visual question — use the browser.
-
-If they agree to the companion, read the detailed guide before proceeding:
-`skills/brainstorming/visual-companion.md`

package/template/.claude/skills/brainstorming/scripts/frame-template.html

@@ -1,214 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <meta charset="utf-8">
-  <title>Superpowers Brainstorming</title>
-  <style>
-    /*
-     * BRAINSTORM COMPANION FRAME TEMPLATE
-     *
-     * This template provides a consistent frame with:
-     * - OS-aware light/dark theming
-     * - Fixed header and selection indicator bar
-     * - Scrollable main content area
-     * - CSS helpers for common UI patterns
-     *
-     * Content is injected via placeholder comment in #claude-content.
-     */
-
-    * { box-sizing: border-box; margin: 0; padding: 0; }
-    html, body { height: 100%; overflow: hidden; }
-
-    /* ===== THEME VARIABLES ===== */
-    :root {
-      --bg-primary: #f5f5f7;
-      --bg-secondary: #ffffff;
-      --bg-tertiary: #e5e5e7;
-      --border: #d1d1d6;
-      --text-primary: #1d1d1f;
-      --text-secondary: #86868b;
-      --text-tertiary: #aeaeb2;
-      --accent: #0071e3;
-      --accent-hover: #0077ed;
-      --success: #34c759;
-      --warning: #ff9f0a;
-      --error: #ff3b30;
-      --selected-bg: #e8f4fd;
-      --selected-border: #0071e3;
-    }
-
-    @media (prefers-color-scheme: dark) {
-      :root {
-        --bg-primary: #1d1d1f;
-        --bg-secondary: #2d2d2f;
-        --bg-tertiary: #3d3d3f;
-        --border: #424245;
-        --text-primary: #f5f5f7;
-        --text-secondary: #86868b;
-        --text-tertiary: #636366;
-        --accent: #0a84ff;
-        --accent-hover: #409cff;
-        --selected-bg: rgba(10, 132, 255, 0.15);
-        --selected-border: #0a84ff;
-      }
-    }
-
-    body {
-      font-family: system-ui, -apple-system, BlinkMacSystemFont, sans-serif;
-      background: var(--bg-primary);
-      color: var(--text-primary);
-      display: flex;
-      flex-direction: column;
-      line-height: 1.5;
-    }
-
-    /* ===== FRAME STRUCTURE ===== */
-    .header {
-      background: var(--bg-secondary);
-      padding: 0.5rem 1.5rem;
-      display: flex;
-      justify-content: space-between;
-      align-items: center;
-      border-bottom: 1px solid var(--border);
-      flex-shrink: 0;
-    }
-    .header h1 { font-size: 0.85rem; font-weight: 500; color: var(--text-secondary); }
-    .header .status { font-size: 0.7rem; color: var(--success); display: flex; align-items: center; gap: 0.4rem; }
-    .header .status::before { content: ''; width: 6px; height: 6px; background: var(--success); border-radius: 50%; }
-
-    .main { flex: 1; overflow-y: auto; }
-    #claude-content { padding: 2rem; min-height: 100%; }
-
-    .indicator-bar {
-      background: var(--bg-secondary);
-      border-top: 1px solid var(--border);
-      padding: 0.5rem 1.5rem;
-      flex-shrink: 0;
-      text-align: center;
-    }
-    .indicator-bar span {
-      font-size: 0.75rem;
-      color: var(--text-secondary);
-    }
-    .indicator-bar .selected-text {
-      color: var(--accent);
-      font-weight: 500;
-    }
-
-    /* ===== TYPOGRAPHY ===== */
-    h2 { font-size: 1.5rem; font-weight: 600; margin-bottom: 0.5rem; }
-    h3 { font-size: 1.1rem; font-weight: 600; margin-bottom: 0.25rem; }
-    .subtitle { color: var(--text-secondary); margin-bottom: 1.5rem; }
-    .section { margin-bottom: 2rem; }
-    .label { font-size: 0.7rem; color: var(--text-secondary); text-transform: uppercase; letter-spacing: 0.05em; margin-bottom: 0.5rem; }
-
-    /* ===== OPTIONS (for A/B/C choices) ===== */
-    .options { display: flex; flex-direction: column; gap: 0.75rem; }
-    .option {
-      background: var(--bg-secondary);
-      border: 2px solid var(--border);
-      border-radius: 12px;
-      padding: 1rem 1.25rem;
-      cursor: pointer;
-      transition: all 0.15s ease;
-      display: flex;
-      align-items: flex-start;
-      gap: 1rem;
-    }
-    .option:hover { border-color: var(--accent); }
-    .option.selected { background: var(--selected-bg); border-color: var(--selected-border); }
-    .option .letter {
-      background: var(--bg-tertiary);
-      color: var(--text-secondary);
-      width: 1.75rem; height: 1.75rem;
-      border-radius: 6px;
-      display: flex; align-items: center; justify-content: center;
-      font-weight: 600; font-size: 0.85rem; flex-shrink: 0;
-    }
-    .option.selected .letter { background: var(--accent); color: white; }
-    .option .content { flex: 1; }
-    .option .content h3 { font-size: 0.95rem; margin-bottom: 0.15rem; }
-    .option .content p { color: var(--text-secondary); font-size: 0.85rem; margin: 0; }
-
-    /* ===== CARDS (for showing designs/mockups) ===== */
-    .cards { display: grid; grid-template-columns: repeat(auto-fit, minmax(280px, 1fr)); gap: 1rem; }
-    .card {
-      background: var(--bg-secondary);
-      border: 1px solid var(--border);
-      border-radius: 12px;
-      overflow: hidden;
-      cursor: pointer;
-      transition: all 0.15s ease;
-    }
-    .card:hover { border-color: var(--accent); transform: translateY(-2px); box-shadow: 0 4px 12px rgba(0,0,0,0.1); }
-    .card.selected { border-color: var(--selected-border); border-width: 2px; }
-    .card-image { background: var(--bg-tertiary); aspect-ratio: 16/10; display: flex; align-items: center; justify-content: center; }
-    .card-body { padding: 1rem; }
-    .card-body h3 { margin-bottom: 0.25rem; }
-    .card-body p { color: var(--text-secondary); font-size: 0.85rem; }
-
-    /* ===== MOCKUP CONTAINER ===== */
-    .mockup {
-      background: var(--bg-secondary);
-      border: 1px solid var(--border);
-      border-radius: 12px;
-      overflow: hidden;
-      margin-bottom: 1.5rem;
-    }
-    .mockup-header {
-      background: var(--bg-tertiary);
-      padding: 0.5rem 1rem;
-      font-size: 0.75rem;
-      color: var(--text-secondary);
-      border-bottom: 1px solid var(--border);
-    }
-    .mockup-body { padding: 1.5rem; }
-
-    /* ===== SPLIT VIEW (side-by-side comparison) ===== */
-    .split { display: grid; grid-template-columns: 1fr 1fr; gap: 1.5rem; }
-    @media (max-width: 700px) { .split { grid-template-columns: 1fr; } }
-
-    /* ===== PROS/CONS ===== */
-    .pros-cons { display: grid; grid-template-columns: 1fr 1fr; gap: 1rem; margin: 1rem 0; }
-    .pros, .cons { background: var(--bg-secondary); border-radius: 8px; padding: 1rem; }
-    .pros h4 { color: var(--success); font-size: 0.85rem; margin-bottom: 0.5rem; }
-    .cons h4 { color: var(--error); font-size: 0.85rem; margin-bottom: 0.5rem; }
-    .pros ul, .cons ul { margin-left: 1.25rem; font-size: 0.85rem; color: var(--text-secondary); }
-    .pros li, .cons li { margin-bottom: 0.25rem; }
-
-    /* ===== PLACEHOLDER (for mockup areas) ===== */
-    .placeholder {
-      background: var(--bg-tertiary);
-      border: 2px dashed var(--border);
-      border-radius: 8px;
-      padding: 2rem;
-      text-align: center;
-      color: var(--text-tertiary);
-    }
-
-    /* ===== INLINE MOCKUP ELEMENTS ===== */
-    .mock-nav { background: var(--accent); color: white; padding: 0.75rem 1rem; display: flex; gap: 1.5rem; font-size: 0.9rem; }
-    .mock-sidebar { background: var(--bg-tertiary); padding: 1rem; min-width: 180px; }
-    .mock-content { padding: 1.5rem; flex: 1; }
-    .mock-button { background: var(--accent); color: white; border: none; padding: 0.5rem 1rem; border-radius: 6px; font-size: 0.85rem; }
-    .mock-input { background: var(--bg-primary); border: 1px solid var(--border); border-radius: 6px; padding: 0.5rem; width: 100%; }
-  </style>
-</head>
-<body>
-  <div class="header">
-    <h1><a href="https://github.com/obra/superpowers" style="color: inherit; text-decoration: none;">Superpowers Brainstorming</a></h1>
-    <div class="status">Connected</div>
-  </div>
-
-  <div class="main">
-    <div id="claude-content">
-      <!-- CONTENT -->
-    </div>
-  </div>
-
-  <div class="indicator-bar">
-    <span id="indicator-text">Click an option above, then return to the terminal</span>
-  </div>
-
-</body>
-</html>