agentleFS
Sign inStart free
HexSleevesHexSleeves/tailscale-mcp/CLAUDE.md

tailscale-mcp

CLAUDE.md149 starsChanged 10 months agoMITView on GitHub

When the user's request matches an available skill, invoke it via the Skill tool. The skill has multi-step workflows, checklists, and quality gates that produce better results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is cheaper than a false negative. Key routing rules: - Product ideas, "is this worth building", brainstorming → invoke /office-hours - Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review - Architecture, "does this design make sense" →…

We split this CLAUDE.md into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user's request matches an available skill, invoke it via the Skill tool.

    line 4
  2. Distinctive:

    Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)

    line 18
  3. Distinctive:

    Update docs after shipping → invoke /document-release

    line 26
  4. Distinctive:

    Import cookies for authenticated testing → invoke /setup-browser-cookies

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Skill routing

When the user's request matches an available skill, invoke it via the Skill tool. The skill has multi-step workflows, checklists, and quality gates that produce better results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is cheaper than a false negative.

Key routing rules:

  • Product ideas, "is this worth building", brainstorming → invoke /office-hours
  • Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
  • Architecture, "does this design make sense" → invoke /plan-eng-review
  • Design system, brand, "how should this look" → invoke /design-consultation
  • Design review of a plan → invoke /plan-design-review
  • Developer experience of a plan → invoke /plan-devex-review
  • "Review everything", full review pipeline → invoke /autoplan
  • Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
  • Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
  • Code review, check the diff, "look at my changes" → invoke /review
  • Visual polish, design audit, "this looks off" → invoke /design-review
  • Developer experience audit, try onboarding → invoke /devex-review
  • Ship, deploy, create a PR, "send it" → invoke /ship
  • Merge + deploy + verify → invoke /land-and-deploy
  • Configure deployment → invoke /setup-deploy
  • Post-deploy monitoring → invoke /canary
  • Update docs after shipping → invoke /document-release
  • Weekly retro, "how'd we do" → invoke /retro
  • Second opinion, codex review → invoke /codex
  • Safety mode, careful mode, lock it down → invoke /careful or /guard
  • Restrict edits to a directory → invoke /freeze or /unfreeze
  • Upgrade gstack → invoke /gstack-upgrade
  • Save progress, "save my work" → invoke /context-save
  • Resume, restore, "where was I" → invoke /context-restore
  • Security audit, OWASP, "is this secure" → invoke /cso
  • Make a PDF, document, publication → invoke /make-pdf
  • Launch real browser for QA → invoke /open-gstack-browser
  • Import cookies for authenticated testing → invoke /setup-browser-cookies
  • Performance regression, page speed, benchmarks → invoke /benchmark
  • Review what gstack has learned → invoke /learn
  • Tune question sensitivity → invoke /plan-tune
  • Code quality dashboard → invoke /health

GBrain Configuration (configured by /setup-gbrain)

  • Engine: pglite
  • Config file: ~/.gbrain/config.json (mode 0600)
  • Setup date: 2026-04-24
  • MCP registered: yes
  • Memory sync: full (pending git repo setup — run gstack-brain-init to complete)
  • Current repo policy: read-write

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free