mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-02 03:35:09 +02:00
merge: resolve README.md conflict (take main's structure)
This commit is contained in:
@@ -22,7 +22,38 @@ I am learning how to get to the edge of what agentic systems can do as of March
|
||||
|
||||
Fork it. Improve it. Make it yours. Don't player hate, appreciate.
|
||||
|
||||
---
|
||||
**Who this is for:**
|
||||
- **Founders and CEOs** — especially technical ones who still want to ship. This is how you build like a team of twenty.
|
||||
- **First-time Claude Code users** — gstack is the best way to start. Structured roles instead of a blank prompt.
|
||||
- **Tech leads and staff engineers** — bring rigorous review, QA, and release automation to every PR
|
||||
|
||||
## Quick start: your first 10 minutes
|
||||
|
||||
1. Install gstack (30 seconds — see below)
|
||||
2. Run `/plan-ceo-review` on any feature idea
|
||||
3. Run `/review` on any branch with changes
|
||||
4. Run `/qa` on your staging URL
|
||||
5. Stop there. You'll know if this is for you.
|
||||
|
||||
Expect first useful run in under 5 minutes on any repo with tests already set up.
|
||||
|
||||
**If you only read one more section, read this one.**
|
||||
|
||||
## Install — takes 30 seconds
|
||||
|
||||
**Requirements:** [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Git](https://git-scm.com/), [Bun](https://bun.sh/) v1.0+
|
||||
|
||||
### Step 1: Install on your machine
|
||||
|
||||
Open Claude Code and paste this. Claude does the rest.
|
||||
|
||||
> Install gstack: run **`git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`** then add a "gstack" section to CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, and lists the available skills: /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /qa-design-review, /setup-browser-cookies, /retro, /document-release. Then ask the user if they also want to add gstack to the current project so teammates get it.
|
||||
|
||||
### Step 2: Add to your repo so teammates get it (optional)
|
||||
|
||||
> Add gstack to this project: run **`cp -Rf ~/.claude/skills/gstack .claude/skills/gstack && rm -rf .claude/skills/gstack/.git && cd .claude/skills/gstack && ./setup`** then add a "gstack" section to this project's CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, lists the available skills: /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /qa-design-review, /setup-browser-cookies, /retro, /document-release, and tells Claude that if gstack skills aren't working, run `cd .claude/skills/gstack && ./setup` to build the binary and register skills.
|
||||
|
||||
Real files get committed to your repo (not a submodule), so `git clone` just works. Everything lives inside `.claude/`. Nothing touches your PATH or runs in the background.
|
||||
|
||||
## See it work
|
||||
|
||||
@@ -76,8 +107,6 @@ Claude: Tests: 42 → 51 (+9 new)
|
||||
|
||||
One feature. Seven commands. The agent reframed the product, ran an 80-item design audit, drew the architecture, wrote 2,400 lines of code, found a race condition I would have missed, auto-fixed two issues, opened a real browser to QA test, found and fixed a bug I didn't know about, wrote 9 tests, and generated a regression test. That is not a copilot. That is a team.
|
||||
|
||||
---
|
||||
|
||||
## The team
|
||||
|
||||
| Skill | Your specialist | What they do |
|
||||
@@ -98,8 +127,6 @@ One feature. Seven commands. The agent reframed the product, ran an 80-item desi
|
||||
|
||||
**[Deep dives with examples and philosophy for every skill →](docs/skills.md)**
|
||||
|
||||
---
|
||||
|
||||
## What's new and why it matters
|
||||
|
||||
**Design is at the heart.** `/design-consultation` doesn't just pick fonts. It researches what's out there in your space, proposes safe choices AND creative risks, generates realistic mockups of your actual product, and writes `DESIGN.md` — and then `/design-review` and `/plan-eng-review` read what you chose. Design decisions flow through the whole system.
|
||||
@@ -112,8 +139,6 @@ One feature. Seven commands. The agent reframed the product, ran an 80-item desi
|
||||
|
||||
**`/document-release` is the engineer you never had.** It reads every doc file in your project, cross-references the diff, and updates everything that drifted. README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, TODOS — all kept current automatically.
|
||||
|
||||
---
|
||||
|
||||
## 10 sessions at once
|
||||
|
||||
gstack is powerful with one session. It is transformative with ten.
|
||||
@@ -122,53 +147,21 @@ gstack is powerful with one session. It is transformative with ten.
|
||||
|
||||
One person, ten parallel agents, each with the right cognitive mode. That is a different way of building software.
|
||||
|
||||
---
|
||||
|
||||
## Install — takes 30 seconds
|
||||
|
||||
**Requirements:** [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Git](https://git-scm.com/), [Bun](https://bun.sh/) v1.0+
|
||||
|
||||
### Step 1: Install on your machine
|
||||
|
||||
Open Claude Code and paste this. Claude does the rest.
|
||||
|
||||
> Install gstack: run `git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup` then add a "gstack" section to CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, and lists the available skills: /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /document-release. Then ask the user if they also want to add gstack to the current project so teammates get it.
|
||||
|
||||
### Step 2: Add to your repo so teammates get it (optional)
|
||||
|
||||
> Add gstack to this project: run `cp -Rf ~/.claude/skills/gstack .claude/skills/gstack && rm -rf .claude/skills/gstack/.git && cd .claude/skills/gstack && ./setup` then add a "gstack" section to this project's CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, lists the available skills: /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /document-release, and tells Claude that if gstack skills aren't working, run `cd .claude/skills/gstack && ./setup` to build the binary and register skills.
|
||||
|
||||
Real files get committed to your repo (not a submodule), so `git clone` just works. Everything lives inside `.claude/`. Nothing touches your PATH or runs in the background.
|
||||
|
||||
---
|
||||
|
||||
```
|
||||
+----------------------------------------------------------------------------+
|
||||
| |
|
||||
| Are you a great software engineer who wants to ship 10K+ LOC/day? |
|
||||
| |
|
||||
| Come work at YC: ycombinator.com/software |
|
||||
| |
|
||||
| Extremely competitive salary and equity. |
|
||||
| Now hiring in San Francisco, Dogpatch District. |
|
||||
| Come join the revolution. |
|
||||
| |
|
||||
+----------------------------------------------------------------------------+
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Come ride the wave
|
||||
|
||||
This is **free, MIT licensed, open source, available now.** No premium tier. No waitlist. No strings.
|
||||
|
||||
I open sourced how I do development and I am actively upgrading my own software factory here. You can fork it and make it your own. That's the whole point. I want everyone on this journey.
|
||||
|
||||
Same tools, different outcome — because gstack gives you structured roles and review gates, not generic agent chaos. That governance is the difference between shipping fast and shipping reckless.
|
||||
|
||||
The models are getting better fast. The people who figure out how to work with them now — really work with them, not just dabble — are going to have a massive advantage. This is that window. Let's go.
|
||||
|
||||
**[github.com/garrytan/gstack](https://github.com/garrytan/gstack)** — MIT License
|
||||
Thirteen specialists. All slash commands. All Markdown. All free. **[github.com/garrytan/gstack](https://github.com/garrytan/gstack)** — MIT License
|
||||
|
||||
---
|
||||
> **We're hiring.** Want to ship 10K+ LOC/day and help harden gstack?
|
||||
> Come work at YC — [ycombinator.com/software](https://ycombinator.com/software)
|
||||
> Extremely competitive salary and equity. San Francisco, Dogpatch District.
|
||||
|
||||
## Docs
|
||||
|
||||
@@ -188,6 +181,16 @@ The models are getting better fast. The people who figure out how to work with t
|
||||
|
||||
**Stale install?** Run `/gstack-upgrade` — or set `auto_upgrade: true` in `~/.gstack/config.yaml`
|
||||
|
||||
**Claude says it can't see the skills?** Make sure your project's `CLAUDE.md` has a gstack section. Add this:
|
||||
|
||||
```
|
||||
## gstack
|
||||
Use /browse from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.
|
||||
Available skills: /plan-ceo-review, /plan-eng-review, /plan-design-review,
|
||||
/design-consultation, /review, /ship, /browse, /qa, /qa-only, /qa-design-review,
|
||||
/setup-browser-cookies, /retro, /document-release.
|
||||
```
|
||||
|
||||
## License
|
||||
|
||||
MIT. Free forever. Go build something.
|
||||
|
||||
Reference in New Issue
Block a user