ux-doc-pass

To improve onboarding docs and reduce first-run confusion, perform a UX-focused review of contributor-facing documentation to surface ambiguities, missing prerequisites, and unclear terminology. This process generates actionable recommendations and tighter wording for better readability.

The best way to review a repository README for usability issues is to run a UX doc pass that prioritizes critical files like README.md and onboarding guides. This surfaces readability problems and enforces a structured Markdown guide with Quick Start instructions.

You can check for missing prerequisites in developer documentation by applying a UX doc pass to critical files like authoring guides and runtime-loading docs. This surfaces readability issues and enforces a three-section Markdown guide with a Quick Start instruction.

A UX documentation review requires no specific dependencies or components to function. You can run the UX doc pass directly on repository files like README.md and contributor guides to return a prioritized list of readability improvements.

When fixing contributor-facing documentation, prioritize critical files such as README.md, docs/adoption-onboarding.md, docs/authoring-guide.md, docs/runtime-loading.md, and docs/testing/smoke-tests.md to rapidly improve GitHub readability and contributor confidence.

Your onboarding documentation needs a three-section Markdown guide to satisfy the frontmatter requirement for a name and description in SKILL.md. This structure enforces Quick Start instructions, which reduces first-run confusion for new contributors.