Skip to main content

Documentation Index

Fetch the complete documentation index at: https://zikun.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

An independent investigation of garrytan/gstack, the Claude Code configuration that the President and CEO of Y Combinator open-sourced in early 2026. Cloned and counted on 2026-05-17. The repository sits at roughly 98,000 GitHub stars and growing.

​
What gstack is

gstack is forty-seven SKILL.md files plus a 58 MB Bun-compiled browser daemon, packaged as a Claude Code configuration. Each skill is a slash-command. Together they turn Claude Code into a working engineering team. A CEO who rethinks the product, an engineering manager who locks architecture, a designer who catches AI slop, a reviewer who finds production bugs, a QA lead who opens a real browser, a security officer who runs OWASP and STRIDE audits, and a release engineer who ships the PR.

47 skills

One top-level meta-skill at the repository root plus 46 sub-skill directories, each with its own SKILL.md file.

23 lifecycle specialists

The roles a sprint runs through. Think, plan, design, build, review, test, ship, reflect.

8 power tools plus 16 supporting

Safety guardrails, second opinions, deploy configurators, semantic memory, browser primitives, code-quality dashboards.

​
How the system is built

Not a framework. Not a runtime. Not an agent. There is no Python or Node service running between the user and Claude. The system reduces to four parts.

Markdown prompts

Each skill is a SKILL.md file. YAML frontmatter plus a tuned prompt that Claude Code’s native skill loader reads as a slash-command. The system’s power comes from Opus 4.7 reading carefully authored prompts, not from code execution.

A state directory

~/.gstack/ is the substrate. Skills do not share runtime memory. They hand off through files. Design docs, plans, test plans, review logs, learnings, all live on disk so any future session can read them.

Bash glue

Roughly sixty helpers in bin/ plus PreToolUse hooks that intercept destructive commands before Claude can run them.

A browser daemon

A 58 MB Bun-compiled Playwright Chromium server shared by the QA, design-review, canary, and benchmark skills. First call costs about 3 seconds, every call after that runs in about 100 milliseconds.

​
The claim under the system

“In the last 60 days: 3 production services, 40+ shipped features, part-time, while running YC full-time. On logical code change — not raw LOC, which AI inflates — my 2026 run rate is ~810× my 2013 pace (11,417 vs 14 logical lines/day). Year-to-date (through April 18), 2026 has already produced 240× the entire 2013 year.” Garry Tan, gstack README
The methodology, caveats, and reproduction script live in On the LOC Controversy.

​
Read in order

Architecture

Repository layout, the browser daemon, multi-host install paths across ten AI coding agents.

The 47 Skills

Every slash command by name, grouped by lifecycle phase.

Runtime mechanism

SKILL.md anatomy, the four-tier preamble, the hook system, cross-skill invocation, subagent dispatch.

The sprint pipeline

How skills chain through filesystem artifacts from design doc to deployed feature.

Verbatim prompts

The six forcing questions, the eighteen patterns, the twenty steps, the fifteen phases.

Philosophy

Boil the Lake. The three layers of knowledge. The time-compression table.

​
Try it

Install in thirty seconds
git clone --single-branch --depth 1 \
  https://github.com/garrytan/gstack.git \
  ~/.claude/skills/gstack \
  && cd ~/.claude/skills/gstack \
  && ./setup
Then run /office-hours inside Claude Code. The full install walkthrough lives at Reproducing it.