agent-architecture-designer

Name: agent-architecture-designer
Availability: InStock
Author: seqis

Select application, API, and data patterns with validation evidence for ADRs.

Updated Aug 23, 2026

Search Tags:#design #architecture #api design #validation #microservices #adr

Ready to run

npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-architecture-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-architecture-designer
Source: https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code/tree/main/skills_tree/agent-architecture-designer
Command: npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-architecture-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that proposed software architectures are validated through prototyping and testing before they are recommended, preventing technical debt from untested designs.

Core Features & Use Cases

Architecture Pattern Selection: Provides guidance on application, API, and data patterns.
Validation Protocol: Enforces a rigorous process of building prototypes, testing integrations, and measuring performance.
ADR Creation: Documents decisions with evidence from validation.
Use Case: A team is deciding between microservices and a modular monolith. This skill guides them through selecting the appropriate pattern and outlines the necessary validation steps (e.g., building a sample service, testing inter-service communication) before a final decision is made and documented in an Architecture Decision Record (ADR).

Quick Start

Use the agent-architecture-designer skill to help validate a proposed microservices architecture by building a prototype.

Frequently Asked Questions about agent-architecture-designer

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

FAQPage Schema

How do I validate a microservices architecture before deployment?▼

Validate a microservices architecture by building a prototype, testing inter-service communication, and measuring performance. This ensures the proposed design is tested before recommendation, preventing untested technical debt.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents software architecture decisions with validation evidence. You need one when selecting application, API, or data patterns to ensure decisions are backed by prototyping and integration testing results.

How do I choose between a modular monolith and microservices architecture?▼

Choosing between a modular monolith and microservices requires selecting the appropriate application pattern and validating it through prototyping. You must build a sample service and test integrations before making a final architecture decision.

What's the best way to document API design patterns with validation evidence?▼

Document API design patterns by enforcing a validation protocol that includes prototyping, integration testing, and performance measurement. Record the gathered validation evidence within an Architecture Decision Record for the selected pattern.

Can I use this architecture validation process for data pattern selection?▼

Yes, the architecture validation process applies to data pattern selection. It enforces building prototypes and measuring performance for proposed data patterns before recommending them, ensuring the design is fully tested.

Why does architecture design require prototyping and integration testing?▼

Architecture design requires prototyping and integration testing to prevent technical debt from untested designs. This strict validation protocol ensures proposed software architectures perform adequately before they are formally recommended.