architect

Guide software architecture decisions and evaluate trade-offs for system design.

Updated Feb 2, 2026

Search Tags:#architecture #decision making #scalability #system design #adr #technical debt

Ready to run

npx skills add https://github.com/echarabati/adi-capital-admin --skill architect-echarabati

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/echarabati/adi-capital-admin/tree/main/.agent/skills/roles/architect
Command: npx skills add https://github.com/echarabati/adi-capital-admin --skill architect-echarabati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides expert guidance on technical decisions, system design, and trade-off evaluations, ensuring technical integrity, scalability, and maintainability without unnecessary complexity.

Core Features & Use Cases

Architectural Decision Records (ADRs): Documents significant technical decisions, their rationale, and consequences.
System Design: Evaluates trade-offs for new features or dependencies, ensuring alignment with project goals and constraints.
Use Case: When considering adding a new third-party service, this Skill can evaluate its integration cost, security implications, and long-term maintainability against existing patterns.

Quick Start

Consult the architect skill for a technical decision on integrating a new payment gateway.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I document technical decisions to avoid accumulating technical debt?▼

You can document technical decisions by creating Architectural Decision Records (ADRs) that capture the rationale, context, and consequences of significant choices, ensuring system maintainability and preventing technical debt accumulation over time.

What is the best way to evaluate trade-offs when integrating a new third-party dependency?▼

Evaluating trade-offs for new dependencies involves analyzing integration costs, security implications, and long-term maintainability against existing architectural patterns and constraints to ensure the system retains its technical integrity and scalability.

When do I need to review system design for scalability and maintainability?▼

You need to review system design when considering new features, adding dependencies, or making architectural changes, ensuring the modifications align with project goals, constraints, and established patterns without introducing unnecessary complexity.

How does evaluating architectural changes maintain system integrity?▼

Evaluating architectural changes maintains system integrity by assessing the impact of new features or dependencies against established patterns and constraints, ensuring technical decisions support long-term scalability and maintainability without unnecessary complexity.

Can I use this to assess the integration cost of a new payment gateway?▼

Yes, you can assess the integration cost of a new payment gateway by evaluating its security implications, long-term maintainability, and alignment with existing system patterns to ensure the architectural decision supports project goals.