Atlas

Analyzes software architecture by mapping module dependencies and detecting structural risks.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill atlas-simota
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Atlas
Source: https://github.com/simota/agent-skills/tree/main/atlas
Command: npx skills add https://github.com/simota/agent-skills --skill atlas-simota

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses complex architectural challenges by analyzing system dependencies, identifying structural bottlenecks, and proposing concrete solutions like ADRs or RFCs to improve maintainability and scalability.

Core Features & Use Cases

  • Dependency Analysis: Visualizes module relationships, detects circular dependencies, and calculates coupling metrics.
  • Technical Debt Assessment: Identifies and quantifies architectural debt, prioritizing remediation efforts.
  • ADR/RFC Generation: Creates formal documentation for architectural decisions and proposed changes.
  • Use Case: When a system becomes hard to change, Atlas can map out the dependencies, pinpoint the most coupled modules, and generate an RFC to propose a refactoring strategy, complete with trade-offs and a migration plan.

Quick Start

Use the Atlas skill to analyze the dependencies of the 'api' module and suggest refactoring options.

Frequently Asked Questions about Atlas

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

FAQPage Schema
How do I detect circular dependencies and map module relationships in my codebase?

Module dependency analysis maps module relationships and detects circular references by calculating coupling metrics. This visualizes structural bottlenecks to pinpoint highly coupled components within your software architecture.

How do I assess technical debt and prioritize architectural refactoring efforts?

Technical debt assessment identifies and quantifies architectural debt to prioritize remediation efforts. It evaluates system dependencies to highlight structural bottlenecks hindering system maintainability and scalability.

What is the best way to generate Architecture Decision Records and RFCs for module restructuring?

Generating Architecture Decision Records and Requests for Comments formalizes architectural decisions and proposed changes. This creates documentation complete with trade-offs and a migration plan to guide module restructuring.

When do I need formal documentation like an ADR or RFC for software refactoring?

You need formal documentation like an ADR or RFC when a system becomes hard to change and requires a proposed refactoring strategy. It documents architectural decisions, trade-offs, and migration plans to coordinate module restructuring.

Can I analyze module boundaries and dependencies without integrating external tools?

Analyzing module boundaries and dependencies works without external tools by mapping module relationships internally. It assesses technical debt and calculates coupling metrics to propose concrete architectural improvements independently.