ericrisco/rsc-harness / skills/gamedev-pathing
gamedev-pathing
VerifiedUse when making NPCs, enemies, or units navigate a level — grid vs waypoint vs navmesh, A*/JPS, navmesh baking and agent radius, off-mesh links, steering, RVO crowd avoidance, and flow fields in Godot 4.x, Unity, Unreal. NOT collision response or character controllers (that is gamedev-physics), NOT aggro or difficulty design (that is game-design).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.1 KB |
| evals/README.md | markdown | 1.2 KB |
| evals/cases.yaml | config | 5.0 KB |
| references/navmesh-workflow.md | markdown | 6.7 KB |
| references/search-algorithms.md | markdown | 6.6 KB |
| references/steering-and-avoidance.md | markdown | 6.5 KB |
evals/README.md
View on GitHub# Eval harness — `gamedev-pathing` skill
`cases.yaml` is a human/CI-readable trigger-and-capability spec, not an automated runner. It asserts two
things. **Triggering**: the skill fires on real navigation asks — engine-specific ("enemies stuck in
Godot 4", "Unreal navmesh won't see a spawned crate"), representation/algorithm theory (A* heuristics,
grid vs navmesh), crowd/avoidance ("units dance and pile up"), and a Catalan off-mesh-link phrasing — and
stays quiet on near-misses that route to `gamedev-physics` (collision response), `game-design` (what the
AI decides), `unity` (lightmap baking — the "bake" false friend), `godot` (animation state machine), and
`gamedev-multiplayer` (netcode). **Capability**: with `SKILL.md` + references loaded, the answer uses
the current Godot 4.x API (`target_position`, `get_next_path_position`, `velocity_computed` — never the
Godot-3 names), separates global pathfinding from per-frame steering, and reaches for a flow field for
many-agents-to-one-goal. Run 3–5 trials per prompt (LLM routing is non-deterministic); a prompt passes on
a majority. Judge `capability` by reading the output against `must_include`; the with-skill answer should
clearly beat a no-skill baseline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |