Tayhlow8/Caixa-D-gua-website-2026 / .agents/skills/gstack
gstack
FlaggedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
openclaw/agents-gstack-section.md
View on GitHub## Coding Tasks (gstack)
### Rules (non-negotiable)
1. **Always spawn, never redirect.** When user asks to use ANY gstack skill,
ALWAYS spawn a Claude Code session via sessions_spawn. Never tell user to
open Claude Code himself. Never say "this needs to run in Claude Code."
Never say "you'll need to open Claude Code for that." Just do it.
2. **Resolve the repo.** If user names a repo or project, set the working
directory to that repo path. If the repo path isn't known, ask which
repo — don't punt to telling the user to open Claude Code.
3. **Autoplan runs end-to-end.** For /autoplan specifically: spawn the session,
let it run the full review pipeline (CEO → design → eng), and when it
finishes, report the plan back here in chat. Write the plan to memory so
the user can find it later. User should never have to leave Telegram.
### Dispatch Routing
When asked for coding work, pick the dispatch tier:
**SIMPLE:** "fix this typo," "update that config," single-file changes
→ sessions_spawn(runtime: "acp", prompt: "<just the task>")
**MEDIUM:** multi-file features, refactors, skill edits
→ sessions_spawn(runtime: "acp", prompt: "<gstack-lite content>\n\n<task>")
**HEAVY:** needs a specific gstack methodology
→ sessions_spawn(runtime: "acp", prompt: "Load gstack. Run /qa https://...")
Skills: /cso, /review, /qa, /ship, /investigate, /design-review, /benchmark, /gstack-upgrade
**FULL:** build a complete feature, multi-day scope, needs planning + review
→ sessions_spawn(runtime: "acp", prompt: "<gstack-full content>\n\n<task>")
Claude Code runs: /autoplan → implement → /ship → report back
**PLAN:** user wants to plan a Claude Code project, spec out a feature, or design
something before any code is written
→ sessions_spawn(runtime: "acp", prompt: "<gstack-plan content>\n\n<task>")
Claude Code runs: /office-hours → /autoplan → saves plan file → reports back
Persist the plan link to memory/knowledge store.
When the user is ready to implement, spawn a new FULL session pointing at the plan.
### Decision Heuristic
- Can it be done in <10 lines of code? → **SIMPLE**
- Does it touch multiple files but the approach is obvious? → **MEDIUM**
- Does the user name a specific skill (/cso, /review, /qa)? → **HEAVY**
- "Upgrade gstack", "update gstack" → **HEAVY** with `Run /gstack-upgrade`
- Is it a feature, project, or objective (not a task)? → **FULL**
- Does the user want to PLAN something without implementing yet? → **PLAN**
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |