JaimeOrtegaxyz

Go Bigger — Testing skill for Claude Code

Testing community

Think bigger about an idea, repo, or project: find the cost constraints that drew its scope, test which collapsed, push the biggest viable expansions, and wall-test each.

How to install Go Bigger

This entry records only its repository, not the path inside it, so there is no exact command to give. Open JaimeOrtegaxyz/go-bigger and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Go Bigger does

Think bigger about an idea, repo, or project: find the cost constraints that drew its scope, test which collapsed, push the biggest viable expansions, and wall-test each. A Claude Code skill.

Alternatives in Testing

  • Webapp Testing — Test local web applications using Playwright for UI verification and debugging 94.1k ★
  • #29 — #52, #103) 92.5k ★
  • /test Routing — Vérifie le routing de commandes RTK sans exécution (dry-run) 25.5k ★

README

go-bigger

A Claude Code skill for thinking bigger about an idea, a repo, or a finished project.

Point it at a thing and it finds the cost constraints that drew that thing's scope, tests which ones quietly dissolved now that building got cheap, pushes the biggest viable expansions through the openings, and stress-tests each against the real wall. Inspired by the framing in Theo's [*It's time to go bigger.*](https://www.youtube.com/watch?v=WBT-z_-OPhw)

How it works

  • Point it at anything — a one-line idea, a repo/path, or a shipped product. It adapts how it reconstructs each.
  • Two unbreakable rules. Every expansion must name the specific constraint it kills and name its wall (trust, security, distribution, network effects, …). No "add AI, make it a platform" slop.
  • It wall-tests, then lands. Weak bets get killed, with reasons; the 1–2 survivors each come with what's now cheap, the real wall, and the smallest probe to test it.
  • It ends on a dare, not a recap, and saves a dated brief to ~/.claude/go-bigger/ — never into the target's repo.

Install

Copy the folder into your skills directory:

git clone https://github.com/JaimeOrtegaxyz/go-bigger.git ~/.claude/skills/go-bigger

Or into `.claude/skills/go-bigger/` inside a project to scope it there.

Full methodology — the nine lenses, the wall taxonomy, the output format — lives in `SKILL.md`.