Design portable, scalable IT architectures with phased roadmaps and ADRs.
npx skills add https://github.com/MotWakorb/claude-agent-dev-team --skill it-architect
Please help me install this Agent Skill. Skill: it-architect Source: https://github.com/MotWakorb/claude-agent-dev-team/tree/main/it-architect Command: npx skills add https://github.com/MotWakorb/claude-agent-dev-team --skill it-architect
IT architecture is hard: making systems portable, scalable, and vendor-lock-in free requires disciplined design, documentation, and phased roadmaps.
Draft a Phase 1 architecture proposal for a new web application with a modular monolith and open-source components.
High-intent search queries and answers about installing and using this skill.
To design a scalable IT architecture, you can generate a two-phase proposal starting with an initial modular setup and advancing to a fully scaled microservices approach. This includes documenting architecture decisions, cost models, and operational considerations.
An Architecture Decision Record (ADR) captures trade-offs, exit paths, and rationale for system design choices. Documenting architecture decisions ensures vendor-lock-in free guidance and maintains portable technology selections across enterprise and startup scales.
Yes, this architectural design process applies directly to hybrid multi-cloud and on-prem contexts. It generates portable, open-source technology guidance tailored to your specific deployment environment while documenting cost and operational constraints.
You create a phased roadmap by drafting a Phase 1 proposal to get started with a modular monolith using open-source components, followed by Phase 2 planning to scale properly. This captures architecture decisions and operational considerations.
The best way to avoid vendor lock-in is by selecting open-source, portable technologies and documenting exit paths in ADRs. This approach ensures your multi-cloud architecture maintains flexibility while capturing cost models and operational considerations.
Yes, this architecture design approach is explicitly applicable to both enterprise and startup scales. It accommodates microservices-first approaches and hybrid contexts, providing tailored cost models, phased roadmaps, and decision records for any organizational size.
OzeroHAXSelect system-level performance patterns for latency, throughput, or cost constraints.
cardinalconseilsConstructs evidence-based business models and a defensible monetization plan.
vanducngCompares multiple technology options across structured criteria to inform decisions.
MrAlexisCordAdvise on technology stack selection and system architecture design.
