devarispbrown
- 43 skills
- 0 followers
- 1 day ago last updated
- ▌
- ▌
- ▌ Developer Docs · devarispbrown bundleDesign, write, restructure, and update world-class documentation for developer-facing and open-source products. Use for READMEs, 15-minute quickstarts, Diátaxis tutorials/how-tos/reference/explanation, API/SDK/CLI/config docs, code comments, examples, integration guides, stakeholder docs, migration docs, and documentation architecture. Establish implementation truth first and flag product/DX design problems instead of documenting around them. For adversarial documentation audits use developer-docs-auditor; for whole-product developer-experience audits use developer-experience-auditor.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Error Experience · devarispbrown bundleDesign and audit the error experience across APIs, CLIs, SDKs, diagnostics, logs, and traces so every expected error answers what happened, why, where, how to fix it, whether retry is safe, and how to correlate with support. Use to build error taxonomies, per-surface contracts, error playbooks, and Time to Recovery measurements. For API error-model design use api-design-reviewer; for release gate enforcement use release-guardian.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Agent Integration Dx · devarispbrown bundleDesign and audit tool definitions and MCP servers as shipped product artifacts. Covers tool naming, description-as-prompt authoring, argument schema design, response shaping against a context budget, pagination and truncation, and error surfaces an agent can act on. Use when building an MCP server, exposing tools to an agent framework, or reviewing a tool surface for wrong-tool selection. For auditing a whole repository's agent readiness use agent-native-dx; for the underlying HTTP API design use api-design-reviewer.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Developer Docs Auditor · devarispbrown bundleAdversarially audit and release-gate developer documentation for correctness, drift, executable examples, API/SDK/CLI/config parity, onboarding friction, terminology, lifecycle coverage, and developer experience. Use for repo/PR/release docs audits, documentation CI, stale-doc detection, 15-minute quickstart validation, SDK parity reviews, and world-class documentation scoring. Prefer observed evidence and fail gates rather than smoothing over product defects. For whole-product developer-experience audits use developer-experience-auditor.
- ▌
- ▌
- ▌ Test Data And Fixtures · devarispbrown bundleAuthor fixtures, seed data, factories, fake services, mock servers, record-replay cassettes, golden files, synthetic datasets, and sanitization, with a project test-data create pattern. For sandbox route design use sandbox-experience; for per-system-type test strategy use quality-engineer.
- ▌
- ▌
- ▌ Experimentation Engineer · devarispbrown bundleRun DX experiments on quickstarts, CLI output variants, error formatting, and onboarding flows, measuring task completion, time, error rate, drop-off, support load, and retention, with OpenFeature-style flagging as the reference. For analyzing passive feedback signals use developer-feedback-analyst.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌