architecture

Analyze software architecture requirements and recommend defensible design decisions.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/pckienuit/GameDev1 --skill architecture-pckienuit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/pckienuit/GameDev1/tree/main/.cursor/skills/architecture
Command: npx skills add https://github.com/pckienuit/GameDev1 --skill architecture-pckienuit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make clear, defensible architecture decisions when a project is becoming more complex and you need to choose between competing design options.

Core Features & Use Cases

  • Requirements Discovery: Clarifies scale, team, timeline, domain, and constraint assumptions before recommending a direction.
  • Pattern Selection: Compares architectural patterns such as monoliths, modular monoliths, microservices, DDD, CQRS, and event-driven approaches.
  • Trade-off Analysis: Frames each decision in terms of benefits, costs, risks, and future migration paths.
  • ADR Guidance: Helps document architectural decisions so teams can revisit them with context later.
  • Use Case: A small team planning a long-term product can use this Skill to decide whether a modular monolith is a better fit than microservices.

Quick Start

Ask the architecture skill to evaluate your project constraints and recommend the simplest architecture that satisfies your requirements.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I evaluate software architecture trade-offs for a new system design?

Evaluating software architecture trade-offs requires framing each design decision in terms of benefits, costs, risks, and future migration paths. This Skill analyzes your project constraints to recommend the simplest defensible architecture.

What is the best way to choose between a modular monolith and microservices?

Choosing between a modular monolith and microservices depends on your team size, timeline, and scaling requirements. This Skill compares architectural patterns against your specific constraints to recommend the most appropriate fit.

How do I write an Architecture Decision Record for system design changes?

Writing an Architecture Decision Record (ADR) involves documenting your architectural choices with clear constraints, simpler alternatives, and rationale. This Skill provides ADR guidance so teams can revisit decisions with full context.

When do I need requirements analysis for architectural pattern selection?

Requirements analysis for architectural pattern selection is needed when a project becomes more complex and you must choose between competing design options. This Skill clarifies scale, domain, and constraint assumptions before recommending a direction.

Does event-driven architecture or CQRS fit small team software engineering projects?

Event-driven architecture and CQRS can fit small team projects if your domain requirements justify the complexity. This Skill evaluates your specific constraints to recommend the simplest architecture that satisfies your requirements.