system-architect

Design system architecture and select technology stacks from requirements.

32|Updated Feb 3, 2026

Search Tags:#architecture #security #scalability #system design #tech stack #microservices #NFR

Ready to run

npx skills add https://github.com/t0dorakis/murmur --skill system-architect-t0dorakis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/t0dorakis/murmur/tree/main/.agents/skills/system-architect
Command: npx skills add https://github.com/t0dorakis/murmur --skill system-architect-t0dorakis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms requirements into comprehensive technical architectures, addressing functional and non-functional needs with justified technology choices and documented decisions.

Core Features & Use Cases

Architecture Design: Creates detailed system blueprints based on PRDs or tech specs.
Technology Stack Selection: Recommends and justifies technology choices.
NFR Mapping: Systematically addresses scalability, security, performance, and other non-functional requirements.
Use Case: Kickstart a new project by generating a complete architecture document, including component designs, data models, and API specifications, ensuring all requirements are met from the outset.

Quick Start

Use the system architect skill to design the architecture for a new e-commerce platform based on the provided requirements document.

Frequently Asked Questions about system-architect

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

FAQPage Schema

How do I design system architecture from a requirements document?▼

Designing system architecture from requirements involves mapping functional needs and NFRs into detailed blueprints, defining components, interfaces, and data models to ensure all project requirements are systematically met.

How do I map non-functional requirements for scalability and security?▼

Mapping non-functional requirements for scalability and security involves systematically addressing NFRs during architecture design, ensuring performance and security constraints are documented and resolved through justified technology choices.

What is the best way to select a technology stack for microservices?▼

Selecting a technology stack for microservices requires analyzing architectural patterns and performing trade-off analysis to recommend and justify technology choices that meet your specific scalability and performance needs.

Does this approach work for both monolith and microservices system design?▼

Yes, this system design approach works for both monolith and microservices architectures by performing architectural pattern selection and trade-off analysis tailored to your specific project scale.

How do I analyze trade-offs when choosing architectural patterns?▼

Analyzing trade-offs when choosing architectural patterns involves evaluating technology choices against non-functional requirements to document decisions and justify the selected system architecture for your project.