gstack Web Skills

A collection of 12 engineering workflow skills adapted from the gstack CLI for use in the Claude web app (claude.ai). These skills turn Claude into a structured engineering partner — covering everything from brainstorming and planning to code review, QA, shipping, and retrospectives. No terminal required.

---

How to Install

Option A — Upload Skill Folders (recommended)

1. Download gstack-web-skills.zip and unzip it.
2. In claude.ai, go to Customize → Skills.
3. Upload each skill folder (e.g. office-hours/, review/, qa/). Each folder contains a SKILL.md that Claude reads automatically.
4. Claude will auto-trigger skills based on what you ask — or invoke directly with /skill-name.

Option B — Upload Individual SKILL.md Files

1. Pick the skill folders you want.
2. Upload each folder’s SKILL.md as a skill. Claude matches tasks to skills via the description field in each file’s frontmatter.

How it works: Each SKILL.md has a name and description in its frontmatter. Claude sees all skill descriptions, and when your request matches, it loads that skill’s instructions automatically. No manual routing needed.

---

Skills

Ideation

Planning

Review

Quality & Shipping

Retrospective

---

Recommended Workflow Order

/office-hours          → Clarify the idea
        ↓
/design-consultation   → Define the design system (if UI work)
        ↓
/plan-ceo-review       → Stress-test the plan (strategy)
/plan-eng-review       → Stress-test the plan (engineering)
/plan-design-review    → Stress-test the plan (design)
        ↓
    [Build it]
        ↓
/review                → Pre-landing code review
/design-review         → Visual QA (if UI work)
/qa                    → Test and fix
        ↓
/ship                  → Merge, version, PR
/document-release      → Sync documentation
        ↓
/retro                 → Reflect on the week

You don’t have to use every skill — pick the ones that fit your workflow.

---

Quick Start

Scenario: You have an idea for a new feature and want to go from concept to shipped code.

1. Start a conversation in your Claude Project.
2. Type: /office-hours — Claude runs a YC-style session, asking you tough questions about your idea and producing a structured design doc.
3. When you have a plan, type: /plan-eng-review and paste your plan — Claude reviews it for architecture gaps, missing tests, and performance risks.
4. After building, paste your code changes and type: /review — Claude does a two-pass code review and fixes issues directly.
5. Run /qa to validate test coverage and code health.
6. Finally, type /ship to walk through the shipping checklist.

Each skill guides you step-by-step with questions and structured output. Just follow the prompts.

---

File Structure

├── README.md                              ← you are here
├── gstack-web-skills/
│   ├── office-hours/
│   │   └── SKILL.md                       ← 💡 Ideation
│   ├── design-consultation/
│   │   └── SKILL.md                       ← 📐 Planning
│   ├── plan-ceo-review/
│   │   └── SKILL.md                       ← 📐 Planning
│   ├── plan-eng-review/
│   │   └── SKILL.md                       ← 📐 Planning
│   ├── plan-design-review/
│   │   └── SKILL.md                       ← 📐 Planning
│   ├── review/
│   │   └── SKILL.md                       ← 🔍 Review
│   ├── investigate/
│   │   └── SKILL.md                       ← 🔍 Review
│   ├── design-review/
│   │   └── SKILL.md                       ← 🔍 Review
│   ├── qa/
│   │   └── SKILL.md                       ← ✅ Quality
│   ├── ship/
│   │   └── SKILL.md                       ← 🚀 Shipping
│   ├── document-release/
│   │   └── SKILL.md                       ← 🚀 Shipping
│   └── retro/
│       └── SKILL.md                       ← 🔄 Retrospective
└── gstack-web-skills.zip                  ← ready-to-download package

Each skill is a self-contained folder with a SKILL.md. This matches the Claude Skills standard — one folder per skill, auto-triggered by description matching.

---

Contributing

Found a way to make a skill better? PRs welcome. Each skill must:

• Live in its own folder with a SKILL.md
• Use only name and description in frontmatter
• Write description as a trigger phrase (what user phrases should activate it)
• Stay under 500 lines / 3000 words per SKILL.md

---

Adapted from gstack by Garry Tan. Web-adapted for Claude Projects.