architecture-and-planning

Design system architectures and plan projects before implementation.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Jaydpatel01/.github --skill architecture-and-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-and-planning
Source: https://github.com/Jaydpatel01/.github/tree/main/skills/architecture-and-planning
Command: npx skills add https://github.com/Jaydpatel01/.github --skill architecture-and-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design robust, scalable, and maintainable system architectures and plan projects effectively before diving into implementation, preventing costly future refactors.

Core Features & Use Cases

  • Architectural Pattern Selection: Guides you in choosing the right pattern (Monolith, Microservices, Event-Driven, CQRS, Serverless) based on project needs.
  • Technology Stack Guidance: Provides criteria and reference patterns for selecting appropriate technologies.
  • Design Process: Outlines a step-by-step approach including ADRs, diagrams, service boundaries, data architecture, API contracts, and cross-cutting concerns.
  • Use Case: When starting a new SaaS product, use this Skill to define the core architecture, select the tech stack (e.g., PostgreSQL, FastAPI, React), and plan the initial service boundaries and API designs.

Quick Start

Use the architecture-and-planning skill to design a scalable microservices architecture for a new e-commerce platform.

Frequently Asked Questions about architecture-and-planning

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

FAQPage Schema
How do I design a scalable microservices architecture before starting implementation?▼

Design scalable microservices architecture by selecting appropriate architectural patterns, defining service boundaries, data flows, and API contracts, and generating Architecture Decision Records to prevent costly future refactors.

What is the best way to plan system design for a new SaaS product?▼

The best way to plan system design for a SaaS product involves outlining a step-by-step approach to select the technology stack, define core components, and establish cross-cutting operational concerns prior to coding.

When do I need to create Architecture Decision Records for system design?▼

Create Architecture Decision Records during the system design phase to document architectural pattern selections, technology stack criteria, and service boundary definitions for maintainable project planning.

How to choose the right architectural pattern between Monolith, Event-Driven, and Serverless?▼

Choose the right architectural pattern by evaluating project needs against the characteristics of Monolith, Microservices, Event-Driven, CQRS, and Serverless models to ensure production-grade scalability.

Can I use this approach to define service boundaries and data flows for an e-commerce platform?▼

Yes, you can use this approach to define service boundaries, data architecture, and API contracts for an e-commerce platform to establish a robust, maintainable system architecture.

What are the limitations of planning architecture before tech stack selection?▼

Planning architecture without tech stack selection limits your ability to define concrete API contracts and cross-cutting concerns, making it harder to guide the selection of appropriate technologies like PostgreSQL or FastAPI.