GitHub - garrytan/gstack: Use Garry Tan’s exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
Garry Tan's gstack is an open-source framework comprising 23 AI specialist tools designed to turn Claude Code (and other AI agents) into a virtual engineering team, covering roles like CEO, Designer, Eng Manager, and QA. It significantly boosts individual developer productivity, enabling one person to ship products at a pace comparable to a large team, by integrating AI throughout the entire software development sprint lifecycle. The framework provides interconnected slash commands for planning,
Curator note
# 🚀 The Ultimate gstack Reference Guide **Goal:** Move from "vibe coding" (prompting) to "high-resolution engineering" (shipping quality). --- ## 1. The Core Philosophy: The Sprint Loop Effective use of `gstack` requires following a linear path. Don't jump to coding immediately. Follow the **Think → Plan → Build → Review → Test → Ship** sequence. --- ## 2. Command Reference (The "Skills") ### 🧠 Phase 1: Strategic Planning (The "Think" Phase) * **/office-hours**: **(Start Here)** Interrogates your idea. It asks "6 forcing questions" to find the simplest version (the "narrowest wedge") of your feature. * **/plan-ceo-review**: Audits the "Design Doc" created in office hours. Focuses on product taste, user value, and scope creep. * **/autoplan**: The "Master" command. It runs the CEO, Design, and Engineering reviews automatically to build a 10/10 implementation plan. ### 🏗️ Phase 2: Technical Architecture (The "Plan" Phase) * **/plan-eng-review**: Your CTO. It creates ASCII diagrams, defines database schemas, identifies edge cases, and writes a "Test Plan" before a single line of code is written. * **/design-consultation**: Researches existing design systems and creates a `DESIGN.md` for your project's visual identity. ### 🛠️ Phase 3: Execution & Safety (The "Build" Phase) * **/freeze**: Locks the AI to a specific folder. Use this to prevent the AI from making "drive-by" edits to parts of your code that already work. * **/guard**: Activates maximum safety (Freeze + Careful mode). Prevents destructive commands like `rm -rf` or `force-push`. ### 🛡️ Phase 4: Quality Control (The "Review" Phase) * **/review**: Your Senior Dev. It audits the code you just wrote for "AI Slop" (verbose/redundant code), security holes (OWASP/STRIDE), and logic bugs. * **/cso**: Runs a dedicated **Chief Security Officer** audit specifically looking for vulnerabilities. * **/design-review**: Uses a real browser to take screenshots of your UI and critiques the typography, spacing, and UX. ### 🧪 Phase 5: Verification (The "Test" Phase) * **/qa [URL]**: Launches a headless browser (Playwright) to click through your site. It verifies that your features actually work in a real browser environment. * **/qa-only**: Runs the testing suite without trying to fix the code, giving you a pure report of what's broken. ### 🚢 Phase 6: Delivery (The "Ship" Phase) * **/ship**: Cleans up your messy "WIP" git commits, runs final tests, and prepares a professional Pull Request. --- ## 3. The "Garry Tan" Effective Workflow To get the most out of gstack, follow this exact recipe for every new feature: 1. **Start with `/office-hours`**: Never code until you've been interrogated. 2. **Run `/autoplan`**: Let the AI "debate itself" (CEO vs. Engineer) to find the best path. 3. **Execute the Plan**: Use Cursor or Claude Code to build. 4. **Audit with `/review`**: Catch the bugs you missed while vibe-coding. 5. **Verify with `/qa`**: Ensure the UI didn't break on different screen sizes. 6. **Finalize with `/ship`**: Keep your git history clean. --- ## 4. Advanced "Power User" Tools * **Continuous Checkpoint Mode**: Set `gstack-config set checkpoint_mode continuous`. This auto-commits your work as you go. If the AI crashes, you can run `/context-restore` to pick up exactly where you left off. * **The Confusion Protocol**: If the AI starts "guessing" (e.g., "I think the API works like this..."), stop it immediately. Use `/careful` and force it to read the documentation using `/browse`. * **GStack Browser**: Use `/open-gstack-browser` to launch a custom Chrome instance that can pass cookies, CSS changes, and screenshots directly back to Claude Code. --- ## 5. Maintenance Commands * **/gstack-upgrade**: Syncs your local skills with the latest improvements from the GitHub repo. * **/learn**: Manages the "Memory" of your project. It exports project-specific patterns so the AI gets smarter about your codebase over time. --- ### Cheat Sheet: Which command do I use? * **"I have a cool idea"** → `/office-hours` * **"Check my logic"** → `/review` * **"Something is broken"** → `/investigate` * **"Is the UI pretty?"** → `/design-review` * **"Ready to go live"** → `/ship`