Optimize Developer Experience and Workflows

DX Optimizer is a skill that turns the agent into a Developer Experience specialist. Its stated mission is to reduce friction, automate repetitive tasks and make development joyful and productive. It improves tooling, setup and workflows, and its description says to use it proactively when setting up new projects, after team feedback, or when development friction is noticed.

The skill organizes its work into four optimization areas.

Environment setup: simplify onboarding to under five minutes, create intelligent defaults, automate dependency installation and add helpful error messages.

Development workflows: identify repetitive tasks for automation, create useful aliases and shortcuts, optimize build and test times, and 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 and integrate helpful development tools.

Documentation: generate setup guides that actually work, create interactive examples, add inline help to custom commands and maintain up-to-date troubleshooting guides.

Work follows a five-step analysis process. First profile the current developer workflows, then identify pain points and time sinks, then research best practices and tools, then implement improvements incrementally, and finally measure the impact and iterate. The skill closes with a guiding principle: great DX is invisible when it works and obvious when it doesn't, so aim for invisible.

Use it when a project is being set up, when a team has given feedback about friction, or when you notice slow builds, painful onboarding, repeated manual steps or setup instructions that do not work. It also applies whenever you want guidance, best practices or checklists specifically about developer experience optimization.

Do not use it when the task is unrelated to DX optimization or needs a different domain or tool outside this scope. The skill's Limitations section adds that it should only be used when the task clearly matches its scope, that its output is not a substitute for environment-specific validation, testing or expert review, and that the agent should stop and ask for clarification if required inputs, permissions, safety boundaries or success criteria are missing.

The general instructions ask the agent to clarify goals, constraints and required inputs, apply relevant best practices and validate outcomes, and provide actionable steps with verification. For detailed examples, the skill points to a resources/implementation-playbook.md file. You invoke the skill by name in a request, such as asking to use dx-optimizer for a task.

The listed deliverables are:

• additions to the agent's local skill directory for common tasks
• improved package.json scripts
• a git hooks configuration
• IDE configuration files
• a Makefile or task runner setup
• README improvements

Progress is judged with four success metrics: time from clone to running app, number of manual steps eliminated, build and test execution time, and developer satisfaction feedback.

Engineering leads, platform and tooling teams, and individual developers who want their repositories to be quick to start, pleasant to work in and well documented. The skill is community-sourced, so review any changes it proposes to scripts, hooks or configuration before applying them.