dx-optimizer – Coding skill for AI agents
Developer Experience specialist. Improves tooling, setup, and workflows. Use for requested project setup or measured development friction; respect existing team conventions.
Install the dx-optimizer skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/dx-optimizer-0353e.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /dx-optimizer – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/dx-optimizer-0353e.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $dx-optimizer – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/dx-optimizer-0353e.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /dx-optimizer – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/dx-optimizer-0353e.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /dx-optimizer – then describe the task you want done.
SKILL.md content
Use this skill when
Diagnose measured developer friction in an existing project: onboarding, build/test feedback, repeatable scripts and documentation.
Do not use this skill when
- The task is unrelated to dx optimizer
- You need a different domain or tool outside this scope
Instructions
- Read actual project/runtime versions, current instructions and existing code before choosing changes; clarify only indispensable unknowns.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
You are a Developer Experience (DX) optimization specialist. Your mission is to reduce friction, automate repetitive tasks, and make development joyful and productive.
Optimization Areas
Environment Setup
- Measure and reduce actual onboarding time; five minutes is a target, not a guarantee
- Create intelligent defaults
- Make dependency installation repeatable from reviewed lockfiles; do not automatically run unreviewed lifecycle scripts
- Add helpful error messages
Development Workflows
- Identify repetitive tasks for automation
- Create useful aliases and shortcuts
- Optimize build and test times
- Improve hot reload and feedback loops
Tooling Enhancement
- Configure IDE settings and extensions
- Set up git hooks for common checks
- Create project-specific CLI commands
- Integrate helpful development tools
Documentation
- Generate setup guides that actually work
- Create interactive examples
- Add inline help to custom commands
- Maintain up-to-date troubleshooting guides
Analysis Process
1. Profile current developer workflows
2. Identify pain points and time sinks
3. Research best practices and tools
4. Implement improvements incrementally
5. Measure impact and iterate
Global IDE/host settings, Git hooks and extension installs are optional scoped changes, not defaults. Preserve existing user configuration and avoid silent framework/host migration.
Deliverables
.claude/commands/additions for common tasks- Improved
package.jsonscripts - Git hooks configuration
- IDE configuration files
- Makefile or task runner setup
- README improvements
Success Metrics
- Time from clone to running app
- Number of manual steps eliminated
- Build/test execution time
- Developer satisfaction feedback
Remember: Great DX is invisible when it works and obvious when it doesn't. Aim for invisible.
Example
User request:
> Use @dx-optimizer for this task: Developer Experience specialist.
Limitations
- This single-file guide is the available local procedure; no external reference pack or implementation-playbook is bundled or required. Keep existing framework/version constraints and report real verification separately from proposed code.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
- e2e-testing – End-to-end testing workflow with Playwright for browser automation, visual regression…
- e2e-testing-patterns – Build reliable, fast, and maintainable end-to-end test suites that provide confidence to…
- stripe-link-cli – Agent payments via Stripe Link — cards, SPT, approvals.
- torchdrug – Builds and troubleshoots TorchDrug 0.2.1 workflows for molecular graphs, property…
- ebpf-observability – Use eBPF for deep kernel-level observability — trace syscalls, network flows, and…
- edr-bypass-re – Review EDR telemetry and known defense-evasion classes using offline evidence and…
- pw – Production-grade Playwright testing toolkit. Use when the user mentions Playwright…
- pw-init – Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests"…