architecture

Create architecture decision records and evaluate system design proposals with structured trade-off analysis.

3|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill architecture-ruskicoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/architecture
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill architecture-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between technologies or documenting design decisions often happens ad hoc, leaving teams without a record of why a choice was made or what alternatives were considered. This Skill produces a structured Architecture Decision Record (ADR) capturing context, options, trade-offs, and consequences. ## Core Features & Use Cases - ADR Creation: Generates a complete ADR with status, context, decision, options comparison tables, trade-off analysis, consequences, and action items. - Design Evaluation: Reviews existing system design proposals and microservices architectures against stated constraints. - System Design from Requirements: Designs new components from requirements and constraints, with guidance to state non-functional requirements like latency, cost, and team expertise. - Use Case: When deciding between Kafka and SQS for an event bus, invoke the skill to receive a side-by-side options comparison with pros, cons, and a documented decision rationale. ## Quick Start Ask the assistant to create an ADR comparing Kafka versus SQS for your event bus, including your constraints such as timeline and throughput requirements.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I write an architecture decision record?

An ADR documents the context, the decision, the options considered with pros and cons, trade-off analysis, and consequences. This skill generates that structure automatically when you describe the decision, such as choosing between Kafka and SQS.

How do I compare two technologies like Kafka vs SQS?

State the decision and your constraints, and the skill produces an options comparison table covering complexity, cost, scalability, and team familiarity for each alternative, followed by a trade-off analysis and recommendation.

Can this skill review an existing system design proposal?

Yes. Provide the proposal, such as a microservices design, and the skill evaluates it against your stated requirements and constraints, highlighting trade-offs and consequences.

What information should I include when requesting an architecture decision?

State constraints upfront such as deadlines and throughput targets, name the candidate options explicitly, and include non-functional requirements like latency, cost, team expertise, and maintenance burden for a balanced analysis.

When should I use the system-design skill instead of an ADR?

Use the system-design skill for detailed frameworks on requirements gathering, scalability analysis, and trade-off evaluation. Use this architecture skill when the goal is documenting or evaluating a specific decision in ADR format.