architecture

Guides architectural decision-making through requirements analysis, trade-off evaluation, and ADR documentation.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/nperepichka/Antigravity --skill architecture-nperepichka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/nperepichka/Antigravity/tree/main/config/skills/architecture
Command: npx skills add https://github.com/nperepichka/Antigravity --skill architecture-nperepichka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right architecture is hard: teams often over-engineer simple projects or under-design systems that later fail to scale. This Skill provides a structured framework for gathering requirements, evaluating trade-offs, selecting patterns, and documenting decisions as Architecture Decision Records (ADRs). ## Core Features & Use Cases - Context Discovery: A question hierarchy covering scale, team, timeline, domain, and constraints, plus a project classification matrix (MVP, SaaS, Enterprise). - Pattern Selection: Decision trees for data access, domain logic, distributed systems, and real-time requirements, with anti-pattern red flags and complexity ratings. - Trade-off Analysis & ADRs: Templates for documenting options, rationale, accepted trade-offs, consequences, and revisit triggers. - Use Case: A team starting a new SaaS product uses the classification matrix to confirm a modular monolith fits their 5-10 developer team, then writes an ADR justifying PostgreSQL and the Repository pattern with explicit trade-offs. ## Quick Start Ask the agent to help design the architecture for a new project by analyzing requirements, comparing pattern options, and drafting an ADR for the key decisions.

Frequently Asked Questions about architecture

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

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

Choose microservices only when all three conditions hold: clear domain boundaries, a team larger than 10 developers, and different scaling needs per service. Otherwise start with a modular monolith and extract services later when the need is proven.

How do I write an Architecture Decision Record (ADR)?▼

An ADR documents the context and problem, the options considered with pros and cons, the chosen decision, rationale tied to constraints, accepted trade-offs, consequences, and a revisit trigger. Store ADRs as numbered markdown files under docs/architecture/.

When should I use the Repository pattern versus direct ORM access?▼

Use the Repository pattern when you need testability, complex queries, or multiple data sources. For simple CRUD against a single database, direct ORM access with tools like Prisma or Drizzle is simpler and preferable.

What questions should I ask before designing a system architecture?▼

Ask about scale (users, data volume, transaction rate), team size and expertise, timeline pressure, domain complexity and compliance needs, and constraints like budget, legacy integrations, and technology preferences before proposing any architecture.

When is event-driven architecture the wrong choice?▼

Event-driven architecture is a poor fit for simple workflows requiring strong consistency, since it introduces eventual consistency and operational complexity. Prefer synchronous REST or GraphQL when real-time updates and loose coupling are not required.