dx-review

Analyze LibPDF's public API and TypeScript typings to produce a structured DX report.

1.8k|62|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/LibPDF-js/core --skill dx-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-review
Source: https://github.com/LibPDF-js/core/tree/main/.opencode/skills/dx-review
Command: npx skills add https://github.com/LibPDF-js/core --skill dx-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DX review helps ensure LibPDF's developer experience is intuitive, consistent, and productive by identifying friction points in the public API, type definitions, and documentation.

Core Features & Use Cases

  • DX discovery: evaluate discoverability, naming, and surface area to ensure developers can find and use features quickly.
  • Consistency & Ergonomics: assess naming conventions, parameter requirements, defaults, and return types for predictability.
  • Documentation Quality: audit in-code docs, examples, and error messages to improve guidance and reduce learning time.
  • DX Reporting: produce structured recommendations and actionable fixes that can be tracked in issues.

Quick Start

Ask the DX Review to assess LibPDF's main public API and propose concrete ergonomic improvements to the TypeScript typings and error messages to improve developer satisfaction.

Frequently Asked Questions about dx-review

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

FAQPage Schema
How do I review API ergonomics for a TypeScript library?

API ergonomics review analyzes the public API surface, TypeScript typings, and error handling to identify friction points. It evaluates discoverability, naming conventions, and parameter requirements to ensure developers can use features quickly and predictably.

What is developer experience analysis for software engineering?

Developer experience analysis assesses API discoverability, consistency, and documentation quality to reduce learning time. It audits in-code docs, examples, and error messages to improve guidance and ensure an intuitive, productive development workflow.

How do I audit TypeScript typings and error messages for developer friction?

Auditing TypeScript typings and error messages involves assessing naming conventions, parameter requirements, defaults, and return types for predictability. It identifies confusing type definitions and poor error guidance to propose concrete ergonomic improvements.

Can I generate a structured report for API design improvements?

Yes, a DX review produces a structured report detailing identified issues, their impact, and actionable recommendations. It outputs concrete fixes for API surface, typings, and documentation that can be tracked directly in issues.

Does developer experience review work for existing public API surfaces?

Yes, developer experience review evaluates existing public API surfaces to assess discoverability, naming, and surface area. It ensures developers can find and use features quickly by identifying friction points in current type definitions and documentation.

What are common limitations of a DX review for documentation quality?

A DX review focuses on the main public API surface, TypeScript typings, and error handling. It audits in-code docs and examples but may not cover internal architecture or private APIs, limiting its scope to public-facing developer ergonomics.