[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3qn3kb3awdb5l":3},{"code":4,"message":5,"data":6,"timestamp":56},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":44,"summary_md":45,"topic":46,"github_topics":49,"license":50,"homepage":51,"updated_at":52,"history":53},"garrytan\u002Fgstack",16,"Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA","TypeScript",137695,20413,177,228,[16,22,28,33,39],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},47436453,"Translate Garry Tan's LinkedIn-speak to plain English",115,22,"2026-03-19",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},47418576,"Garry Tan's Claude Code Setup",74,79,"2026-03-17",{"id":29,"title":30,"points":31,"comments":31,"posted_at":32},47355173,"gstack – Garry Tan's Claude Code Setup",15,"2026-03-12",{"id":34,"title":35,"points":36,"comments":37,"posted_at":38},47424580,"Garry Tan's exact Claude Code setup",3,2,"2026-03-18",{"id":40,"title":41,"points":36,"comments":42,"posted_at":43},47484489,"Garrytan\u002Fgstack: Use Garry Tan's exact Claude Code setup: 15 opinionated tools",1,"2026-03-23","A Claude Code skill pack that applies CEO, design, release and QA reviews to a solo developer's coding workflow.","Worth a look if you already drive Claude Code daily and want structured review steps around it; skip it if you expect a standalone tool or dislike installing skills into your global Claude setup.\n\n## The problem\n\nA solo builder wants the kind of scrutiny a small team gives a feature: someone to challenge the scope, someone to review the branch, someone to check the release and run QA. Doing that manually means switching hats between coding sessions and improvising each review. With gstack installed, those steps become named skills invoked from inside Claude Code: describe what you are building, run the planning and review skills, then run QA against a staging URL or an isolated local target. The result is a repeatable checklist around the coding agent rather than a new editor or platform.\n\n## What's different\n\nThe mechanism is a set of 23 skills installed under `~\u002F.claude\u002Fskills\u002Fgstack`, each mapped to a role such as CEO review, QA, release management or documentation. The README's quick start deliberately stops after five commands so you can judge whether the style suits you. A team mode bootstraps the repository so teammates inherit the setup, with an hourly, network-failure-safe auto-update check instead of vendored copies. There are also four standalone skills for OpenClaw agents that need no Claude Code session.\n\nThe trade-off is that this is a personal workflow encoded as instructions, not a product with a stable interface. It depends on Claude Code and on a long list of local prerequisites, and the network traffic has three separate switches, including opt-in telemetry that logs skill names, outcomes and error classes. If you want minimal tooling overhead, that is a lot of moving parts; if you want opinionated review steps, it is the point.\n\n## Who should try it\n\nGood fit: a developer already using Claude Code who wants enforced planning, review and QA passes on solo or small-team work, and is comfortable with local installs. Poor fit: someone who wants an editor-independent tool, or who shares a repo with teammates unwilling to install the same stack, since team mode is the documented way to keep versions aligned. Users on Codex or OpenClaw have documented alternative setup paths, which changes the audience but not the Claude Code dependency for the core skills.\n\n## Requirements and limitations\n\nYou need Claude Code, Git and Bun v1.4.2+ (setup refuses older than 1.3.3), plus Node.js on Windows. On macOS, the recommended Aside browser is optional but changes which browser the browser skills drive; without it, setup builds a bundled browser. `\u002Fcso` is stricter and needs a Bun build with specific compile flags and a native toolchain, so on machines without a C compiler that skill reports `not assessed` while the rest installs.\n\nOngoing upkeep matters: the team mode auto-update, the doctor command and the troubleshooting reference for individual skill messages are the documented paths when something is stale or unregistered. The README also documents uninstall and state cleanup, which keeps removal from being a manual hunt.\n\n## HotRepo's take\n\nHotRepo recorded the project on the daily board once, on 2026-10-25, at 137,611 stars and +177 for that day; with a single dated sample, persistence of interest cannot be judged. The visible HN discussion is mostly about the README's marketing tone rather than the skills themselves. Before installing, check that the specific skill you care about (especially `\u002Fcso`) reports `ok` in the doctor output on your machine.\n\n[Project source and documentation](https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack)",{"slug":47,"name":48},"developer-tools","Developer Tools",[],"MIT",null,"2026-10-25T11:01:57Z",[54],{"date":55,"stars":11,"stars_gained":13},"2026-10-25",1792967938]