mcpField
D
developer-tool-product-design

developer-tool-product-design

github.com/sylphxaiDesign & UI151 installsUpdated today
Repository

About developer-tool-product-design

A skill for evaluating developer products from discovery through production adoption. It turns audits of the developer experience into an activation plan covering product, documentation, instrumentation, and support.

Key features

  1. 01Maps developer persona and adoption path
  2. 02Audits docs, SDKs, APIs, and errors
  3. 03Reviews limits, telemetry, and trust signals
  4. 04Produces an activation plan

Use cases

  1. 01Assessing a developer product’s first-run experience
  2. 02Preparing a product for production adoption

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill developer-tool-product-design

After installing, type/developer-tool-product-designin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/developer-tool-product-systems.md

Details

From the project README

Developer Tool Product Design

Use this skill to make developer products easy to understand, fast to try, safe to adopt, and credible in production.

Workflow

  1. Identify developer persona, job-to-be-done, integration surface, adoption path, and production risk.
  2. Read references/developer-tool-product-systems.md.
  3. Map the path from discovery to first successful call/run, production integration, debugging, billing, and support.
  4. Audit docs, examples, SDK/API shape, error messages, limits, telemetry, changelog, and trust signals.
  5. Produce an activation plan with product changes, docs changes, instrumentation, and support readiness.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not optimize only for signups; optimize for first success and safe production adoption.
  • Do not hide limits, pricing, auth requirements, data handling, or breaking-change policy.
  • Treat error messages, logs, examples, and support traces as product UX.

Output format

Developer persona/job:
Integration surface:

Activation path:
- <step> -> success evidence, failure mode, fix

DX findings:
- P0 <issue> -> product/docs/API change

Operational trust:
- limits, pricing, changelog, status, support, migration policy

Metrics:
- discovery, first success, production adoption, retention, support load

Comments

Markdown supported