Click any command node to learn how to use it. Drag to explore. Scroll to zoom.
Each specialist brings deep expertise. Click any card to see a real founder scenario.
Six commands. From idea to shipped PR. Click any step to see exactly what happens.
Flip to reveal. Mark as learned. Arrow keys to navigate. Master all 31 commands.
A conversational overview of GStack — what it is, why it matters, and how to use it as a founder.
Welcome to GStack — Garry Tan's Claude Code engineering team. If you're a founder who's using AI to build software, this changes how you work.
Here's the core idea: when you open Claude Code, you're usually talking to a generalist. GStack gives you 23 specialists instead — each one deeply focused on a specific part of the engineering process. A CEO advisor who questions your product decisions. An engineering manager who locks down architecture. A designer who catches visual slop. A security officer who runs OWASP audits. All of them, on demand, in seconds.
Let's walk through how a founder actually uses this. You have an idea for a new feature. You start with /office-hours — you describe what you want to build in plain English. GStack's team listens, asks clarifying questions, and produces a structured plan. Not vague advice. An actual plan with role assignments.
Then you run /plan-ceo-review. This is Garry Tan's CEO advisor lens. It pressure-tests your idea. Is this the right thing to build? Will users actually want this? Are you solving the real problem or a symptom? This saves you from building the wrong thing — which is the most expensive mistake a founder makes.
Once you're confident in the direction, /plan-eng-review locks the architecture. The engineering manager role prevents you from making shortcuts that become nightmares later. It's the difference between code you can scale and code that collapses at 10x users.
Your AI agents build the feature. Then you run /review. This is a production-grade code review — not a vibe check. It finds real bugs, edge cases, performance issues, and security holes. Things that would slip through any PR review at a normal startup.
Next, /qa opens a real browser and tests your app like a first-time user would. It's not unit tests. It's actual browser automation — clicking through flows, checking that buttons work, finding the broken states that only appear in production.
Finally, /ship. One command. Claude Code commits your changes, runs the tests, creates the pull request, monitors CI, and tells you when it's merged. End-to-end. No DevOps knowledge required.
That's six commands from idea to shipped feature. For a founder, that's the entire engineering workflow — handled by a team of AI specialists who never sleep, never complain, and never bill by the hour.
GStack also has a /freeze and /guard system so you can protect critical parts of your codebase from accidental AI modifications. A /cso command that runs a full security audit. A /canary deployment strategy for rolling out risky changes safely.
The bottom line: GStack is the engineering team you can't afford to hire, available right now, for the cost of a Claude Code subscription. Use it. Master it. Ship faster than teams with five engineers.
Search, filter, and copy. No friction.