agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/design/procgen-design/SKILL.md

procgen-design

Skill105 starsChanged 8 months agoMITView on GitHub

Design procedural content systems with seeds, constraints, and validation gates so generated output stays fun and shippable.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 63
  2. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 64

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Procedural Generation Design

Purpose

Design procedural content systems with seeds, constraints, and validation gates so generated output stays fun and shippable.

Use When

  • levels, loot, encounters, or world content will be generated rather than authored
  • generated output quality varies wildly and needs constraints
  • determinism, seed sharing, or reproducibility matters for testing or community features

Inputs

  • content type and generation goals (variety, replayability, scale)
  • authored content that generation must complement
  • difficulty and pacing constraints
  • determinism and seed requirements

Process

  1. define what generation must guarantee versus what may vary
  2. choose the authored-versus-generated split per content type
  3. specify seed handling, determinism scope, and reproducibility rules
  4. define validation gates that reject degenerate output before the player sees it
  5. plan telemetry to detect quality drift in shipped generation
  6. define how designers tune generators without touching generation code

Outputs

  • generation constraint specification
  • seed and determinism rules
  • validation gate definitions with rejection criteria
  • tuning surface for designers

Quality Bar

  • supports the core fantasy and player goals
  • defines readable rules, edge cases, and feedback
  • creates concrete hooks for tuning, telemetry, and QA

Common Failure Modes

  • generation without validation gates, shipping degenerate output
  • non-deterministic systems that QA cannot reproduce
  • variety goals that ignore pacing and difficulty constraints

Related Agents

  • systems-designer
  • level-designer
  • gameplay-programmer

Related Commands

  • procgen-design
  • level-beat
  • qa-plan

Related Skills

  • level-design
  • core-loop-design

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

Download now (ZIP)

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.

Check your setup, free