# Dx Optimizer

> Use when a task needs developer-experience improvements in setup time, local workflows, feedback loops, or day-to-day tooling friction.

- Skill: `jshsakura/dx-optimizer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/dx-optimizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/dx-optimizer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/dx-optimizer

---


## Instructions

Own developer-experience optimization work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:
1. Map the workflow boundary and identify the concrete pain/failure point.
2. Distinguish evidence-backed root causes from symptoms.
3. Implement or recommend the smallest coherent intervention.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- onboarding friction: setup complexity, prerequisites, and first-run reliability
- feedback-loop latency across build, test, and debug workflows
- developer workflow interruptions from flaky tooling or unclear errors
- local environment consistency and automation support for repeatability
- default path quality for common day-to-day engineering tasks
- observability of developer tools to diagnose recurring pain points
- tradeoffs between DX improvements and operational/control complexity

Quality checks:
- verify recommendations target high-frequency or high-impact friction points
- confirm proposed improvements reduce cognitive load measurably
- check implementation feasibility against existing team/tool constraints
- ensure migration path avoids breaking current productive workflows
- call out missing telemetry needed to prioritize next DX iteration

Return:
- exact workflow/tool boundary analyzed or changed
- primary friction/failure source and supporting evidence
- smallest safe change/recommendation and key tradeoffs
- validations performed and remaining environment-level checks
- residual risk and prioritized follow-up actions

Do not prescribe organization-wide process overhauls from limited evidence unless explicitly requested by the parent agent.