G-Stack

Larry Chiang here. UIUC CS. Your CS major CRO for rent.

Plain text. No slides. No hype. Just straight execution.

Garry Tan ships more code part-time running YC than most full-time engineers because of G-stack. This is his exact Claude Code setup. He open-sourced it. Twenty-three specialist skills that turn one AI into a full virtual engineering team. Here is how to reverse engineer Garry Tan’s stack, row by row, plain.

Row 1. Office hours runs YC-style product interrogation. Six forcing questions. Reframe everything before you touch code. Outputs a design doc that feeds every later row.

Row 2. Plan ceo review acts as founder CEO. Rethinks the request. Four scope modes: expand, selective expand, hold, or reduce. Finds the ten-star version hiding inside.

Row 3. Plan eng review locks architecture, data flow, diagrams, edge cases, and tests. Forces hidden assumptions out.

Row 4. Plan design review scores every design dimension zero to ten and shows exactly what ten looks like.

Row 5. Plan devex review audits time-to-hello-world, friction points, and magical moments.

Row 6. Autoplan runs the full planning pipeline automatically and surfaces only the taste decisions for you.

Row 7. Review works as staff engineer. Finds bugs that pass CI but explode in production. Auto-fixes the obvious ones.

Row 8. Investigate does systematic root-cause debugging. Iron law: no fixes until you know why.

Row 9. Design review does live-site visual audit plus fixes with atomic commits and screenshots.

Row 10. Design shotgun generates multiple AI mockup variants and opens a browser comparison board.

Row 11. Design html turns approved mockups into production-quality responsive HTML/CSS. Framework-aware.

Row 12. Design consultation builds a complete design system from scratch.

Row 13. QA opens the real browser, tests the app, finds bugs, fixes them atomically, and adds regression tests.

Row 14. QA only delivers pure bug reports without touching code.

Row 15. CSO runs full OWASP Top Ten plus STRIDE security audit.

Row 16. Ship syncs main, runs tests, checks coverage, and opens the PR. Bootstraps testing if missing.

Row 17. Land and deploy merges the PR, waits for CI and deploy, then verifies in production.

Row 18. Canary monitors post-deploy for console errors and performance regressions using the browser.

Row 19. Benchmark tracks page load times, Core Web Vitals, and trends before and after every change.

Row 20. Document release updates all project docs to match what just shipped.

Row 21. Document generate creates proper Diataxis docs (tutorial, how-to, reference, explanation) straight from code.

Row 22. Retro runs the weekly engineering retrospective with per-person breakdowns, shipping streaks, test health, and next opportunities.

Power tools sit around the rows: careful, freeze, guard for safety; real Chromium browser with cookie import and screenshots; GBrain persistent memory that syncs with your repo; codex for a second opinion from another model; and self-upgrade so the stack stays current.

How to reverse engineer and run it yourself

Clone the GitHub repo. Paste the one-line install into Claude Code. Add the gstack section to your CLAUDE.md file so it always knows the skills. Start every new thing with row 1 office hours. Chain the rows exactly. Use the browser for real QA instead of pretend tests. Keep GBrain synced so the AI remembers your taste and past decisions. Safety layers on first so it never wrecks your code.

This stack is the Posterous-to-Posthaven mindset applied to AI coding. When the old way dies, you build the forever version that actually makes money and keeps promises. Garry used it to ship three production services and forty-plus features while running YC. Logical code changes went eight hundred ten times faster than his 2013 pace.

UIUC CS lesson: structure beats raw talent. Process beats prompting. One AI with twenty-three clear roles and safety rails ships like a whole team. Clone it. Run the rows. Measure your own output. Then charge real money for what you ship.

Need a CS major CRO for rent to turn your stack into revenue? Hit me. Duck9 rules since 1989.

Ship or die. Execute the rows. Keep the URLs and the AI team alive forever.

Larry Chiang

UIUC CS

CRO for rent