📐 supersite-plan: Collaborative Architect
supersite-plan plans the website before writing code. It prevents misaligned expectations by conducting a focused interview, establishing the design system, drafting the narrative sequence, and producing a complete supersite-plan.md project contract.
Once the plan is confirmed, the user simply runs /supersite-build to execute it.
The Collaborative Planning Flow
┌─────────────────────────────────────────────────────────────┐
│ 1. Multi-Dimensional Discovery Interview │
│ Ask structured frontier questions (Options + Custom Prompt) │
├─────────────────────────────────────────────────────────────┤
│ 2. Design Token & Genre Syntheses │
│ Map selections to 60-30-10 palette, typography & materials │
├─────────────────────────────────────────────────────────────┤
│ 3. Narrative & Route Architecture │
│ Detail section sequence, headlines, and component breakdown │
├─────────────────────────────────────────────────────────────┤
│ 4. Output supersite-plan.md Specification Contract │
│ Persist full architecture for execution by /supersite-build │
└─────────────────────────────────────────────────────────────┘
Step 1: The Frontier Discovery Interview
Ask the user a set of targeted questions. For each question, provide structured options with a recommended default, while explicitly welcoming custom instructions.
Question Pattern:
Question [N]: [Topic]
[A] (Recommended) Option 1 description
[B] Option 2 description
[C] Option 3 description
👉 Reply with an option letter (A, B, C) or type your own specific instructions directly.
The Zero Em-Dash Rule (Mandatory)
When asking questions, phrasing options, formulating copy, or replying to the user, NEVER use an em-dash (— or --). Em-dashes make interview questions and choices feel like synthetic AI boilerplate. Break thoughts into clean, confident sentences, or use colons, commas, or parentheses instead.
The 4 Discovery Areas:
1. Site Scope & Route Hierarchy
- [A] (Recommended) High-Conversion Landing Page: Single-page narrative scroll optimized for maximum conversion velocity (Hero → Problem → Product Preview → Proof → Pricing → CTA).
- [B] Multi-Page SaaS Architecture: Multi-route structure (
/Home,/featuresDeep Dive,/pricingMatrix & FAQ,/securityCompliance). - [C] Studio Portfolio & Case Studies: Visual showcase (
/Showreel,/work/[slug]Interactive Case Studies,/inquireContact Form).
2. Aesthetic Genre & Material Foundation
- [A] (Recommended) Dark Precision: Obsidian surfaces (
#09090b), hairline borders (border-white/10), monospace telemetry, laser emerald or cyan accent. - [B] Quiet Luxury: Tactile ivory canvas (
#faf8f5), deep forest green ink (#0c2217), champagne gold details, editorial serif headings. - [C] Swiss Editorial: Broadsheet newsprint paper, solid 1px black divider grids, vermillion signal accents, bold grotesque/serif contrast.
- [D] Modern Enterprise: Crisp white surfaces, deep navy blue trust accents, SOC2/HIPAA compliance ribbons, dense comparison tables.
- [E] Bold Consumer: Warm cream canvas, 2.5px solid ink borders, hard offset drop shadows, punchy neon accents, playful microcopy.
- [F] Cinematic Studio: Full-viewport dark theater stage, ambient backdrop vignette, live product showcase, scroll-driven scene markers.
3. Core Capability & Contrast
- What specific friction or broken status quo does this product eliminate?
- What concrete, quantifiable metric proves your superiority (e.g. "Sub-14ms cold starts", "Zero AWS egress markups" vs. generic "Lightning fast")?
4. Codebase Relationship
- [A] (Recommended) Greenfield Clean Build: New project using standard Next.js, React, Tailwind CSS, and Lucide icons.
- [B] Inherit from Existing Codebase (
from-codebase): Inspect local repository (globals.css, Tailwind tokens,package.json) to match existing product branding.
Step 2: Synthesize the Project Contract
Once the user provides their answers or instructions:
- Load the corresponding genre blueprint from
../supersite/references/genres/. - Apply the anti-slop rules from
../supersite/references/anti-slop.md. - Draft authentic, high-status headlines and copy using
../supersite/references/copy-craft.md. - Define the composable component breakdown based on
../supersite/references/component-system.md. - Enforce the Zero Em-Dash Rule: ensure
supersite-plan.mdcontains zero em-dashes (—or--) in its descriptions, section blueprints, headlines, and microcopy.
Step 3: Write supersite-plan.md
Persist the agreed architecture into supersite-plan.md in the project root:
# ⚡ supersite Specification Contract: [Project Name]
> Generated by `/supersite-plan`. Execute with `/supersite-build`.
## 1. Project Overview & Target Audience
* **Product:** [Concise product description]
* **Target Audience:** [Specific role, e.g., Senior Infrastructure Engineers]
* **Primary Conversion Goal:** [e.g., Deploy free staging cluster / Book enterprise demo]
## 2. Design System Tokens
* **Aesthetic Genre:** [e.g., Dark Precision]
* **60-30-10 Palette:**
* 60% Canvas: `#09090b` (Obsidian)
* 30% Structural: `#121317` (Panels) / `#27272a` (Hairline Borders) / `#fafafa` (Ink)
* 10% Laser Accent: `#10b981` (Electric Emerald)
* **Typography:** Display (`Geist Sans`), Telemetry (`Geist Mono`)
* **Corner Radius:** `rounded-lg` (8px for buttons, 12px for cards)
## 3. Site Navigation & Route Hierarchy
* Route 1: `/` (Home conversion narrative)
* Route 2: `/features` (Architecture & API deep dive)
* Route 3: `/pricing` (Interactive tier matrix & FAQ)
## 4. Section-by-Section Blueprint
* **Navbar:** Sticky frosted glass header (`backdrop-blur-md`), logo, links, primary CTA.
* **Section 1 (Hero):**
* Pill: `v2.4 RELEASE // DISTRIBUTED VECTOR CACHE`
* Headline: *"Deploy serverless vector indexing with 12ms global read replicas."*
* Subhead: *"Store embeddings at the edge. Automatic sync across 32 regions with zero egress markups."*
* CTA: *"Deploy Cluster Now"* + *"Read the RFC"*
* Product Visual: Live tabbed interactive terminal (`TypeScript` / `cURL`).
* **Section 2 (Problem Contrast):** Before/After comparison of centralized database bottlenecks vs. distributed edge cache.
* **Section 3 (Feature Bento):** 3 asymmetric cells (Architecture data flow, latency chart, SDK ergonomic sample).
* **Section 4 (Social Proof):** Quantified metrics (14.2M daily vectors, 99.99% uptime) + 2 verified engineering quotes.
* **Section 5 (Pricing Matrix):** Developer (Free), Team ($49/mo), Enterprise (Custom) with billing interval toggle.
* **Section 6 (FAQ):** 4 technical disclosure accordions.
* **Footer:** Sitemap, status dot, copyright, and compliance badges.
## 5. File & Component Manifest
* `src/components/ui/container.tsx`
* `src/components/ui/section-header.tsx`
* `src/components/ui/button.tsx`
* `src/components/site/navbar.tsx`
* `src/components/site/hero.tsx`
* `src/components/site/problem-contrast.tsx`
* `src/components/site/feature-grid.tsx`
* `src/components/site/social-proof.tsx`
* `src/components/site/pricing-matrix.tsx`
* `src/components/site/faq-accordion.tsx`
* `src/components/site/footer.tsx`
* `src/config/site.ts`
* `src/types/site.ts`
## 6. Pre-Flight Verification Criteria
* Zero purple gradient orbs or generic AI blobs.
* WCAG 2.2 AA contrast compliance (≥4.5:1 text, ≥3.0:1 UI boundaries).
* Mobile touch targets ≥44×44px.
* `npm run build` succeeds with zero TypeScript or styling warnings.
Step 4: Next Action Prompt
After writing supersite-plan.md, inform the user:
Plan complete! The architectural contract has been written to
supersite-plan.md.
Review the plan or ask for any adjustments. When you are ready to construct the site, trigger:
/supersite-build