Manage Architecture

Enforce import and packaging rules to prevent circular dependencies.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Row0902/agents --skill manage-architecture-row0902
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Manage Architecture
Source: https://github.com/Row0902/agents/tree/main/.agent/skills/manage_architecture
Command: npx skills add https://github.com/Row0902/agents --skill manage-architecture-row0902

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces robust architecture and import strategies to prevent circular imports, promote modular design, and eliminate "Import Hell" in large codebases.

Core Features & Use Cases

  • Absolute vs Relative imports guidance: Cross-package references use ABSOLUTE imports, while intra-package siblings use RELATIVE imports to keep boundaries clean.
  • Public API pattern: Export key components in package init.py to avoid importing deep modules directly.
  • Structural Integrity & Packaging: Encourage grouping by domain, enforce module size considerations, and prevent God files by distributing logic across sub-packages.
  • Review Protocol & Troubleshooting: Provide a standard checklist before changes and guidance for common import issues.
  • Use Case: A large monorepo with multiple packages maintaining clean import graphs and easy evolvability.

Quick Start

Enforce architecture standards across your codebase by applying absolute imports for cross-package references, using relative imports for siblings, and exporting essential symbols in init.py to avoid deep imports.

Frequently Asked Questions about Manage Architecture

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

FAQPage Schema
How do I prevent circular imports in a large Python monorepo?

Prevent circular imports by enforcing clean architecture standards that apply absolute imports for cross-package references and relative imports for siblings. This maintains clear module boundaries and eliminates Import Hell in large codebases.

What is the best way to manage cross-package imports and public API exposure?

Manage cross-package imports by using absolute references across packages and exporting key components in package __init__.py files. This public API pattern prevents direct deep module imports and keeps dependency graphs clean.

How do I enforce modular code structure and avoid God files in my project?

Enforce modular code by applying structural integrity checks that group modules by domain, monitor module size, and distribute logic across sub-packages. This prevents God files and promotes evolvability across the project.

Does this approach work for large monorepos with multiple packages?

Yes, this architecture enforcement is designed for large monorepos with multiple packages. It applies structural checks, review protocols, and packaging guardrails to maintain clean import graphs and easy evolvability across complex codebases.

When should I use relative imports instead of absolute imports?

Use relative imports for intra-package sibling references to keep boundaries clean, while using absolute imports for cross-package dependencies. This distinction is central to maintaining a healthy modular architecture.