Architecture

Review system architecture for structural patterns, data flow, and module boundaries.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill architecture-sheldon-92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture
Source: https://github.com/Sheldon-92/TAD/tree/main/.tad/skills/architecture
Command: npx skills add https://github.com/Sheldon-92/TAD --skill architecture-sheldon-92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural reviews help teams identify and resolve design issues that hinder scalability, maintainability, and alignment with best practices by evaluating structure, data flow, and module boundaries.

Core Features & Use Cases

  • Review structural patterns (layered, clean, hexagonal) and their applicability to the system.
  • Assess data flow, responsibilities, integration points, and boundary definitions.
  • Provide actionable recommendations and documentation (e.g., ADRs) to guide refactors and evolution.

Quick Start

Describe your current system design and request a structured architecture review.

Frequently Asked Questions about Architecture

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

FAQPage Schema
How do I review system architecture to prevent anti-patterns and ensure scalable design?

To review system architecture for scalable design, describe your current system and request a structured review. This validates structural decisions, assesses data flow traceability, and identifies anti-patterns across module boundaries to ensure maintainability.

What is the best way to evaluate structural patterns like layered, clean, or hexagonal architecture for my system?

Evaluating structural patterns like layered, clean, or hexagonal architecture requires assessing their applicability to your current system boundaries and integration points. A structured architecture review validates these patterns against your specific data flow responsibilities and modular boundaries.

How do I validate microservices module boundaries and data flow traceability during a feature refactor?

To validate microservices module boundaries and data flow traceability during a feature refactor, apply an architecture review to evaluate integration points and structural patterns. This identifies boundary definition issues and ensures maintainable designs across your distributed system.

When do I need architecture documentation like ADRs for my systems design?

You need architecture decision records (ADRs) for systems design during design phases, feature refactors, and architecture reviews. ADRs provide actionable documentation to guide system evolution, satisfy structural pattern requirements, and track modular boundary decisions.

Can I use an architecture review to assess data flow responsibilities and integration points across microservices?

Yes, you can use an architecture review to assess data flow responsibilities, integration points, and boundary definitions across microservices. It evaluates structural patterns and provides actionable recommendations to resolve design issues that hinder scalability and maintainability.