agentleFS
AlomoesDataScienceAlomoesDataScience/claude-skills/.claude/skills/map-camera/SKILL.md

map-camera

Skill1 starsChanged 10 days agoNo licenceView on GitHub

How Claude drives a game's map camera so it can see everything it needs - find every camera control (in-game key list first, then manual), clear the screen of overlays, choose top-down vs angled view, zoom out for the whole board and in for detail, calibrate how far a held pan key moves the map (camcal.py) so photos overlap and moves land where intended, recentre by minimap or unit list, rotate/pitch to look behind woods and hills, and wait out camera transitions before photographing. Works with photo-map (panorama.py) and game-ui bgplay. Learned on Field of Glory II Medieval with the user, 2026-11-02. Use whenever a game has a movable map camera - before photographing the board, when something is hidden, off screen or covered, when photos don't stitch, or on a new game's first battle.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill 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.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.