the-grid-cc 1.5.0 → 1.6.0

package/.grid/plans/blog-block-06.md

@@ -1,325 +0,0 @@
----
-cluster: james-weatherhead-blog
-block: 06
-type: execute
-wave: 4
-depends_on: [02, 04, 05]
-files_modified: [.gitignore, README.md, vercel.json]
-autonomous: false
-
-must_haves:
-  truths:
-    - "Project builds successfully for production"
-    - "All pages render without errors"
-    - "Vercel configuration is deployment-ready"
-  artifacts:
-    - path: "README.md"
-      provides: "Project documentation for setup and deployment"
-      min_lines: 30
-    - path: ".gitignore"
-      provides: "Git ignore rules for build artifacts and secrets"
-      min_lines: 10
-    - path: "vercel.json"
-      provides: "Vercel deployment configuration"
-      min_lines: 5
-  key_links:
-    - from: "vercel.json"
-      to: "astro.config.mjs"
-      via: "framework detection"
-      pattern: "astro"
----
-
-<objective>
-Finalize project for production deployment - verification, documentation, and deployment configuration.
-
-Purpose: Ensure blog is production-ready with comprehensive documentation and verified build.
-Output: Deployment-ready blog with README, verified build, and Vercel config.
-</objective>
-
-<context>
-All feature blocks completed:
-- Block 01: Project initialization ✓
-- Block 02: Layout system with dark mode ✓
-- Block 03: Content collection and blog posts ✓
-- Block 04: Static pages and tag filtering ✓
-- Block 05: RSS feed ✓
-
-This final block:
-1. Verifies entire site builds without errors
-2. Creates comprehensive README for users/developers
-3. Confirms Vercel configuration from Block 01
-4. Tests production build locally
-5. Prepares for Vercel deployment
-
-This is a verification and documentation block - no new features, just ensuring everything works together.
-</context>
-
-<threads>
-
-<thread type="auto">
-  <name>Thread 1: Comprehensive production build verification</name>
-  <files>.gitignore</files>
-  <action>
-  Verify production build and clean up configuration:
-
-  1. Run full build pipeline:
-     ```bash
-     cd /Users/jacweath/grid/blog
-     npm run build
-     ```
-
-  2. Verify build outputs:
-     - Check dist/ directory created
-     - Verify all pages generated (index, blog, about, posts, tags, rss.xml)
-     - Check for build warnings or errors
-     - Verify syntax highlighting assets included
-
-  3. Test production build locally:
-     ```bash
-     npm run preview
-     ```
-     - Visit all pages: /, /blog, /about, /blog/sample-post, /blog/tags/{tag}, /rss.xml
-     - Test dark mode toggle on each page
-     - Check for console errors
-     - Verify navigation links work
-
-  4. Update .gitignore if needed:
-     - Ensure dist/ excluded
-     - Ensure .astro/ excluded
-     - Ensure .vercel/ excluded
-     - Add any OS-specific files (.DS_Store, Thumbs.db)
-
-  AVOID: Do not ignore node_modules in package-lock.json (commit lock file). Do not add IDE configs to gitignore (use global gitignore). WHY: Lock files ensure reproducible builds; IDE configs are personal preference, not project-level.
-  </action>
-  <verify>
-  Run: npm run build
-  Check: Exit code 0 (success)
-  Check: dist/ contains index.html, blog/, rss.xml
-  Run: npm run preview
-  Visit: All pages load without errors
-  Check: Console has no errors
-  Check: Dark mode works on all pages
-  </verify>
-  <done>
-  - npm run build completes successfully
-  - All pages generated in dist/ directory
-  - npm run preview serves production build
-  - All pages accessible and functional
-  - No console errors or build warnings
-  - .gitignore updated with all necessary exclusions
-  </done>
-</thread>
-
-<thread type="auto">
-  <name>Thread 2: Create comprehensive README documentation</name>
-  <files>README.md</files>
-  <action>
-  Create README.md with project documentation:
-
-  1. Project overview section:
-     - Project name: James Weatherhead Blog
-     - Description: Minimal technical blog built with Astro
-     - Tech stack: Astro, Tailwind CSS, TypeScript
-     - Features: Dark mode, markdown posts, tags, RSS feed
-
-  2. Prerequisites section:
-     - Node.js 18+ required
-     - npm or pnpm
-
-  3. Getting Started section:
-     ```bash
-     # Install dependencies
-     npm install
-
-     # Start dev server
-     npm run dev
-
-     # Build for production
-     npm run build
-
-     # Preview production build
-     npm run preview
-     ```
-
-  4. Project Structure:
-     ```
-     /
-     ├── src/
-     │   ├── components/       # Reusable components
-     │   ├── content/
-     │   │   └── blog/        # Markdown blog posts
-     │   ├── layouts/         # Layout components
-     │   ├── pages/           # Route pages
-     │   └── styles/          # Global styles
-     ├── public/              # Static assets
-     └── astro.config.mjs     # Astro configuration
-     ```
-
-  5. Content Management:
-     - How to add new blog post (create .md in src/content/blog/)
-     - Frontmatter schema explanation
-     - Tag usage
-
-  6. Deployment section:
-     - Vercel deployment instructions
-     - Environment variables (if any)
-     - Custom domain setup (brief)
-
-  7. Features section:
-     - Dark mode toggle
-     - Syntax highlighting
-     - RSS feed at /rss.xml
-     - Tag-based filtering
-
-  AVOID: Do not add contributing guidelines yet (single author). Do not add license section unless specified. WHY: Personal blog doesn't need complex governance docs; add if project becomes open source.
-  </action>
-  <verify>
-  Check: README.md exists with all sections
-  Check: Installation commands are accurate
-  Check: Project structure matches actual structure
-  Run: Follow getting started steps to verify accuracy
-  </verify>
-  <done>
-  - README.md created with comprehensive documentation
-  - All sections present: overview, prerequisites, getting started, structure, deployment
-  - Installation and build commands verified
-  - Content management instructions clear
-  - Deployment instructions for Vercel included
-  </done>
-</thread>
-
-<thread type="auto">
-  <name>Thread 3: Verify and document Vercel configuration</name>
-  <files>vercel.json</files>
-  <action>
-  Verify Vercel deployment configuration:
-
-  1. Check vercel.json from Block 01:
-     - Ensure framework: "astro"
-     - Ensure buildCommand: "npm run build"
-     - Ensure outputDirectory: "dist"
-
-  2. Verify astro.config.mjs:
-     - Adapter: @astrojs/vercel/serverless (or /static if fully static)
-     - Site URL: Update if final domain known (e.g., https://jamesweatherhead.com)
-
-  3. Create deployment checklist in README:
-     ```markdown
-     ## Deployment to Vercel
-
-     1. Push code to GitHub repository
-     2. Import project in Vercel dashboard
-     3. Vercel auto-detects Astro framework
-     4. Set environment variables (if any):
-        - SITE_URL: https://yourdomain.com
-     5. Deploy
-     6. Configure custom domain (optional)
-     ```
-
-  4. Test local build mimics Vercel:
-     - Ensure no local-only dependencies
-     - Verify all imports are relative (not absolute)
-     - Check no hardcoded localhost URLs
-
-  AVOID: Do not add CI/CD pipelines yet (Vercel handles this). Do not add preview deployment config (Vercel provides automatically). WHY: Vercel's built-in CI/CD is sufficient for blog; manual configuration adds complexity.
-  </action>
-  <verify>
-  Check: vercel.json has correct framework and build settings
-  Check: astro.config.mjs has site URL configured
-  Check: README.md has deployment instructions
-  Run: npm run build (simulate Vercel build)
-  Check: No errors referencing localhost or local paths
-  </verify>
-  <done>
-  - vercel.json verified with correct configuration
-  - astro.config.mjs has site URL set
-  - README.md includes deployment checklist
-  - Build succeeds without local-only dependencies
-  - Project ready for Vercel deployment
-  </done>
-</thread>
-
-<thread type="checkpoint:human-verify" gate="blocking">
-  <what-built>
-  Production-ready blog with:
-  - Verified production build (all pages generate correctly)
-  - Comprehensive README documentation
-  - Vercel deployment configuration
-  - Complete project ready for deployment
-  </what-built>
-  <how-to-verify>
-  1. cd /Users/jacweath/grid/blog
-
-  2. Clean build test:
-     ```bash
-     rm -rf dist/
-     npm run build
-     ```
-     - Should complete without errors
-     - Check dist/ contains all expected files
-
-  3. Preview production build:
-     ```bash
-     npm run preview
-     ```
-     - Visit http://localhost:4321
-     - Test all pages: /, /blog, /about, /blog/sample-post
-     - Test tag filtering: click tags, verify filtered posts
-     - Test RSS feed: visit /rss.xml
-     - Test dark mode toggle on each page
-     - Check browser console for errors (should be none)
-
-  4. Review documentation:
-     - Read README.md
-     - Verify instructions are clear and accurate
-     - Check project structure matches reality
-
-  5. Verify deployment readiness:
-     - Check vercel.json exists with correct settings
-     - Check .gitignore excludes build artifacts
-     - Verify no hardcoded localhost URLs in code
-
-  6. Final checklist:
-     - [ ] Build completes successfully
-     - [ ] All pages load in preview
-     - [ ] Dark mode works everywhere
-     - [ ] Navigation links functional
-     - [ ] Tags filter correctly
-     - [ ] RSS feed validates
-     - [ ] README accurate
-     - [ ] No console errors
-  </how-to-verify>
-  <resume-signal>Type "approved" if blog is production-ready and documentation is complete, or describe issues (e.g., "build fails", "page missing", "README unclear")</resume-signal>
-</thread>
-
-</threads>
-
-<verification>
-Complete verification checklist:
-1. npm run build completes with exit code 0
-2. dist/ directory contains all pages and assets
-3. npm run preview serves production build successfully
-4. All pages load without errors (/, /blog, /about, posts, tags, rss.xml)
-5. Dark mode toggle works on all pages
-6. Navigation links functional across site
-7. Tag filtering displays correct posts
-8. RSS feed accessible and validates
-9. README.md complete with all sections
-10. vercel.json configured correctly
-11. .gitignore excludes all build artifacts
-12. No hardcoded localhost or local-only dependencies
-13. Browser console has no errors
-14. User approves blog is deployment-ready
-</verification>
-
-<success_criteria>
-- Production build succeeds without errors
-- All pages render correctly in preview
-- Dark mode functional across entire site
-- Navigation and filtering work as expected
-- RSS feed validates and loads in feed readers
-- README provides clear setup and deployment instructions
-- Vercel configuration ready for deployment
-- No console errors or warnings
-- User confirms blog is ready to deploy to Vercel
-</success_criteria>

package/DEMO_SCRIPT.md

@@ -1,162 +0,0 @@
-# THE GRID - Demo Recording Script
-
-## Target: 60-second GIF/Video for README
-
-### Setup Before Recording
-- Clean terminal (black background, cyan/white text if possible)
-- Font size large enough to read
-- Window sized to ~800x600
-- Clear any previous .grid/ state
-- Have `asciinema` or screen recording ready
-
----
-
-## THE SCRIPT
-
-### Scene 1: The Hook (5 seconds)
-```
-$ claude
-```
-*Wait for Claude Code to load*
-
-### Scene 2: Enter The Grid (5 seconds)
-```
-/grid
-```
-
-**Expected Output:**
-```
-THE GRID
-════════
-
-Master Control online.
-
-What would you like to build?
-
-End of Line.
-```
-
-### Scene 3: The Ask (5 seconds)
-Type:
-```
-Build me a CLI that analyzes a GitHub repo and shows contributor stats
-```
-
-### Scene 4: Mode Selection (5 seconds)
-**Expected Output:**
-```
-How involved do you want to be?
-
-  HANDS OFF - I make all decisions and build it. You see the finished result.
-  HANDS ON  - We discuss choices together before building.
-```
-
-Type:
-```
-hands off
-```
-
-### Scene 5: The Magic (30 seconds)
-*Let it run - this is the money shot*
-
-**What viewers should see:**
-- "Researching best practices..."
-- "Spawning Planner Program..."
-- Task(Plan github-analyzer) with tool uses expanding
-- Multiple agents potentially spawning
-- Files being created
-- Tests running
-
-*Speed this up 2-4x in post if needed*
-
-### Scene 6: The Result (10 seconds)
-**Expected Output:**
-```
-BUILD COMPLETE
-══════════════
-
-Project: github-analyzer
-Stack: Python 3 + requests + rich
-Files:
-  - analyzer.py (CLI tool)
-  - README.md
-
-Usage: python analyzer.py <repo-url>
-
-[Shows example output]
-```
-
-Type:
-```
-python analyzer.py https://github.com/anthropics/claude-code
-```
-
-*Show it actually working*
-
----
-
-## ALTERNATIVE DEMOS (Pick most impressive)
-
-### Option B: Full-Stack in 2 Minutes
-```
-Build a todo app with React frontend and Express API
-```
-- Shows parallel agent spawning
-- Multiple files created
-- Actually runs
-
-### Option C: The Meta Demo
-```
-Build a CLI that generates ASCII art from text
-```
-- Simple enough to complete quickly
-- Visual output is satisfying
-- Easy to verify it works
-
----
-
-## POST-PRODUCTION
-
-1. **Speed up** the waiting/building parts (2-4x)
-2. **Add captions** at key moments:
-   - "Tell Master Control what to build"
-   - "HANDS OFF = zero decisions"
-   - "Agents spawn automatically"
-   - "Working code in 60 seconds"
-3. **Loop** the GIF for README
-
----
-
-## RECORDING TOOLS
-
-**For GIF:**
-```bash
-# Install asciinema + agg
-brew install asciinema
-cargo install --git https://github.com/asciinema/agg
-
-# Record
-asciinema rec demo.cast
-
-# Convert to GIF
-agg demo.cast demo.gif --speed 2
-```
-
-**For Video:**
-- OBS Studio
-- macOS built-in screen recording
-- Loom (if you want voiceover)
-
----
-
-## KEY MESSAGES TO CONVEY
-
-1. **One command** to start: `/grid`
-2. **One word** to delegate: `hands off`
-3. **Zero decisions** - it just builds
-4. **Working code** - not stubs, real output
-5. **TRON aesthetic** - memorable branding
-
----
-
-*End of Line.*

package/HN_POST.md

@@ -1,104 +0,0 @@
-# Hacker News Post Drafts
-
-## OPTION A: The Direct Approach
-
-**Title:** Show HN: The Grid – TRON-themed agent orchestration for Claude Code
-
-**Text:**
-I built The Grid because I was tired of babysitting AI coding sessions. Every time Claude needed a decision about frameworks, folder structure, or deployment—another context switch.
-
-The Grid adds a simple mode to Claude Code: HANDS OFF.
-
-You say what you want. Master Control (the orchestrator) spawns specialized agents—Planner, Executor, Recognizer—to do the work. You get working code, not questions.
-
-```
-/grid
-> Build me a CLI that converts JSON to YAML
-> hands off
-
-[2 minutes later]
-
-BUILD COMPLETE
-Files: converter.py (207 lines)
-Tests: All passing
-```
-
-Built with Claude, for Claude Code users. TRON theme because why not.
-
-GitHub: https://github.com/JamesWeatherhead/grid
-Install: `npx the-grid-cc`
-
----
-
-## OPTION B: The Problem-First Approach
-
-**Title:** Show HN: The Grid – Stop babysitting your AI coding sessions
-
-**Text:**
-Problem: Claude Code is powerful but chatty. "Which framework?" "Where should I put this?" "Should I use TypeScript?" Death by a thousand decisions.
-
-Solution: The Grid adds orchestration to Claude Code with two modes:
-- HANDS OFF: AI makes all technical decisions, you approve the result
-- HANDS ON: Collaborate on choices
-
-Under the hood, it spawns specialized subagents (Planner, Executor, Verifier) with fresh context windows. Master Control stays lean while heavy work happens in parallel.
-
-The TRON theme keeps it fun. "End of Line."
-
-Try it: `npx the-grid-cc` then `/grid` in Claude Code.
-
----
-
-## OPTION C: The Technical Hook
-
-**Title:** Show HN: The Grid – Parallel AI agent orchestration for Claude Code
-
-**Text:**
-The Grid orchestrates Claude Code subagents to build software autonomously.
-
-Key features:
-- Spawns parallel agents via Claude's Task tool (real subprocess isolation)
-- Wave-based execution (computed during planning, not runtime)
-- Goal-backward verification (checks outcomes, not just task completion)
-- Fresh 200k context per agent (no degradation from long sessions)
-
-Architecture is simple: You → Master Control → Programs (Planner/Executor/Recognizer)
-
-HANDS OFF mode: describe what you want, get working code. No framework debates. No folder structure discussions.
-
-GitHub: https://github.com/JamesWeatherhead/grid
-
----
-
-## POSTING STRATEGY
-
-**Best time to post:** Tuesday-Thursday, 9-11am ET
-
-**Title rules:**
-- Start with "Show HN:"
-- No ALL CAPS (except Show HN)
-- Under 80 chars
-- Lead with benefit or unique angle
-
-**Engagement:**
-- Be ready to answer questions for first 2 hours
-- Be honest about limitations
-- Thank people for feedback (even criticism)
-
-**Avoid:**
-- Defensive responses
-- Marketing speak
-- "We're excited to announce"
-
----
-
-## BACKUP TITLES
-
-1. "Show HN: The Grid – One word ('hands off') to make Claude Code fully autonomous"
-2. "Show HN: The Grid – Orchestrate Claude Code agents with a TRON-themed CLI"
-3. "Show HN: The Grid – Parallel AI agents that actually build working code"
-4. "Show HN: I built an orchestrator so Claude Code stops asking me questions"
-
----
-
-*End of Line.*