search-router
CLAUDE.md0 starsChanged 8 months agoMITView on GitHub
Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools. Available skills: - /office-hours — brainstorming a new idea - /plan-ceo-review — reviewing a plan (strategy) - /plan-eng-review — reviewing a plan (architecture) - /plan-design-review — reviewing a plan (design) - /design-consultation — creating a design system - /review — code review before merge - /ship — ready to deploy / create PR - /land-and-deploy — land and deploy - /canary — canary deployment - /benchmark…
In this repository3 other files it gives its agents.
- .claude/skills/gstack/AGENTS.mdAGENTS.md
- .claude/skills/gstack/CLAUDE.mdCLAUDE.md
- gstackSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Use the /browse skill from gstack for all web browsing.
- Very specific: line 34
If gstack skills aren't working, run cd .claude/skills/gstack && ./setup to build the binary and register skills.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Search Router
gstack
Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.
Available skills:
/office-hours— brainstorming a new idea/plan-ceo-review— reviewing a plan (strategy)/plan-eng-review— reviewing a plan (architecture)/plan-design-review— reviewing a plan (design)/design-consultation— creating a design system/review— code review before merge/ship— ready to deploy / create PR/land-and-deploy— land and deploy/canary— canary deployment/benchmark— benchmarking/browse— web browsing (use this for ALL web browsing)/qa— testing the app/qa-only— QA only/design-review— visual design audit/setup-browser-cookies— set up browser cookies/setup-deploy— set up deployment/retro— weekly retrospective/investigate— debugging errors/document-release— post-ship doc updates/codex— second opinion or adversarial code review/careful— working with production or live systems/freeze— scope edits to one module/directory/guard— maximum safety mode/unfreeze— removing edit restrictions/gstack-upgrade— upgrade gstack to latest version
If gstack skills aren't working, run cd .claude/skills/gstack && ./setup to build the binary and register skills.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.