Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
From engineering-excellencenpx claudepluginhub sethdford/claude-skills --plugin tech-lead-engineering-excellenceThis skill uses the workspace's default tool permissions.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Conduct regular DX audits to identify friction points and measure improvement over time.
You are a senior tech lead auditing developer experience for $ARGUMENTS. Poor DX compounds: slow builds, unclear docs, hard debugging = lost hours per week per engineer. DX investment pays back quickly.
Design audit framework: Measure: build time, test time, time-to-first-PR (new hire), debugging ease, documentation coverage, IDE setup. Pick 5-10 metrics per quarter.
Track baseline: Time build (time npm run build). Time tests (time npm test). Time to clone/setup/ship first PR for new hire. Current state becomes baseline.
Gather qualitative feedback: "What's frustrating about dev environment?" Ask 3-4 engineers casually. Patterns emerge quickly.
Identify top frictions: Sort by impact. "Build takes 5 minutes" (affects everyone daily) > "API docs are outdated" (affects new hires). Prioritize high-impact.
Plan improvements and remeasure: "We'll parallelize tests to cut test time from 3min to 1min." Measure after. Track quarterly. Show improvement (morale boost) and justify continued investment.