naive-ux-check

Run persona-specific manual UX tests and log redacted feedback.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/ByronWilliamsCPA/cyo-adventure --skill naive-ux-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naive-ux-check
Source: https://github.com/ByronWilliamsCPA/cyo-adventure/tree/main/.claude/skills/naive-ux-check
Command: npx skills add https://github.com/ByronWilliamsCPA/cyo-adventure --skill naive-ux-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the difficulty of maintaining consistent, high-quality user experience testing for complex, multi-persona web applications by providing a structured, repeatable framework for manual UX audits.

Core Features & Use Cases

  • Persona-Based Prompting: Orchestrates 17 distinct UX scenarios across Kid, Guardian, and Admin personas to ensure role-specific features are intuitive.
  • Standardized Reporting: Enforces a mandatory redaction and logging workflow to capture friction points and dead-ends without exposing sensitive user data.
  • Use Case: Before a major release, use this skill to perform a comprehensive pass-through of the auth-gate and story-request flows to identify and document usability bottlenecks.

Quick Start

Invoke the naive-ux-check skill to begin the next unrun scenario for the current target environment.

Frequently Asked Questions about naive-ux-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a manual UX audit for multi-persona web applications?

A manual UX audit for multi-persona web applications requires persona-specific scenario prompts to navigate role-based interfaces, identifying friction points and dead-ends while logging redacted findings reports for consistent quality testing.

What is persona-based usability testing for kid, guardian, and admin roles?

Persona-based usability testing evaluates role-specific features by orchestrating distinct scenarios for kid, guardian, and admin users, ensuring interfaces remain intuitive across different permission levels and navigation flows.

How do I document friction points during usability testing without exposing sensitive data?

Document friction points during usability testing by enforcing a mandatory redaction and logging workflow, capturing navigation dead-ends in local dated findings reports without exposing sensitive user data.

Can I use a browser extension to facilitate manual UX comprehension testing?

Yes, manual UX comprehension testing requires a human operator to interface with a browser extension, maintaining a local directory of dated findings reports while executing scenario-based usability checks.

What's the best way to identify navigation dead-ends before a major release?

Identify navigation dead-ends before release by performing a comprehensive pass-through of auth-gate and story-request flows using structured persona-based scenarios, documenting usability bottlenecks in standardized reports.

Does this UX testing approach work for complex multi-persona interfaces?

Yes, this UX testing approach targets complex multi-persona web applications by providing a structured, repeatable framework with 17 distinct scenarios across kid, guardian, and admin personas to maintain consistent testing quality.