debugging-toolkit-dx-optimizer — Claude Code subagent
A subagent that streamlines onboarding to under 5 minutes and removes workflow bottlenecks. It configures tools and automates repetitive developer routines.
/plugin marketplace add wshobson/agents
/plugin install debugging-toolkit@claude-code-workflowsWhat debugging-toolkit-dx-optimizer does
This subagent focuses on developer experience. It inspects local development habits, speeds up build and test loops, and automates dependency setup so team onboarding takes less than five minutes.
Its tangible outputs include scripts in package.json, Git hooks for pre-commit checks, IDE configuration files, and a Makefile. It also drafts custom project commands inside .claude/commands/ alongside clear troubleshooting steps in README.md.
Execution relies on the sonnet model. Calling this subagent makes the most sense right after cloning a repository or whenever manual terminal friction slows down daily tasks.
What it helps with
- cut fresh project setup time to under five minutes
- automate repetitive CLI steps with custom commands
- configure Git hooks for common code checks
- improve build scripts and hot reload feedback loops
Example prompts for the agent
- Audit our
package.jsonscripts and speed up local test runs - Set up Git hooks to prevent committing unformatted files
- Write a reliable setup guide for onboarding in
README.md
How to install debugging-toolkit-dx-optimizer
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install debugging-toolkit@claude-code-workflows2Manually: put the files in place
.claude/agents/dx-optimizer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/dx-optimizer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/dx-optimizer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about debugging-toolkit-dx-optimizer
How to install debugging-toolkit-dx-optimizer in Claude Code?
First register the marketplace by running /plugin marketplace add wshobson/agents. Then complete the setup with /plugin install debugging-toolkit@claude-code-workflows.
What does debugging-toolkit-dx-optimizer do?
It identifies friction points in development workflows, automates common terminal tasks, configures IDE settings, and updates project documentation.
What files does this subagent generate?
It delivers scripts in package.json, Git hook configs, Makefile targets, files in .claude/commands/, and documentation guides.
Source text
dx-optimizer.md · MIT
--- name: debugging-toolkit-dx-optimizer description: Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed. model: sonnet --- 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 - Simplify onboarding to < 5 minutes - Create intelligent defaults - Automate dependency installation - 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 ## Deliverables - `.claude/commands/` additions for common tasks - Improved `package.json` scripts - 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.
© Seth Hobson · MIT · wshobson/agents
