agentleFS
tanitaka-techtanitaka-tech/todome/.agents/skills/todome-server-navigator/SKILL.md

todome-server-navigator

Skill1 starsChanged 7 months agoMITView on GitHub

Navigate todome's server-side TypeScript structure and answer where handlers, payloads, storage logic, and AI flows live without dumping large code blocks. Use when locating WebSocket handlers, tracing server flows, or mapping server payloads to `client/src/types.ts`.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the main need is fast orientation inside server/ rather than editing.

    line 8
  2. Very specific:

    Start with rg to narrow the search, then read only the relevant files or sections.

    line 21
  3. Very specific:

    Do not dump long code excerpts.

    line 22
  4. Distinctive:

    When tracing a flow, present it as a small sequence such as:

    line 23
  5. Distinctive:

    When asked about payload shapes, summarize keys and relationships instead of copying object literals.

    line 28
  6. Very specific:

    Check client/src/types.ts only when the question involves cross-boundary payloads or mismatches.

    line 29
  7. Distinctive:

    If something is uncertain, say so instead of inferring.

    line 30
  8. Distinctive:

    Prefer a compact format like:

    line 34
  9. Distinctive:

    Keep answers investigation-focused.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

Todome Server Navigator

Use this skill when the main need is fast orientation inside server/ rather than editing.

What to Inspect

  • server/ws/handlers/ for message handlers
  • server/ws/endpoint.ts and server/ws/handlers/index.ts for dispatch flow
  • server/storage/ for persistence and migrations
  • server/ai/ for Claude Agent SDK integration and todo/profile/retro processing
  • server/github/ for git and sync behavior
  • server/types.ts and client/src/types.ts for payload/type alignment

Working Style

  • Start with rg to narrow the search, then read only the relevant files or sections.
  • Do not dump long code excerpts. Return file:line plus a short explanation.
  • When tracing a flow, present it as a small sequence such as:
    • entry handler
    • validation or normalization
    • storage/domain call
    • broadcast/response
  • When asked about payload shapes, summarize keys and relationships instead of copying object literals.
  • Check client/src/types.ts only when the question involves cross-boundary payloads or mismatches.
  • If something is uncertain, say so instead of inferring.

Output Rules

  • Prefer a compact format like:
    • 場所: server/ws/handlers/message.ts:12
    • 要点: ...
    • 関連: client/src/types.ts:88
  • Keep answers investigation-focused. Do not edit files unless the user asks for changes.

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.