docs(v1): README hero reframe + writing-style + CHANGELOG + version bump to 1.0.0.0

README.md:
- Hero removes "600,000+ lines of production code" framing; replaces
  with the computed 2013-vs-2026 pro-rata multiple (via
  <!-- GSTACK-THROUGHPUT-PLACEHOLDER --> anchor, filled by the
  update-readme-throughput build step).
- Hiring callout: "ship real products at AI-coding speed" instead of
  "10K+ LOC/day."
- New Writing Style section (~80 words) between Quick start and
  Install: "v1 prompts = simpler" framing, outcome-language example,
  terse-mode opt-out, pointer to /plan-tune.

CLAUDE.md: one-paragraph Writing style (V1) note under project
conventions, linking to preamble resolver + V1 design docs.

CHANGELOG.md: V1 entry on top of v0.19.0.0 with user-facing narrative
(what changes, how to opt out, for-contributors notes). Mentions
scope reduction — pacing overhaul ships in V1.1.

CONTRIBUTING.md: one-paragraph note on jargon-list.json maintenance
(PR to add/remove terms; regenerate via gen:skill-docs).

VERSION + package.json: bump to 1.0.0.0.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-04-18 11:38:57 +08:00
parent 2c404f9bd0
commit 18fc95c0a0
6 changed files with 63 additions and 4 deletions
+6 -2
View File
@@ -6,7 +6,7 @@ When I heard Karpathy say this, I wanted to find out how. How does one person sh
I'm [Garry Tan](https://x.com/garrytan), President & CEO of [Y Combinator](https://www.ycombinator.com/). I've worked with thousands of startups — Coinbase, Instacart, Rippling — when they were one or two people in a garage. Before YC, I was one of the first eng/PM/designers at Palantir, cofounded Posterous (sold to Twitter), and built Bookface, YC's internal social network.
**gstack is my answer.** I've been building products for twenty years, and right now I'm shipping more code than I ever have. In the last 60 days: **600,000+ lines of production code** (35% tests), **10,000-20,000 lines per day**, part-time, while running YC full-time. Here's my last `/retro` across 3 projects: **140,751 lines added, 362 commits, ~115k net LOC** in one week.
**gstack is my answer.** I've been building products for twenty years, and right now I'm shipping more products than I ever have. 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 output is <!-- GSTACK-THROUGHPUT-PLACEHOLDER --> my 2013 output pro-rata. (Public repos only; private work at both eras is excluded to make the comparison apples-to-apples.) AI wrote most of it. The point isn't who typed it, it's what shipped.
**2026 — 1,237 contributions and counting:**
@@ -38,6 +38,10 @@ Fork it. Improve it. Make it yours. And if you want to hate on free open source
5. Run `/qa` on your staging URL
6. Stop there. You'll know if this is for you.
## Writing style
v1 prompts = simpler. gstack's default output explains technical terms on first use, frames questions in outcome terms ("what breaks for your users if..."), and keeps sentences short. Good writing for everyone, not just non-technical folks. If you'd rather read the older, tighter prose style with no glosses, run `gstack-config set explain_level terse` — it sticks across all skills. You can also tune how often gstack asks you questions with `/plan-tune`.
## Install — 30 seconds
**Requirements:** [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Git](https://git-scm.com/), [Bun](https://bun.sh/) v1.0+, [Node.js](https://nodejs.org/) (Windows only)
@@ -349,7 +353,7 @@ Free, MIT licensed, open source. No premium tier, no waitlist.
I open sourced how I build software. You can fork it and make it your own.
> **We're hiring.** Want to ship 10K+ LOC/day and help harden gstack?
> **We're hiring.** Want to ship real products at AI-coding speed and help harden gstack?
> Come work at YC — [ycombinator.com/software](https://ycombinator.com/software)
> Extremely competitive salary and equity. San Francisco, Dogpatch District.