soviet-doctrine
Skill1 starsChanged 12 days agoNo licenceView on GitHub
The Soviet school of operations and tactics for games, in Claude's words from FM 100-2-1 The Soviet Army - Operations and Tactics (1984) and a 1953 CIA report on the secret Soviet Field Manual 1948 (PU-48), Military Theory shelf - laws of war and principles of military art, offense as the normal form of combat, echelons (first, second, reserve) and 3:1 force ratios, attack from the march, frontal attack combined with flank attack and envelopment, forward detachments and the operational maneuver group, deep battle and tempo, norms vs initiative, encirclement as the end of every offensive, the five 1948 formations (wedge, inverted wedge, staggered, line), artillery as Queen of Battle. Contrasts with the US school (military-operations, military-doctrine). Use when playing an Eastern Front or Cold War game, modelling a Soviet-style AI or opponent, choosing an echeloned attack, or comparing doctrines for game design.
In this repository48 other files it gives its agents.
- army-logSkill
- battle-tacticsSkill
- borrow-from-gamesSkill
- check-skillsSkill
- combat-modelsSkill
- delegateSkill
- dice-mathSkill
- discord-logsSkill
- draw-mapSkill
- draw-movesSkill
- game-databaseSkill
- game-setupSkill
- game-sourcesSkill
- game-uiSkill
- generalize-learningSkill
- hand-backSkill
- idle-viewSkill
- install-windows-gamesSkill
- learn-from-tutorialsSkill
- learn-to-modSkill
- learn-to-playSkill
- loading-screensSkill
- manual-firstSkill
- map-cameraSkill
- map-measureSkill
- map-usageSkill
- military-doctrineSkill
- military-operationsSkill
- mod-diffSkill
- mod-docsSkill
- move-phasesSkill
- obs-recordSkill
- photo-mapSkill
- planningSkill
- rules-skillsSkill
- save-scumSkill
- scoutingSkill
- screeningSkill
- skills-managerSkill
- skill-syncSkill
- stream-panelSkill
- unit-combat-mathSkill
- video-watchSkill
- waiting-checklistSkill
- war-conceptsSkill
- war-languageSkill
- wiki-scoutSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
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.

