Garry Tan's Claude Code Strategies: Roles, Parallels, Tools, Plans

The Breakthrough

Garry Tan uses Claude Code with role-specific prompting in gstack's .claude.md file, which enforces skill routing to assign tasks to virtual team roles (CEO for product rethink, engineering manager for architecture, designer for slop detection), mandatory code search before new writes, and effort compression (fast responses for simple tasks like renames, deep analysis for architecture).

What Actually Worked

• Users describe tasks naturally; gstack routes them to roles like product CEO, engineering manager, or security checker without explicit instructions.
• Claude searches existing codebase before generating new code to avoid reinvention as projects scale.
• Effort levels adjust automatically: quick for low-effort tasks, thorough for high-effort ones.
• Run up to 5 parallel Claude sessions simultaneously across workspaces (one for feature building, one for code review, one for security); exceed 5 at risk of oversight and incomplete products.
• Build personal tools with low ROI bar, like gbrain (ingests meetings, emails, tweets, calendar into searchable knowledge base that Claude queries before responses).
• Run /offhours command in gstack for structured planning interview answering: what problem it solves, who it is for, what success looks like, what it should not do.

Before / After

Garry Tan ships 600,000 lines of code in 60 days part-time while running Y Combinator full-time (8-9 hours meetings daily), including 3 production services and 40+ features; achieves 10,000 lines per day across 3 projects.

Context

Garry Tan runs Y Combinator, a major AI investor backing Airbnb and Stripe, yet builds software solo with Claude Code instead of hiring engineers, as AI lowers build costs below explanation costs. Video author Austin Marchese analyzes Tan's public posts and gstack repo, implements it, critiques parallel sessions as overhyped (recommends cap at 5), praises tool-building mindset shift, and provides copy-paste prompts for .claude.md setup and /offhours equivalent (6 questions to extract overlooked details). Results matter because they enable CEO-level orchestration without teams; planning anchors everything to avoid fast wrong-direction builds.

Notable Quotes

• Major CTO on gstack security role: "gstack security role caught a security flaw his entire engineering team had missed ... this is like god mode."
• Garry Tan: "I'm shipping more products than I ever have. In the last 60 days: three production services, 40 plus shipped features, part-time while running YC full-time."
• Garry Tan: "I can do my full-time job doing like eight nine hours of meetings and get 10,000 lines of code done on like three different projects right now."