architect-agent

Design and evaluate scalable system architectures for cloud and on-prem environments.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill architect-agent-unnamedmistress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-agent
Source: https://github.com/unnamedmistress/menuspy-marketing/tree/main/architect-agent
Command: npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill architect-agent-unnamedmistress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

System architecture and technical design guidance to help teams evaluate trade-offs, design data flows, and address scalability and security concerns.

Core Features & Use Cases

  • Component design and interactions
  • Data flow and storage strategies
  • Trade-off analysis (cost vs performance vs complexity)
  • Security architecture and threat modeling
  • Scalability and reliability patterns
  • Technology selection and justification
  • Integration points and APIs

Quick Start

Provide a scalable, secure system architecture for a given problem by outlining components, data flows, and security controls.

Frequently Asked Questions about architect-agent

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

FAQPage Schema
How do I design a scalable system architecture for complex software?

Design scalable system architecture by outlining components, data flows, deployment patterns, and scalability strategies. Evaluate trade-offs across cost, performance, and complexity to ensure reliable component interactions and technology selection.

What is included in a system architecture and threat modeling evaluation?

Architecture and threat modeling evaluation includes security architecture controls, risk mitigations, and data flow diagrams. It assesses integration points and APIs to address security concerns across cloud and on-prem environments.

How do I evaluate trade-offs between cost, performance, and complexity in system design?

Evaluate trade-offs in system design by analyzing technology stack rationales and deployment patterns. Compare component interactions and storage strategies against scalability requirements to justify technology selection.

Can I use this approach for both cloud and on-prem environment deployments?

Yes, this approach applies to both cloud and on-prem environments. It provides deployment pattern guidance and integration point analysis to map data flows and security models across diverse infrastructure configurations.

What's the best way to plan data flows and storage strategies for a new system?

Plan data flows and storage strategies by mapping component interactions and data flow diagrams. Define integration points, APIs, and storage mechanisms while addressing scalability and reliability patterns for complex systems.

When should I not use a broad system design approach for my architecture?

Avoid broad system design approaches when specific components lack defined integration points or APIs. Without clear data flow diagrams and security models, generalized architecture patterns cannot properly address targeted scalability constraints.