Skip to content

AI Skills

Massive Swarm System ships instruction files that teach an AI coding agent how to drive it. If you work with Claude Code, Cursor, Unity AI or any similar tool, pointing it at these files stops it from inventing a swarm system from scratch and gets it using the one you paid for.

What they are

An AI Skill is a plain markdown file, SKILL.md, written for an agent rather than for you. Each one covers a job you would ask for in a single sentence, and each states the exact menu paths, component names and default values verified against the runtime code.

They ship inside the package at:

Assets/CreativeSpore/MassiveSwarmSystem/AI/Skills/

Four skills ship, each in its own folder:

Skill What it covers
massive-swarm-system-setup-and-overview First-time setup, the install check, a working swarm in five steps, where every menu entry lives, and which of the other skills owns what.
massive-swarm-system-spawning-and-targets Spawner Director, ring and rect spawners, spawn modes, difficulty ramps, mixed hordes, the Pressure Recycler, and target priority.
massive-swarm-system-agents-and-vat Agent archetypes, the archetype wizard, the VAT Baker, batch bakes, and choosing between Animator and VAT animation.
massive-swarm-system-performance-and-navigation Swarm Settings, capacity, LOD tiers, grounding, body and obstacle blocking, the Surface Flow Field, and the stats overlay.

Pointing your agent at them

Agents do not find the folder on their own. It sits under Assets/, which no tool scans by default, so you have to tell yours where to look. This is a one-time step per project.

Claude Code

Project skills are read from .claude/skills/. Copy the four folders across, or link them so a package update keeps them current:

# From the project root in Command Prompt (cmd, not PowerShell), with Developer Mode on.
# Create the .claude\skills folder first if it does not exist.
mklink /D ".claude\skills\massive-swarm-system-setup-and-overview" "Assets\CreativeSpore\MassiveSwarmSystem\AI\Skills\massive-swarm-system-setup-and-overview"

Repeat for the other three, or copy the folders if you would rather not use links.

Any other agent

Most tools accept either a folder of instructions or a line in their project instructions file pointing at one. Add something like this to whatever file your tool reads at the start of a session:

Massive Swarm System ships AI skills at
Assets/CreativeSpore/MassiveSwarmSystem/AI/Skills/. Read the relevant SKILL.md
before writing any code that spawns, steers, or animates swarm agents.

Check it took

Ask your agent "how do I add a swarm to this scene?" before trusting it with real work. A correct answer names GameObject > Massive Swarm System > Swarm Manager and mentions that a target is needed. An answer that starts writing a MonoBehaviour with an Update loop means the skills are not being read.

What the skills will not let an agent do

Each skill carries a Boundaries section, and the agents skill adds a rule about where generated assets go. Those limits exist because working around them breaks the asset rather than extending it. An agent following the skills will refuse to:

  • Add a NavMeshAgent to swarm agents. Navigation runs through the Surface Flow Field.
  • Write an Update, FixedUpdate or LateUpdate per agent. Agents are entries in dense arrays, and a per-agent script collapses the frame rate at the counts this asset exists to reach.
  • Drive simulation state from a transform. Visuals follow the data and never lead it.
  • Write generated assets inside the package folder, where the next update would overwrite them.

If your agent proposes one of these, it either has not read the skills or has decided to override them. Both are worth stopping for.

Keeping them accurate

The skills carry the asset version they were verified against in their front matter, along with a last-verified date. They are updated alongside the code, so a skill and the release it ships in always describe the same thing.

They describe this asset only. Your own game code, your enemy stats and your wave design are yours, and no skill here makes assumptions about them.

Getting help

If an agent following a skill produces something wrong, that is worth reporting, because it usually means an instruction is unclear rather than that the agent misbehaved. Discord is the fastest route, and support@creativespore.com works too. Both are on the Help & Support page.