skills.rest
mkalkere
mkalkereCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Evaluate and design system architecture and API design with ADRs.

4|Updated Feb 1, 2026
Search Tags:#design#architecture#adr#patterns#trade-offs#api-design
One-click install
npx skills add https://github.com/mkalkere/agent-coordinator --skill architecture-mkalkere
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/development/architecture
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill architecture-mkalkere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate and design system architecture and API design to guide end-to-end decisions, ensuring scalable, maintainable, and well-documented systems.

Core Features & Use Cases

  • Architecture pattern selection and component design to support scalable, maintainable systems.
  • API design with contracts, versioning, and clear failure handling for reliable integrations.
  • Documentation of architectural decisions through ADRs, trade-offs, and rationale to align stakeholders.

Quick Start

Begin by clarifying requirements and constraints, then outline a complete architecture plan for a target system.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I select the right system architecture patterns and document trade-offs for a new application?▼

To select system architecture patterns, evaluate functional and non-functional requirements, map out component interfaces, and document architectural trade-offs using ADRs to align stakeholders on design decisions.

What is the best way to design robust APIs with clear failure handling and versioning?▼

Designing robust APIs involves defining clear contracts, implementing API versioning strategies, and establishing explicit failure handling mechanisms to ensure reliable and maintainable system integrations.

How do I evaluate an existing system architecture across data flows and deployment patterns?▼

Evaluate existing system architecture by analyzing current data flows, reviewing component interfaces, and assessing deployment patterns against real-world product contexts to identify scalability and maintainability gaps.

When do I need to write Architecture Decision Records for my software design?▼

You need to write Architecture Decision Records when selecting architectural patterns or defining component interfaces, ensuring the rationale and trade-offs of your system architecture are documented for stakeholders.

How do I articulate functional and non-functional requirements for scalable system design?▼

Articulate functional and non-functional requirements by clarifying product constraints upfront, which then guides the selection of architectural patterns and component design for scalable and maintainable systems.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
maggitmaggit

eng-spec

Translate product requirements into detailed engineering specifications with architecture, data models, and API contracts.

Community
Advanced
ThrookieThrookie
2

project-guidelines-example

Generate project guidelines and architectural templates from a predefined blueprint.

Community
Intermediate
Joncik91Joncik91
29

architect

Creates architectural decision records and evaluates system design options.

Community
Advanced