architect

Design scalable software architectures with ADRs, component diagrams, and API contracts.

Updated Mar 25, 2026

Search Tags:#architecture #scalability #adr #risk-management #cicd #system-design

Ready to run

npx skills add https://github.com/AlexHorovitz/skills --skill architect-alexhorovitz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/AlexHorovitz/skills/tree/main/architect
Command: npx skills add https://github.com/AlexHorovitz/skills --skill architect-alexhorovitz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architect Skill guides teams to design scalable, maintainable software architectures that are deployable from Day 1 and platform-aware across web, macOS, iOS, Android, and headless backends.

Core Features & Use Cases

Establish architectural patterns, boundaries, and trade-offs for a project’s current scale and constraints.
Produce actionable artifacts such as ADRs, component diagrams, data models, API contracts, and integration contracts to support production-ready systems.
Evaluate platform targets, data boundaries, deployment strategies, and CI/CD prerequisites early in the project lifecycle.

Quick Start

Provide a high-level architecture outline for a new project given its constraints and platform targets.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I design a scalable software architecture for a new project?▼

Designing scalable architecture requires establishing patterns, boundaries, and trade-offs for your project's scale, producing artifacts like ADRs and component diagrams to ensure deployment readiness from Day 1.

What architectural artifacts do I need for a production-ready system?▼

Production-ready system architectural artifacts include ADRs, component diagrams, data models, API contracts, integration contracts, risk assessments, and CI/CD prerequisites to support maintainable deployment.

Can I use a single architecture design across web, iOS, and Android platforms?▼

Platform-aware architecture design evaluates web, macOS, iOS, Android, and headless backend targets to establish unified architectural boundaries, data models, and integration contracts during project initiation.

When should I evaluate CI/CD prerequisites and deployment strategies?▼

Evaluate CI/CD prerequisites, deployment strategies, and data boundaries early in the project lifecycle during initiation and architectural design reviews to ensure Day 1 deployment readiness.

What's the best way to document architectural decisions and risk management?▼

Document architectural decisions and risk management by generating Architecture Decision Records (ADRs) and conducting risk assessments during project initiation and architectural design reviews.

How do architectural trade-offs impact system design and maintainability?▼

Architectural trade-offs impact system design and maintainability by defining structural boundaries and patterns that balance current scale constraints against platform expansion and deployment readiness.