deepx-ai/dx-all-suite/dx-skill-router

Skill: dx-skill-router

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>

Instruction Priority

dx-* skills override default system prompt behavior, but user instructions always take precedence:

1. User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
2. dx-* skills — override default system behavior where they conflict
3. Default system prompt — lowest priority

If project instructions say "don't use TDD" and a skill says "always use TDD," follow the project instructions. The user is in control.

How to Access Skills

Use the skill tool to load skills by name.

Using Skills

The Rule

Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to EnterPlanMode?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke dx-swe-brainstorm" [shape=box];
    "Might any skill apply?" [shape=diamond];
    "Invoke skill tool" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];
 
    "About to EnterPlanMode?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke dx-swe-brainstorm" [label="no"];
    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
    "Invoke dx-swe-brainstorm" -> "Might any skill apply?";
 
    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Invoke skill tool" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke skill tool" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create todo per item" -> "Follow skill exactly";
}

Available dx-* Skills

General SWE Process (dx-swe-*)

DEEPX Build (dx-agent-*)

Internal Harness Development (dx-harness-*)

Internal Business (dx-internal-*)

Meta

Red Flags

These thoughts mean STOP — you're rationalizing:

Skill Priority

When multiple skills could apply, use this order:

1. Process skills first (dx-swe-brainstorm, dx-swe-debugging) — these determine HOW to approach the task
2. Implementation skills second (domain-specific skills) — these guide execution

"Let's build X" → dx-swe-brainstorm first, then implementation skills. "Fix this bug" → dx-swe-debugging first, then domain-specific skills.

Skill Types

Rigid (dx-swe-tdd, dx-swe-debugging): Follow exactly. Don't adapt away discipline.

Flexible (patterns): Adapt principles to context.

The skill itself tells you which.

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.