devex-review

Audits live developer experience by testing docs, onboarding flows, and CLI help output.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill devex-review-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/devex-review
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill devex-review-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developer experience is usually reviewed on paper, not tested in reality. This Skill runs a live DX audit: it navigates your docs, attempts the getting started flow, times time-to-hello-world (TTHW), screenshots error messages, and evaluates CLI help text, then produces an evidence-backed DX scorecard. ## Core Features & Use Cases - Live DX Testing: Uses a browse tool and bash to actually walk the onboarding flow instead of reading about it, capturing screenshots as evidence. - Eight-Dimension Scorecard: Scores Getting Started, API/CLI/SDK ergonomics, Error Messages, Documentation, Upgrade Path, Dev Environment, Community, and DX Measurement on a calibrated 0-10 rubric. - Boomerang Comparison: Compares live audit scores against prior /plan-devex-review plan-stage scores to flag where reality fell short of the plan. - Use Case: After shipping a developer-facing feature, run a DX audit to measure actual TTHW, catch confusing error messages, and verify docs search works before users bounce. ## Quick Start Ask the assistant to run a DX audit of your product's getting started flow and produce a scored report with evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I audit developer experience for my product?

Run a live DX audit that navigates your docs, attempts the getting started flow, and times each step. The audit scores eight dimensions including onboarding, error messages, and documentation on a 0-10 rubric with screenshot evidence.

What is a good time to hello world benchmark?

Under 2 minutes is champion tier and correlates with 3-4x higher adoption. Two to five minutes is competitive baseline, while over 10 minutes causes 50-70% of developers to abandon the product.

Can a DX audit test CLI tools and terminal output?

Browse-based testing covers web surfaces like docs and playgrounds, but CLI install friction and terminal output are tested via bash commands like running --help. Untestable dimensions are marked INFERRED from files rather than guessed.

How does the DX scorecard compare plan versus reality?

The boomerang comparison reads prior plan-stage DX review scores and diffs them against live audit scores per dimension. Any dimension where the live score falls more than 2 points below the plan score gets flagged.

What are the limitations of a live DX audit?

It cannot test email verification flows, auth requiring real credentials, offline behavior, build times, or IDE integration. These dimensions are scored from file evidence like CHANGELOG and README, and marked as INFERRED.