arch-agent

Define system architecture and produce technical design decisions for software systems.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Unicorn/Radium --skill arch-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-agent
Source: https://github.com/Unicorn/Radium/tree/main/skills/core/arch-agent
Command: npx skills add https://github.com/Unicorn/Radium --skill arch-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and engineers convert requirements, constraints, and business goals into a clear, actionable system architecture and technical decisions that guide implementation, deployment, and long-term evolution.

Core Features & Use Cases

  • High-level system design: Break systems into components and define responsibilities, interactions, and deployment topology.
  • Technology selection & trade-offs: Recommend stacks, frameworks, and infrastructure with justification tied to team skills and constraints.
  • Data and API design: Propose data models, database strategies, API contracts, and integration patterns.
  • Reliability, security, and scaling: Provide caching, partitioning, monitoring, and disaster recovery approaches.
  • Documentation & governance: Produce Architecture Decision Records (ADRs), diagrams, and risk/mitigation plans.
  • Use Case: Designing a multi-tenant SaaS platform, migrating a monolith to microservices, or specifying real-time analytics infrastructure.

Quick Start

Draft a system architecture for a multi-service SaaS platform that must support 10,000 concurrent users, real-time updates, and multi-tenant isolation.

Frequently Asked Questions about arch-agent

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

FAQPage Schema
How do I design system architecture for a multi-tenant SaaS platform?

To design system architecture for a multi-tenant SaaS platform, you define component responsibilities, data models, and deployment topology. This produces component diagrams, API contracts, and deployment strategies addressing multi-tenant isolation, reliability, and maintainability requirements.

What goes into an Architecture Decision Record for microservices migration?

An Architecture Decision Record for microservices migration documents technology selection trade-offs, API contracts, and deployment strategies. It captures risk and mitigation plans alongside component diagrams to justify architectural choices and guide long-term system evolution.

How do I choose a technology stack for a real-time analytics system?

Choosing a technology stack for a real-time analytics system involves recommending frameworks and infrastructure justified by team skills and constraints. The selection evaluates trade-offs to address specific scalability, reliability, and performance requirements for the real-time platform.

Does this system design approach work for high-level web service planning?

Yes, this system design approach works for high-level web service planning by defining component interactions and deployment topology. It applies to architecture tasks during planning and reviews, producing technical design decisions that guide implementation and long-term evolution.

What is the best way to define API contracts and data models for scalable web services?

The best way to define API contracts and data models for scalable web services is to propose database strategies and integration patterns. This ensures the data and API design directly addresses scalability, security, and maintainability requirements specified during architecture planning.