uefn-verse

Files (2)

• SKILL.md
• verse-rules.md · references/

SKILL.md (first lines)

# UEFN Verse

Write the least Verse that makes the slice clear and maintainable.

## Rules

- Prefer existing Creative devices when they already express the behavior.
- Use Verse for orchestration, game state, rules, and gaps between devices.
- Keep one obvious owner for important state.
- Give functions one clear job.
- Prefer descriptive names over clever names.
- Prefer `@editable` for scene dependencies and designer-tuned configuration.
- Subscribe to events in an obvious setup location.
- Keep event handlers short; delegate meaningful behavior to named functions when it improves clarity.
- Log meaningful transitions when they are useful for debugging or proof.
- Compile after a small meaningful change.
- Do not invent APIs. Discover or verify current APIs when uncertain.
- Do not create architecture for hypothetical future features.

See [references/verse-rules.md](references/verse-rules.md) for the code-review questions.

From RCSnyder/open-uefn-kit, MIT.

More from RCSnyder/open-uefn-kit