architecture

Enforce Manos file structure and import rules during code reviews.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/brianmontero18/astral --skill architecture-brianmontero18
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/brianmontero18/astral/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/brianmontero18/astral --skill architecture-brianmontero18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that file structure and imports follow Manos project patterns, helping teams maintain consistent architecture.

Core Features & Use Cases

  • Enforces proper file locations (tests in tests/, hooks in hooks/, types in types/, UI components in feature/ui-components/, etc.)
  • Detects cross-feature imports and ensures modules stay encapsulated within their feature boundaries
  • Provides guidance on remediation and promotes maintainability during PR reviews and architectural audits.

Quick Start

Run the architecture check to verify file placements and enforce feature encapsulation during PR reviews.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I enforce feature encapsulation and prevent cross-feature imports during code reviews?

Feature encapsulation is enforced by verifying module boundaries and detecting internal cross-feature imports during PR reviews. This ensures modules stay isolated within their feature directories, preventing unauthorized dependencies and maintaining project structure.

How do I check if file placements follow project patterns in a pull request?

File placement is checked against a rule-driven checklist that verifies tests reside in __tests__/, hooks in hooks/, types in types/, and UI components in feature/ui-components/. This validates correct locations during PR checks.

What is module encapsulation and how does it affect repo quality?

Module encapsulation restricts internal imports to within feature boundaries, preventing cross-feature dependencies. It improves repo quality by keeping components isolated, maintainable, and properly placed according to architectural patterns.

Can I use this architecture check for feature audits beyond standard PR reviews?

Architecture checks apply to feature audits as well as pull requests and PR checks. They verify placement, encapsulation, and module boundaries across the repository, detecting misplacements and overly large components during structural reviews.

What's the best way to detect misplacements and overly large components in a project structure?

Detecting misplacements and oversized components is best handled through rule-driven architectural checks that validate file locations and flag overly large components. This identifies structural violations and provides remediation guidance during audits.

Why does cross-feature importing violate module boundaries in project architecture?

Cross-feature importing violates module boundaries because it breaks encapsulation by creating dependencies between isolated features. Enforcing boundary rules prevents these violations and maintains consistent architecture across the project.