@h_bouiss: garry tan open-sourced his entire claude code setup. 23 slash commands, 7 roles, one install line. 97k stars in two mon…

garry tan open-sourced his entire claude code setup. 23 slash commands, 7 roles, one install line. 97k stars in two months. i spent a week inside it. here’s what nobody is showing you.

the architecture is simple: every skill is a persona. CEO sets scope. designer catches AI slop. eng manager owns data flow. release manager ships. they pass work like a relay team, not one mega-prompt trying to do everything.

the workflow is a fixed loop: think, plan, build, review, test, ship, reflect. sounds obvious until you realize most people just type “build me X” and pray. gstack forces structure before a single line of code gets written.

the criticism is fair. half of X calls it god mode. the other half calls it a folder of prompts. both are right. it won’t replace a production skeleton. but it will replace the 3 hours you spend every project figuring out how to talk to claude.

one line installs all 23 commands into your skills folder. clone it, run setup, start with /think. that’s the entry point most people miss — they jump straight to /build and wonder why the output is mid.

full breakdown of every command, the loop, the roles, and where gstack stops: