32 skills · sorted by relevance
Audit a developer product by trying its documentation and setup flow, measuring onboarding time, capturing errors, and reviewing command-line help. Produce an evidence-backed scorecard and compare results with earlier planning scores when available.
Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".
The English summary is being prepared. Showing the original description.
Review plans for APIs and developer tools through the eyes of their users. Explore developer needs, compare competitors, and identify onboarding friction, with modes for competitive differentiation, detailed refinement, or critical gaps.
Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".
The English summary is being prepared. Showing the original description.
Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
The English summary is being prepared. Showing the original description.
Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infrastructure orchestration (Crossplane), GitOps (Argo CD), and adoption patterns. Use when building developer platforms, improving DevEx, or establishing platform teams.
The English summary is being prepared. Showing the original description.
Live developer experience audit. (gstack)
The English summary is being prepared. Showing the original description.
Audit existing mocks and test doubles — find contract drift, missing error cases, and stale fixtures. Use when asked to "audit our mocks", "find stale test fixtures", or "check for contract drift".
The English summary is being prepared. Showing the original description.
Design a consumer-driven contract testing setup — Pact configuration and CI integration. Use when asked to "set up contract testing", "configure Pact", or "add consumer-driven contracts".
The English summary is being prepared. Showing the original description.
Audit the developer onboarding experience — measure TTFC and find friction points. Use when asked "why do developers drop off", "audit our onboarding", or "measure time to first call".
The English summary is being prepared. Showing the original description.
Design a mock server for an API — tooling selection, response fixtures, and error scenarios. Use when asked to "build a mock server", "mock this API for development", or "create response fixtures".
The English summary is being prepared. Showing the original description.
Write a developer quickstart — minimal steps from zero to first successful API call. Use when asked to "write a quickstart", "get users from zero to first API call", or "write a getting started guide".
The English summary is being prepared. Showing the original description.
Survey existing onboarding docs and developer portal — find gaps and structural issues. Use when asked to "survey our onboarding docs", "find developer portal gaps", or "review our onboarding structure".
The English summary is being prepared. Showing the original description.
Audit existing API documentation for completeness, accuracy, and developer experience. Use when asked to "audit our API docs", "are our docs accurate", or "review documentation quality".
The English summary is being prepared. Showing the original description.
Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt. Use when asked to "audit our API quality controls", "find missing lint rules", or "assess our API governance".
The English summary is being prepared. Showing the original description.
Write API reference documentation for an endpoint or SDK method. Use when asked to "document this endpoint", "write API reference docs", or "document this SDK method".
The English summary is being prepared. Showing the original description.
Survey documentation coverage across an API or SDK — find undocumented endpoints and gaps. Use when asked "what is undocumented", "find docs coverage gaps", or "survey our API documentation".
The English summary is being prepared. Showing the original description.
Design an API linting ruleset — style rules, severity levels, and custom organization conventions. Use when asked to "design an API lint ruleset", "enforce API style", or "write Spectral rules".
The English summary is being prepared. Showing the original description.
Integrate API quality gates into CI — linting, breaking change detection, and coverage checks. Use when asked to "add API checks to CI", "detect breaking changes in CI", or "set up an API quality gate".
The English summary is being prepared. Showing the original description.
Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".
The English summary is being prepared. Showing the original description.
Audit a proposed API change for breaking changes — classification and impact assessment. Use when asked "is this a breaking change", "will this break clients", or "assess the impact of this API change".
The English summary is being prepared. Showing the original description.
Audit existing API for breaking change risks and missing compatibility controls. Use when asked to "find breaking change risks in our API", "audit our compatibility controls", or "what could break clients".
The English summary is being prepared. Showing the original description.
Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".
The English summary is being prepared. Showing the original description.
Audit existing changelog and deprecation practices — find missing entries, undocumented breaks, and stale deprecations. Use when asked to "audit our changelog", "find undocumented breaking changes", or "check for stale deprecations".
The English summary is being prepared. Showing the original description.