Architecting Solutions

Design system architecture with modular component specifications and implementation options.

2|22|Updated Oct 9, 2025

Search Tags:#architecture #specifications #modularity #brick-philosophy #design-before-code

Ready to run

npx skills add https://github.com/rysweet/azlin --skill architecting-solutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecting Solutions
Source: https://github.com/rysweet/azlin/tree/main/.claude/skills/development/architecting-solutions
Command: npx skills add https://github.com/rysweet/azlin --skill architecting-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides architectural design before implementation, producing modular, regeneratable component specs.

Core Features & Use Cases

Problem decomposition and requirement gathering
2-3 architectural options with tradeoffs
Final recommended architecture with module specs

Quick Start

Start by describing the system and get architecture options.

Frequently Asked Questions about Architecting Solutions

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

FAQPage Schema

How do I design a modular architecture before coding?▼

Modular architecture breaks complex systems into simple, independent components with clear boundaries. Start by decomposing your problem into functional requirements, then generate 2-3 architectural options with tradeoffs, and select the one that best balances your constraints. Each module should be regeneratable and serve a single responsibility.

What's the best way to break down a complex feature into components?▼

Problem decomposition identifies the core requirements and dependencies, then maps them to discrete modules. Analyze what each component does, how it interfaces with others, and whether it can be built, tested, and replaced independently. This brick philosophy ensures components remain simple and maintainable.

When should I design architecture before implementation?▼

Design architecture before coding when planning new features, refactoring existing systems, or evaluating multiple implementation approaches. Early architectural decisions prevent costly rewrites and guide development by clarifying module responsibilities, data flow, and integration points.

How do I compare different architectural approaches for my system?▼

Evaluate 2-3 options by analyzing tradeoffs in complexity, scalability, maintainability, and implementation effort. Document how each approach satisfies functional requirements and aligns with your constraints. The recommended architecture emerges from this comparative analysis with detailed module specifications.

What makes a component truly modular and regeneratable?▼

Modular components have clear input/output contracts, minimal external dependencies, and single responsibilities. Regeneratable means you can rebuild or replace a component without cascading failures. Simple, well-specified modules enable teams to work in parallel and adapt to changing requirements.