architect

Analyze system architecture and generate architectural decision records.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/zapabob/Skills --skill architect-zapabob
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/zapabob/Skills/tree/main/registry/skills/architect/variants/cursor
Command: npx skills add https://github.com/zapabob/Skills --skill architect-zapabob

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the analysis of system architecture, design patterns, module boundaries, and scalability, providing actionable recommendations and architectural decision records.

Core Features & Use Cases

  • Architecture Analysis: Deep dives into project structure, languages, frameworks, and entry points.
  • Design Pattern Detection: Identifies common design patterns within the codebase.
  • Scalability Assessment: Evaluates concurrency models, data layers, and potential bottlenecks.
  • ADR Generation: Creates templates for documenting architectural decisions.
  • Use Case: A new developer joins a complex project and needs to understand its architecture. This Skill can provide a comprehensive overview, identify key patterns, and highlight areas for potential improvement or scalability concerns.

Quick Start

Run the architect skill to analyze the current system architecture and generate a report.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I analyze system architecture and identify design patterns in my codebase?

System architecture analysis involves deep diving into project structure, languages, and frameworks to detect design patterns and assess module boundaries. This process generates high-level design recommendations and actionable architectural reports.

What is the best way to document architectural decisions for a complex software project?

Documenting architectural decisions is best achieved by generating Architectural Decision Records (ADR). ADR templates capture the context, decision, and consequences of a design choice, ensuring system design rationale is transparent for new developers.

How do I assess scalability and concurrency bottlenecks in a software system?

Scalability assessment evaluates concurrency models, data layers, and potential bottlenecks within the codebase. By analyzing system architecture, you can identify areas for potential improvement and highlight scalability concerns.

Can I use automated tools to understand a complex project structure when onboarding new developers?

Automated architecture analysis tools process project structure, entry points, and frameworks to provide a comprehensive overview. This helps new developers understand system design, module boundaries, and key patterns quickly.

Does architecture analysis work for evaluating module boundaries and data layers?

Architecture analysis evaluates module boundaries, data layers, and concurrency models directly. It detects common design patterns within the codebase and highlights potential bottlenecks to ensure robust system design.

When should I generate an ADR template for my software architecture?

You should generate an ADR template when making significant high-level design decisions or assessing scalability. It documents architectural choices, detected design patterns, and module boundaries for future reference.