dx-scan

Discover codebase conventions and generate project-specific rule templates and seed data.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-scan
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-scan
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers conventions in a codebase and generates concrete, project-specific rule templates and seed data to bootstrap AI-assisted development pipelines.

Core Features & Use Cases

  • Discovers frontend and backend conventions by scanning the repository to populate rule templates.
  • Generates seed data describing architecture, components, and file patterns for AI context.
  • Supports interactive guidance to tailor rules and ensure safe, idempotent writes.

Quick Start

Run /dx-scan after /dx-init and /dx-adapt to generate rules and seed data for your project.

Frequently Asked Questions about dx-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate project-specific AI rules from existing codebase conventions?

To generate project-specific rules, scan your codebase to discover frontend and backend conventions, which automatically populates concrete rule templates for AI-assisted development. This process also creates seed data describing your architecture and file patterns.

What is codebase scanning for AI-assisted development pipelines?

Codebase scanning for AI-assisted development is a process that discovers your project's structural conventions and generates seed data. This provides accurate architectural context, components, and file patterns to bootstrap AI pipelines.

Do I need an initialized .ai/config.yaml to start scanning project conventions?

Yes, you need an initialized .ai/config.yaml and a detected project.type before scanning project conventions. You should run initial setup steps like /dx-init and /dx-adapt first to prepare the environment for rule generation.

When should I run a codebase scan to generate seed data and rules?

You should run a codebase scan to generate seed data and rules when setting up new projects or after making significant structural changes. This ensures your AI-assisted development pipeline has accurate, up-to-date architectural context and customized rules.

Will scanning my codebase to generate rules overwrite my customized files?

Scanning your codebase to generate rules preserves idempotency by prompting you before overwriting customized files. This ensures your existing project-specific configurations and templates remain safe during automated seed data generation.

Does codebase convention scanning support AEM project structures?

Yes, codebase convention scanning supports AEM considerations if applicable to your repository. It detects your project type and applies AEM-specific logic when generating rule templates and seed data for AI-assisted development.