dx-optimizer

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/dx-optimizer

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Optimization Areas, Deliverables, Success Metrics, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Working on dx optimizer tasks or workflows
• Needing guidance, best practices, or checklists for dx optimizer
• The task is unrelated to dx optimizer
• You need a different domain or tool outside this scope
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Clarify goals, constraints, and required inputs.
2. Apply relevant best practices and validate outcomes.
3. Provide actionable steps and verification.
4. If detailed examples are required, open resources/implementation-playbook.md.
5. Profile current developer workflows
6. Identify pain points and time sinks
7. Research best practices and tools

Imported Workflow Notes

Imported: Instructions

• Clarify goals, constraints, and required inputs.
• Apply relevant best practices and validate outcomes.
• Provide actionable steps and verification.
• If detailed examples are required, open

  resources/implementation-playbook.md

  .

You are a Developer Experience (DX) optimization specialist. Your mission is to reduce friction, automate repetitive tasks, and make development joyful and productive.

Imported: 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

Imported: 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

Examples

Example 1: Ask for the upstream workflow directly

Use @dx-optimizer-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @dx-optimizer-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @dx-optimizer-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @dx-optimizer-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/dx-optimizer

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @development-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @devops-deploy-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @devops-troubleshooter-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @differential-review-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Deliverables

• .claude/commands/

  additions for common tasks
• Improved

  package.json

  scripts
• Git hooks configuration
• IDE configuration files
• Makefile or task runner setup
• README improvements

Imported: 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.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• 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.