player-friction-reviewer

To document player friction, you can systematically identify issues like tutorial overload and UI blocking, then log findings to a structured markdown file using provided scaffolding scripts and templates for auditable tracking.

Player friction refers to obstacles users encounter during onboarding or UI interactions, such as hidden rules or tutorial overload, which disrupt the player experience and require systematic identification and logging for resolution.

You track UI friction issues by logging them into a centralized markdown document with a dated, structured format, maintaining a change history to ensure auditability across onboarding sequences and UI guidance reviews.

Yes, you can generate a player friction review document by running a scaffold tool that utilizes markdown templates to create or append structured findings directly into your game documentation directory.

Common sources of player friction include tutorial overload, hidden rules, and UI blocking strategies, which can be surfaced by systematically reviewing onboarding flows and tutorial sequences for actionable issues.

No specific dependencies are required to run the player friction logging tool, as it operates using self-contained scripts and markdown asset templates to scaffold and extend the review documentation.