Developer Experience Review
By Logan · Published · Updated
Audits how quickly a new developer gets from the README to a first working call, and ranks the fixes that would shorten that path.
Prompt template
## Developer Experience Review Audit the developer experience of my product from first contact to first success. - Product and audience: [textarea: What developers use it for and their skill level] - Entry points: [textarea: README or docs site or quickstart links] - Setup steps today: [textarea: Install and configure and run steps as a new user does them] - Time to first success: [text: Minutes you or a tester needed] - Where people get stuck: [textarea: Support questions or issues] - Package type: [dropdown: SDK, REST API, CLI, Framework, Template] Act as a new developer and follow the documented path exactly as written, timing each stage: find the docs, install, authenticate, make the first call, see a result. Record every point of friction: missing prerequisite, stale command, unexplained error, jump to a different page. Rate the docs on a quickstart that works verbatim, copyable examples, error message quality, and reference completeness. Rank the fixes by minutes saved per developer, with the effort for each. Rewrite the first screen of the quickstart so it reaches a working result in the fewest steps. Close with a target time to first success.