Skip to content

ericrisco/rsc-harness / skills/level-design

level-design

Verified

Use when designing a game level's space — blockout/greybox layout, pacing that drags or spikes, guiding lost players without waypoints, encounter and arena progression, or secret placement. NOT mechanics or economy (that is `game-design`), NOT story beats (that is `game-storytelling`), NOT engine tooling like nav meshes or lightmaps (that is `godot`/`unity`/`unreal`).

FileKindSize
SKILL.mdskill md14.7 KB
evals/README.mdmarkdown2.0 KB
evals/cases.yamlconfig6.4 KB
references/blockout-to-art.mdmarkdown6.1 KB
references/guidance-and-readability.mdmarkdown7.7 KB
references/pacing-and-encounters.mdmarkdown7.0 KB

evals/README.md

View on GitHub
# Eval harness — level-design

These evals assert two things about the `level-design` skill. **Triggering:** it
fires on level layout, pacing, encounter, guidance, and reward requests, and
stays out of systemic mechanic/economy design (`game-design`), narrative
(`game-storytelling`), and engine-specific level tooling (`godot`/`unity`/
`unreal`). **Capability:** when engaged, it delivers the craft — the
blockout→art pipeline, the sawtooth intensity graph with breathers, the
introduce→develop→twist→combine teaching pattern, light/color/affordance
guidance, and observe-don't-coach playtesting — rather than generic advice.

## How to run

Run through an agent harness with skills loadable on demand; `cases.yaml` is the
fixture. Use the same model for every trial; vary only which skills are loaded.

- **Triggering:** load the full catalog so the agent can route to siblings; feed
  each `should_trigger` / `should_not_trigger` prompt verbatim and record which
  skill fires. Run 3–5 trials per prompt (the choice is stochastic).
  - Pass: `should_trigger` selects **level-design** in the majority of trials;
    `should_not_trigger` does not (ideally routes to the listed `route_to`).
  - Bar: **≥90%** trigger accuracy across all prompts.
- **Capability:** run each scenario WITH only level-design loaded vs WITHOUT any
  skill (baseline), 3 times each. Grade responses against the `must_include`
  rubric, one point per checkable item genuinely present.
  - Bar: WITH covers **≥80%** of items on average AND beats WITHOUT by **≥25**
    percentage points (a skill that doesn't move the needle fails).

## Notes / honesty

- LLM-graded and stochastic — re-run on edits; treat small deltas as noise.
- `route_to` targets assume the sibling skills (`game-design`,
  `game-storytelling`, `godot`, `unity`, `unreal`) exist in the catalog; a
  missing sibling can cause a near-miss to mis-route without it being a
  level-design fault — note it, don't count it against this skill.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall