devex-review

Audit developer experience by navigating docs, running getting started flows, and evaluating CLI help text.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill devex-review-makyua-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/devex-review
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill devex-review-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams evaluate the real developer experience by simulating how a new user would navigate docs, run the getting started flow, and work with the CLI. It surfaces friction points, collects evidence like timings, screenshots, and CLI outputs, and translates them into actionable recommendations. The end result is a DX scorecard that makes onboarding and developer workflows measurable.

Core Features & Use Cases

  • Browse-driven onboarding testing: navigates docs, setup steps, and command-line flows to identify stuck points.
  • Evidence generation: records timings, screenshots, error messages, and CLI help quality to justify scores.
  • Plan-aware comparison: compares results against existing plan-devex-review benchmarks when available to show progress.
  • Improvement suggestions: outputs concrete next steps for onboarding, docs, and tooling.

Quick Start

Run the devex-review skill to perform a live developer experience audit using the browse tool.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I perform a developer experience audit for onboarding flows?

A developer experience audit simulates new user interactions by navigating docs, running the getting started flow, and testing CLI help text to identify friction points and generate a DX scorecard.

What is a browse-driven DX scorecard and how does it work?

A browse-driven DX scorecard works by using a browse tool to simulate real user interactions, capturing evidence like timings, screenshots, and error messages to evaluate developer workflows and onboarding friction.

How do I test CLI help text quality and getting started documentation?

You can test CLI help text quality and getting started flows by running a live DX audit that navigates setup steps, executes command-line operations, and records friction points with evidence for evaluation.

Can I compare my latest DX audit results against previous benchmarks?

You can compare DX audit results against existing plan-devex-review benchmarks when available, allowing you to track progress on onboarding friction points and developer workflow improvements over time.

What evidence is captured during a developer experience review?

A developer experience review captures evidence including timings, screenshots, error messages, and CLI help quality to justify DX scores and produce actionable onboarding and tooling recommendations.

Are there limitations to using automated browse tools for DX testing?

Automated browse tools for DX testing simulate user navigation but may not capture subjective developer frustrations, meaning complex environment setup issues outside the browser could be missed.