architect-inspect

Map and analyze architecture around a top-level file to reveal boundaries and dependencies.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill architect-inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-inspect
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/architect-inspect
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill architect-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and document the architecture around a specified top-level file, clarifying boundaries, responsibilities, and potential risks.

Core Features & Use Cases

  • Classify the entry file's architectural role (route, feature entry, domain service, UI container).
  • Map inbound callers and outbound dependencies to reveal coupling and data flow.
  • Produce a structured architecture inspection report with findings, risks, and recommended next steps.

Quick Start

Provide the path to a top-level file and an optional output path to generate a detailed architecture inspection.

Frequently Asked Questions about architect-inspect

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

FAQPage Schema
How do I analyze a component's architecture from a top-level file?

To analyze a component's architecture, you provide the path to a top-level file, and the system maps inbound callers and outbound dependencies to reveal boundaries, data flow, and risks in a structured inspection report.

What is architectural role classification for a feature entry file?

Architectural role classification identifies the function of a top-level file within a system, categorizing it as a route, feature entry, domain service, or UI container to clarify its boundaries and responsibilities.

How do I map inbound and outbound dependencies for a system design review?

Mapping inbound and outbound dependencies traces data flow and coupling around a top-level file, revealing how components interact and highlighting potential architectural risks for system design reviews.

Can I use an architecture inspection report for code refactoring and onboarding?

An architecture inspection report is suitable for refactoring and onboarding, providing a clear architectural snapshot from a starting file that includes findings, risks, and recommended next steps.

What is the best way to assess architectural risks and boundaries in a codebase?

The best way to assess architectural risks and boundaries is to map the architecture around a top-level file, tracing dependencies and data flow to produce a structured inspection report with recommended next steps.