devex-review

Audit developer onboarding flows and CLI usability with evidence-based DX scorecards.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/nexus-finance --skill devex-review-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/Chang-Shih-Yung/nexus-finance/tree/main/.claude/skills/gstack/devex-review
Command: npx skills add https://github.com/Chang-Shih-Yung/nexus-finance --skill devex-review-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shipping developer-facing features that feel confusing or broken to new users. It catches onboarding friction, unclear docs, and CLI usability issues before they reach production by actually testing the developer journey end-to-end.

Core Features & Use Cases

  • Live DX Testing: Uses the browse tool to navigate docs, run the getting started flow, and time TTHW (time to hello world) in a real environment.
  • Evidence-Based Scorecard: Screenshots error messages, evaluates CLI help text, and produces a structured DX scorecard with concrete evidence rather than opinions.
  • Boomerang Comparison: Compares actual developer experience against planned estimates (e.g., plan said 3 minutes, reality says 8) to surface estimation gaps.
  • Use Case: After shipping a new API or CLI tool, run this Skill to verify that a stranger can successfully complete onboarding in under 5 minutes without reading the README twice.

Quick Start

Use the devex-review skill to audit the developer onboarding flow for the current project and produce a DX scorecard with evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema
What is a developer experience audit and how does it work?

A developer experience audit tests onboarding flows, documentation, and CLI usability in live environments to capture friction. It navigates real setup paths, executes commands, and times TTHW to produce evidence-based scorecards.

How do I measure time-to-hello-world for my API onboarding flow?

Measure time-to-hello-world by running the getting started flow in a live environment and timing the duration from initial setup to first successful execution. The audit captures this duration and compares it against planned estimates.

Can I test CLI usability and documentation clarity before a pre-release launch?

Yes, pre-release validation of CLI tools and API onboarding is supported. The audit executes setup commands, evaluates CLI help text, and screenshots error messages to verify a stranger can complete onboarding without reading the README twice.

What is the best way to identify onboarding friction in developer-facing features?

The best way to find onboarding friction is testing the developer journey end-to-end in a real environment. This approach navigates live documentation, captures screenshots of failures, and generates a structured DX scorecard with concrete evidence.

How do I compare actual developer experience against planned onboarding estimates?

Compare actual developer experience against planned estimates using a boomerang comparison. It measures the real time-to-hello-world against planned durations, such as a 3-minute estimate versus an 8-minute reality, to surface estimation gaps.

Does the DX audit require a live environment to test documentation?

Yes, the DX audit requires a live environment because it uses the browse tool to navigate live documentation, execute setup commands, and capture screenshots of failures to generate an evidence-based scorecard rather than relying on opinions.