architect

Evaluate architectural patterns and generate ADRs for scalable systems.

66|16|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/RaheesAhmed/SajiCode --skill architect-raheesahmed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/RaheesAhmed/SajiCode/tree/main/skills/architect
Command: npx skills add https://github.com/RaheesAhmed/SajiCode --skill architect-raheesahmed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and evaluating scalable system architectures is complex and time-consuming; this skill guides teams to compare architectural patterns, document decisions, and align on robust designs.

Core Features & Use Cases

  • Evaluate architectural patterns (monolith, modular monolith, microservices, event-driven) and recommend suitable approaches.
  • Generate Architecture Decision Records (ADRs), reference architectures, and scalable infrastructure patterns for teams.
  • Use Case: when starting a new product, obtain a structured architecture plan and decision log to guide implementation.

Quick Start

Describe your system goals and constraints, and I will generate architecture recommendations and ADRs.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I evaluate and choose the right architecture pattern for a scalable system?▼

To evaluate architecture patterns for scalable systems, compare monoliths, modular monoliths, microservices, and event-driven designs against your specific requirements to recommend a suitable approach.

What is an Architecture Decision Record and when do I need one for system design?▼

An Architecture Decision Record (ADR) documents architectural decisions. You generate ADRs during system design to align teams on chosen patterns, maintain decision logs, and guide implementation.

How do I generate a reference architecture for a new product?▼

To generate a reference architecture, describe your system goals and constraints to receive structured architecture plans, scalable infrastructure recommendations, and decision logs for guiding implementation.

Can I use event-driven architecture for teams and projects of varying sizes?▼

Yes, event-driven architecture supports projects of varying sizes. The system evaluates event-driven patterns alongside microservices and monoliths to recommend scalable infrastructure tailored to your team.

What is the best way to document decisions when choosing between microservices and a monolith?▼

The best way to document decisions between microservices and monoliths is generating Architecture Decision Records, which provide a structured workflow to compare patterns, capture requirements, and align teams on designs.

When should I not use microservices for system design?▼

You should reconsider microservices when project constraints favor simpler patterns; evaluating modular monoliths or event-driven architectures might yield more robust and scalable designs for your team size.