## gstack

Use the `/browse` skill from gstack for all web browsing. Never use `mcp__claude-in-chrome__*` tools.

Available gstack skills:
- /office-hours
- /plan-ceo-review
- /plan-eng-review
- /plan-design-review
- /design-consultation
- /design-shotgun
- /design-html
- /review
- /ship
- /land-and-deploy
- /canary
- /benchmark
- /browse
- /connect-chrome
- /qa
- /qa-only
- /design-review
- /setup-browser-cookies
- /setup-deploy
- /retro
- /investigate
- /document-release
- /codex
- /cso
- /autoplan
- /careful
- /freeze
- /guard
- /unfreeze
- /gstack-upgrade
- /learn

## Testing Methodology

- When performing tests do not deprecate to simpler testing methods - work through the problem and if, need be, download packages to aid in your debugging.
- never deprecate tests or simplify them - ALWAYS ALWAYS ALWAYS work through issues. Do not just make tests simpler just so you can clear the hurdle. If a problem is difficult work through it! Find the source of the problem and fix it EVERY TIME!

## GitHub Workflow

- When pushing to GitHub, use SSH (key: SHA256:7X+8TXzSjBE88FP41JQClH1uHWjLbKP/LEAVTKSIapQ) commit and push changes.
- Before pushing to GitHub, always audit the repo to make sure that only essential files are located in the root directory, all other files are saved to logical subfolders, and make sure that no unnecessary test or irrelevant to-do/roadmap files are in the repo. Always make sure the repo is clean and organized enough for an external audit by either investors or developers.

## Development Best Practices

- Whenever possible/appropriate edit existing files rather than creating new ones. Otherwise, you may create a daisy chain of dependencies that turn into knots when trying to debug.