developer-experience plugins

by tonone-ai

Developer Experience Team — 10 agents: Guide, Sample, Mock, Schema, Port, Change, Onboard, Bench, Compat, Gate

by Alister Lewis-Bowen

Expert UX evaluator for command-line interfaces, CLIs, terminal tools, shell scripts, and developer APIs

by tonone-ai

Developer Experience Team — 10 agents: Guide, Sample, Mock, Schema, Port, Change, Onboard, Bench, Compat, Gate

by Alberto Leal

Build and refactor CLIs for AI agent compatibility. Use when making CLI tools machine-readable with structured JSON output, input hardening, schema introspection, dry-run safety, and MCP surfaces.

by Matt Corbett

Developer-relations / DevRel team — agents (developer-advocate, devrel-content-engineer, developer-community-manager) for the developer experience of a product with an API/SDK: time-to-first-success (getting-started) audits, sample-app and SDK-quickstart design, a DX content strategy, conference talks + CFP abstracts, community health, DX metrics (activation funnel), and the product-feedback loop that fixes the product instead of writing around it. skills, a knowledge bank with Mermaid decision trees (advocate-vs-docs-vs-community, fix-the-product-or-document-it, content-format choice), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from technical-writing-docs (reference docs), marketing-operations (demand gen), and product-management (what to build). Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Platform Engineering (IDP) specialist team — agents (platform-eng-lead, golden-path-architect, developer-experience-analyst, platform-reliability-specialist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A platform-engineering team for a platform lead or eng director accountable for developer productivity and adoption — it treats the platform as a product with developers as customers, paves golden paths over mandates, measures DevEx with DORA and lead time, and runs the platform on SLOs and an error budget. Inherits ravenclaude-core protocols.

by Emanuele Minotto

Use whenever the user asks about QA, testing strategy, CI/CD health, team processes, developer experience, code review practices, test coverage, flaky tests, monitoring, or any audit of an engineering team's quality practices.

by rvfvazquez

Structured specs, architecture documentation, and pragmatic engineering patterns for developer experience.

by Paulo Soares

Configure and manage Claude Code status line — installs a rich, configurable bash status bar (single-jq-pass, dynamic colors, formatted tokens, truncated paths) showing model, git branch, context usage, rate limits, and token counts.

by Wagner Ignacio Pinto Junior

Build and evaluate command-line tools for AI agent consumption: machine-readable output, semantic exit codes, hardened input, and a 0-21 agent-friendliness rubric

by jessebldr

Make Claude Code easier to understand without making it less capable. Ships the Clear Partner output style — answer-first, plain English, concise by default, deep when asked — plus two read-only diagnostic skills, clear-doctor and clear-audit.

by jessebldr

A calm, adaptive status bar for Claude Code: model, effort, project and git branch on the left; context, 5-hour and weekly usage on the right. One row when the terminal is wide enough, two when it is not. Drawn only from the data Claude Code already provides plus one cached git status — no network, no credentials, no transcript parsing. Optional companion to clear-claude.

by Wagner Ignacio Pinto Junior

Design and evaluate command-line tools for human users: naming and grammar, interactive prompts, colour and progress output, error messages, and a 0-21 usability rubric