domain-dag

Validate domain ownership and acyclic dependency graphs in modular codebases.

4|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/atmo-network/deos --skill domain-dag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-dag
Source: https://github.com/atmo-network/deos/tree/main/.agents/skills/domain-dag
Command: npx skills add https://github.com/atmo-network/deos --skill domain-dag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers maintain a well-structured and readable codebase by ensuring the code follows a directed acyclic graph (DAG) architecture, reducing complexity and improving maintainability.

Core Features & Use Cases

  • Validate Domain DAG Architecture: Checks for domain ownership, acyclic local dependency graphs, and other architectural principles.
  • Audit and Refactor: Use the Skill to audit existing codebases or refactor code to improve architecture.
  • Use Case: For a large codebase with multiple modules and dependencies, use this Skill to identify and resolve architectural issues like shared buckets and cyclic dependencies.

Quick Start

Validate the architecture of your codebase using the domain-dag skill by running 'validate-domain-dag.sh' in the project root directory.

Frequently Asked Questions about domain-dag

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

FAQPage Schema
How do I validate a directed acyclic graph architecture in my codebase?

To validate a directed acyclic graph architecture, run the validate-domain-dag.sh script in your project root. This checks domain ownership, acyclic local dependency graphs, and interface surface pressure to ensure modular codebase maintainability.

What is a domain DAG and when do I need it for modular codebases?

A domain DAG is a directed acyclic graph architecture enforcing domain ownership and acyclic local dependencies. You need it for modular codebases to reduce complexity, resolve shared buckets, and improve maintainability and scalability.

How do I fix cyclic dependencies and shared buckets in a large codebase?

Fix cyclic dependencies and shared buckets by auditing your codebase with a dependency graph validator. It identifies architectural issues like local cycles, guiding refactoring efforts to restore proper domain ownership and acyclic structure.

Can I use this dependency graph validator to audit existing module designs?

Yes, you can use this dependency graph validator to audit existing module designs. It assesses composition roots, domain ownership, and interface surface pressure to identify architectural violations in current codebases.

What are the limitations of enforcing a directed acyclic graph architecture?

A limitation of enforcing a directed acyclic graph architecture is the strict requirement for acyclic local dependency graphs and clear domain ownership, which may demand significant refactoring for codebases with deeply entrenched shared buckets.