MA

Visualizes domain/layer architecture and detects drift between your config and filesystem.

Install

mkdir -p .claude/skills/map-domain && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12288" && unzip -o skill.zip -d .claude/skills/map-domain && rm skill.zip

Installs to .claude/skills/map-domain

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use this skill to render the harness's domain/layer config as a mermaid diagram + check for drift between .harness/config.json#domains and the actual filesystem. Surfaces "the config says layers A→B→C but the repo has folders A, B, X" — drift that silently invalidates the structural-test contract.
298 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Render a Mermaid diagram of the harness's domain/layer configuration
  • Check for drift between `config.json#domains` and the filesystem
  • Identify missing directories for configured layers
  • Generate a report with domain, layer, and drift counts
  • Update a README with the generated markdown diagram

How it works

The skill runs a side-car script to parse the `.harness/config.json` file and compare its domain/layer definitions against the actual filesystem. It then generates a Mermaid diagram and a drift report.

Inputs & outputs

You give it
`.harness/config.json` and the project's filesystem structure
You get back
Mermaid diagram of domain layers, drift report, and an updated markdown file

When to use map-domain

  • Visualizing project domain layers
  • Identifying architecture drift after moving files
  • Onboarding new developers to project structure
  • Validating structural test contracts

About map-domain

Parses harness domain configurations to render a mermaid diagram of your architecture. It cross-references the config against the actual file structure to surface discrepancies or 'drift' in layer organization.

Use this skill to render the harness's domain/layer config as a mermaid diagram + check for drift between .harness/config.json#domains and the actual filesystem. Surfaces "the config says layers A→B→C but the repo has folders A, B, X" — drift that silently invalidates the structural-test contract.

When not to use it

  • When the project does not use `.harness/config.json` for domain/layer configuration
  • When the user does not need to visualize architectural layers
  • When the user does not need to check for filesystem discrepancies

Limitations

  • Requires `.harness/config.json` for configuration
  • Drift detection is based on directory existence, not content
  • The skill only generates Mermaid diagrams

How it compares

This skill automates the visualization of architectural layers and detects structural drift by comparing configuration with the filesystem, which is more efficient than manual inspection.

Compared to similar skills

map-domain side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
map-domain (this skill)02moReviewIntermediate
project-overview152moNo flagsBeginner
mcaf-architecture-overview06moNo flagsIntermediate
understand-codebase-architecture01moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

project-overview

lobehub

Complete project architecture and structure guide. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, or project overview needs.

1548

mcaf-architecture-overview

Zendevve

Create or update `docs/Architecture/Overview.md` (architecture diagrams): maintain Mermaid diagrams for system/modules, interfaces/contracts, and key classes/types; document dependency rules; link to ADRs/features. Use when onboarding, refactoring, or adding modules/boundaries.

00

understand-codebase-architecture

isaac-scarrott

Build an interactive onboarding map of a codebase's architecture as a self-contained HTML report — click a box to drill into a subsystem, breadcrumbs to climb back, detail behind clicks so nothing overloads. Use when the user wants the generated visual artifact: a "map", "diagram", "visualise the ar

00

mermaid-diagram-specialist

davila7

Mermaid diagram specialist for creating flowcharts, sequence diagrams, ERDs, and architecture visualizations

1277

wiki-architect

microsoft

Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.

1144

specification-writing

EpicenterHQ

Write technical specifications that give agents enough context to implement features while leaving room for autonomous research and decision-making. Use when planning features, documenting architecture decisions, or creating implementation guides.

25

Search skills

Search the agent skills registry