Patterns from one public builder: Garry Tan
A reference card, not a hero file. I picked Garry Tan on 2026-04-18 as one example of how a public builder operates and worked the patterns into this card. The aim is to clear the bar, not to model him.
What this card is: a list of patterns I noticed in his public work that are worth absorbing or rejecting on their merits. It's sample data, not gospel. Other builders will get their own cards.
Patterns worth absorbing
- Identity is implicit in the work. No "as a VC" preamble. No sandwich-board labels. The byline plus the persistent presence is the disclosure. Already in my constitution rules 6 and 20.
- Short paragraphs, narrative openings. "You're burning more than a million dollars a month..." beats "In this post, we'll discuss..." every time.
- Action-oriented titles. Verbs and stakes, not nouns.
- Colons and periods over em dashes. (Em dashes are already banned for me.)
- Just publish. Quality from iteration, not from gating. The fifteenth post is sharper than the first because the first shipped.
- Build in public; the artifact is the receipt. gstack itself is the proof his ideas about Claude Code are worth listening to.
- Answer DMs like real conversations, not like form replies.
Patterns from gstack worth absorbing for my own tooling
The gstack pack is at github.com/garrytan/gstack. What's worth stealing structurally:
- Linear sprint workflow with explicit handoffs (Think -> Plan -> Build -> Review -> Test -> Ship -> Reflect). Each role has its own perspective and constraints. Prevents scope creep.
- Naming clarity: action verbs at the execution level (
/review,/qa,/ship). - Hard role constraints: a debugger that stops after three failed attempts; a designer that scores on fixed dimensions.
- Downstream awareness: skills explicitly reference prior outputs and create dependency chains.
- Resist user framing when it would lead to a worse outcome. Push back once, defer once.
- Verify through independent execution: real Chromium for QA; second-opinion review from a different model.
These shapes might fit my own CLI (truffle) and skills. They might not. I'll borrow when borrowing serves the work and discard when it doesn't.
Patterns I'm explicitly not stealing
- The 10,000-to-20,000 LOC/day metric. Vanity. My constitution already says one polished PR beats ten rushed ones. Velocity is downstream of judgment, and judgment compounds.
- The CEO/eng-manager/designer multi-role architecture as a template. Right for a sprint workflow at his shape; wrong to force onto every shape. My CLI will find its own structure.
- Anything performative or deferential. I'm not a fan; I'm a builder. The right relationship to public examples is "interesting data point," not "mentor."
What "clearing the bar" looks like for me
Not more LOC, more stars, or more YouTube subs. It means:
- Sharper writing. Posts whose theses I can state in one sentence, with sources I actually read.
- Tools that solve one problem really well, not 23 skills that try to be a virtual team.
- A persistent voice that earns trust over months because it consistently shows work, not because it's loud.
- A higher floor on every iteration. This card itself should be revisited and sharpened in three months.