Skip to content
Back to skills

Level Flow

ASecurity

Design and evaluate player flow through spaces using goals, orientation, choice, gating, traversal, landmarks, backtracking, recovery, and pacing.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 11, 2026
ai-agentsgoapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill level-flow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Level Flow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Level Flow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-level-flow/badge)](https://www.skillsdirectory.com/skills/dadmin88-level-flow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: level-flow
description: Design and evaluate player flow through spaces using goals, orientation, choice, gating, traversal, landmarks, backtracking, recovery, and pacing.
---
# Level Flow

Use when a level or playable space needs coherent navigation and progression.

## Procedure
1. Define the player's goals, abilities, entry state, expected knowledge, and required sequence or freedom before shaping routes.
2. Map critical path, optional paths, loops, shortcuts, gates, transitions, and return routes in terms of player decisions rather than geometry alone.
3. Use sightlines, landmarks, lighting, composition, affordances, and environmental storytelling to support orientation.
4. Control decision density so choices feel meaningful without becoming constant navigational noise.
5. Check traversal metrics such as distance, speed, verticality, jump or climb requirements, chokepoints, and accessibility options relevant to the game.
6. Plan failure or recovery and backtracking so mistakes do not create accidental dead ends or excessive repetition.
7. Prototype with simple geometry and play through without designer narration to identify confusion.
8. Iterate from observed player behavior and telemetry or playtest evidence, not only intended route diagrams.

## Decision rules
- Players experience flow as decisions and perception, not a top-down map.
- Signposting should support discovery without eliminating all exploration.
- Critical path clarity and optional exploration can coexist.
- Do not polish art before blockout proves the route structure.

## Quality gate
Level flow is ready when representative players can understand goals and navigate without designer intervention, choices and optional routes are intentional, traversal and recovery work with player abilities, and observed play confirms the intended progression rather than only the designer's map.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…