gstack

Install it and your coding assistant grows a staff. One command convenes a CEO to second-guess the spec; another an engineering manager to pick it apart; /qa opens a real browser and writes regression tests; /cso runs a security audit; /ship files the pull request. None of it is new code. gstack is a folder of Markdown instruction files — prompts that tell Claude Code to impersonate a role — pasted into your config with a single line. Garry Tan, the president and CEO of Y Combinator, published his personal one verbatim, the literal setup he uses daily, under an MIT licence.

It removes friction, it does not buy you judgment.

Within weeks it passed 100,000 GitHub stars, more than most heavily-engineered open-source projects ever earn. That is the genuinely odd part. Critics were quick to point out that it is, in one reviewer's words, 'a bunch of prompts in a text file' — and they are literally right; there is no library here, no novel machinery. The thing that pulled the stars was provenance: not a framework, but one influential operator's exact end-to-end workflow, shipped as-is and runnable on Claude Code plus eight or so other coding agents.

Tan paired the release with a striking boast — an 810-fold jump in his own output, hundreds of thousands of lines shipped part-time. That number, which leans entirely on a productivity metric he defined himself, is what started the fight; no independent party has reproduced it, and the repo now carries Tan's own rebuttal as a versioned document. Reviewers who actually ran gstack report real but far smaller gains, and converge on the same verdict: it strips friction out of the workflow, but the judgment about what to build still has to come from you.