dx-scan

Purpose

Scan the actual codebase to discover conventions, then interactively customize .claude/rules/ with real values and generate .ai/project/ seed data files. This is the "teach the AI about YOUR project" step.

Before this skill: /dx-init scaffolds config, /dx-adapt detects type/toolchain, /aem-init sets up AEM. After those, rules still have generic placeholders and seed data is empty.

After this skill: Rules contain real CSS variables, actual component patterns, discovered naming conventions. Seed data describes the architecture, features, and file patterns. Every AI skill benefits from this context.

Prerequisites

1. .ai/config.yaml must exist (run /dx-init first)
2. project.type must be set (run /dx-adapt first)
3. For AEM projects: aem: section must exist (run /aem-init first)

If any prerequisite is missing, print which skill to run and STOP.

Argument

Optional phase selector:

• phase1 — frontend conventions only
• phase2 — backend conventions only
• phase3 — seed data only
• all or no argument — run all phases

Flow

digraph dx_scan {
    "Check prerequisites" [shape=box];
    "Prerequisites OK?" [shape=diamond];
    "Read config + detect scope" [shape=box];
    "Phase 1: Frontend conventions" [shape=box];
    "Phase 2: Backend conventions" [shape=box];
    "Phase 3: Seed data" [shape=box];
    "Summary" [shape=doublecircle];
    "STOP — missing prereqs" [shape=doublecircle];

    "Check prerequisites" -> "Prerequisites OK?";
    "Prerequisites OK?" -> "STOP — missing prereqs" [label="no"];
    "Prerequisites OK?" -> "Read config + detect scope" [label="yes"];
    "Read config + detect scope" -> "Phase 1: Frontend conventions";
    "Phase 1: Frontend conventions" -> "Phase 2: Backend conventions";
    "Phase 2: Backend conventions" -> "Phase 3: Seed data";
    "Phase 3: Seed data" -> "Summary";
}

Node Details

Check prerequisites

Read .ai/config.yaml. Verify:

• File exists
• project.type is set
• If type starts with aem-: verify aem: section exists