agentleFS
Sign inStart free
Kevin-Liu-01Kevin-Liu-01/Claude-of-Tanks/src/SKILL.md

src-skill

Skill531 starsChanged 3 months agoMITView on GitHub

Navigate browser boot and shared source contracts while preserving subsystem and bundle boundaries.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Kevin-Liu-01/Local-Search★ 16same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use the nearest child SKILL.md for implementation details.

    line 11
  2. Very specific:

    Read docs/SYSTEMS.md and docs/DECISIONS.md for cross-subsystem contracts.

    line 21
  3. Very specific:

    Keep main.ts surgical: compose existing owners rather than duplicating their state, lifecycle, or gameplay policy.

    line 26
  4. Distinctive:

    Keep simulation/network logic Node-runnable and deterministic.

    line 28
  5. Distinctive:

    Keep product totals dependency-free and verify them against registries.

    line 33

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

claude-of-tanks / src

Purpose

<!-- agent-docs:fill:purpose -->

Compose the game and its public pages from independently owned subsystems. Use the nearest child SKILL.md for implementation details; this directory's root files supply boot wiring and small shared contracts.

Mental model & key files

<!-- agent-docs:fill:model -->

main.ts wires strict typed lifecycle owners from app/, game/, and the rendering subsystems. runtimeTypes.ts defines unvalidated runtime and JSON boundary values, not domain models. productStats.ts supplies dependency-free totals and template tokens; authorship.ts supplies first-party attribution. analytics.ts is deferred public-page telemetry, separate from game boot. Read docs/SYSTEMS.md and docs/DECISIONS.md for cross-subsystem contracts.

Patterns to follow / invariants

<!-- agent-docs:fill:patterns -->
  • Keep main.ts surgical: compose existing owners rather than duplicating their state, lifecycle, or gameplay policy.
  • Keep simulation/network logic Node-runnable and deterministic; DOM/WebGL belongs to presentation. Rendering does not authorize combat outcomes.
  • Preserve demand-loaded phase boundaries and allocation-neutral frame loops.
  • Narrow RuntimeValue at subsystem boundaries before accessing fields; keep domain-specific types with their actual owner.
  • Keep product totals dependency-free and verify them against registries; do not pull fleet/map builders into lightweight public or boot modules.

Common tasks → first action

<!-- agent-docs:fill:tasks -->
  • Boot or phase wiring: read app/SKILL.md and game/SKILL.md, then the affected lifecycle owner's selftest.
  • Product counts: run node src/productStats.selftest.mjs.
  • Authorship/provenance: inspect NOTICE.md, docs/ATTRIBUTION.md, and run npm run attribution:check.
  • Shared typed integration: run npm run typecheck plus focused owner tests; use package.json for current full build/test commands.

Gotchas

<!-- agent-docs:fill:gotchas -->

src/docs/ is the player-facing manual implementation; repository docs/ contains engineering documentation. Public pages must not import game boot, and the latency-sensitive game entry must not schedule public analytics.

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