architect

Design and evaluate scalable software architectures with component boundaries and trade-offs.

5|Updated Jan 20, 2026

Search Tags:#architecture #scalability #adr #modularity #trade-offs #system-design

Ready to run

npx skills add https://github.com/Bamose/everything-codex-cli --skill architect-bamose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Bamose/everything-codex-cli/tree/main/skills/architect
Command: npx skills add https://github.com/Bamose/everything-codex-cli --skill architect-bamose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design scalable, maintainable software architectures and make informed architectural decisions.

Core Features & Use Cases

Analyze current architecture and document patterns, debt, and bottlenecks.
Propose high-level designs, component responsibilities, and ADRs.
Define architectural principles, patterns, and governance for consistent development.

Quick Start

Provide a high-level architectural plan for a new feature by analyzing the current system and outlining trade-offs and decisions.

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 feature?▼

Document architectural decisions by creating ADRs that capture component responsibilities, data models, interfaces, and non-functional requirements to ensure consistent development and system modularity.

What is the best way to plan a major system migration across a complex codebase?▼

Evaluate an existing architecture by analyzing system patterns, identifying technical debt and bottlenecks, and proposing high-level designs that emphasize modularity, scalability, and security.

How do I document trade-offs and architectural decisions for a system refactor?▼

Document trade-offs and architectural decisions for a system refactor by detailing component boundaries and generating ADRs that outline non-functional requirements, data models, and interfaces.

When should I define architectural principles and governance for my software system?▼

Define architectural principles and governance when planning major refactors or feature rollouts to establish patterns that guide consistent development, maintain modularity, and ensure system scalability.