architecture

Define system boundaries, quality attributes, and API contracts in ADRs.

Updated Apr 19, 2026

Search Tags:#architecture #documentation #adr #system-design #api-contract

Ready to run

npx skills add https://github.com/saranskumar/anti-slop --skill architecture-saranskumar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/architecture
Command: npx skills add https://github.com/saranskumar/anti-slop --skill architecture-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are hard to change later, and making the wrong choices early can cost far more to fix. This skill helps you reason about structure, boundaries, and trade-offs before committing to an approach.

Core Features & Use Cases

Define system boundaries and scope to prevent scope creep.
Evaluate and prioritize quality attributes (availability, security, scalability) to guide trade-offs.
Create and maintain Architecture Decision Records (ADRs) and define API contracts before implementation.
Choose appropriate architectural patterns (monolith vs. service boundaries) and document the rationale.

Quick Start

Outline a high-level architecture for your project, defining system boundaries, key components, and initial ADRs to guide implementation.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I define system boundaries to prevent scope creep during project initiation?▼

Defining system boundaries early prevents scope creep by isolating features into distinct components. This approach ensures structural integrity and guides development decisions before committing to a specific architectural pattern.

When do I need to create Architecture Decision Records for a software project?▼

Create Architecture Decision Records when making structural choices that are hard to change later, such as choosing architectural patterns. Documenting rationale ensures repeatable, auditable outcomes during refactoring or major feature planning.

What is the best way to evaluate quality attributes like scalability and reliability before implementation?▼

Evaluating quality attributes requires prioritizing trade-offs between availability, security, and scalability. This ensures boundaries and quality attributes are defined early to guide implementation and prevent costly architectural fixes later.

How do I define API contracts and data modeling for a new system architecture?▼

Defining API contracts involves specifying data modeling and component interactions before implementation begins. This ensures system boundaries are respected and provides a clear guide for downstream development decisions.

Can I use this approach for both monolithic and service-oriented system design?▼

Yes, this approach supports choosing appropriate architectural patterns, including monolith versus service boundaries. It helps evaluate structural trade-offs and document the rationale for whichever pattern fits your scalability needs.