pact-architecture-patterns

Recommend architectural patterns and generate C4 diagrams for system design.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/v4lheru/linkedin-comments-telegram --skill pact-architecture-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pact-architecture-patterns
Source: https://github.com/v4lheru/linkedin-comments-telegram/tree/main/.claude/skills/pact-architecture-patterns
Command: npx skills add https://github.com/v4lheru/linkedin-comments-telegram --skill pact-architecture-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing scalable, maintainable systems is hard. This Skill provides proven architectural patterns and reference templates to help you choose the right pattern, document boundaries, and craft implementation-ready specs, reducing guesswork and risk.

Core Features & Use Cases

  • Architectural patterns: Layered, Microservices, Event-Driven, Hexagonal, CQRS, and design anti-pattern guidance.
  • C4 diagram templates & API contract references: ready-to-use templates to communicate structure and interfaces.
  • Use Case: When starting a new system, quickly select a pattern, define module boundaries, and generate a C4 container diagram and interfaces.

Quick Start

Ask for a system description and receive recommended architectural patterns, boundaries, and a C4 diagram outline.

Frequently Asked Questions about pact-architecture-patterns

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

FAQPage Schema
How do I choose the right architectural pattern for my system design?

Architectural patterns like layered, microservices, event-driven, hexagonal, and CQRS each solve different scalability and maintainability challenges. Provide your system description to receive pattern recommendations with trade-offs and decision workflows tailored to your constraints.

What's the best way to document system architecture with C4 diagrams?

C4 diagrams communicate system structure across context, container, component, and code levels. This Skill provides ready-to-use C4 templates and container diagram outlines so you can quickly document module boundaries and interfaces without starting from scratch.

How do I design APIs that follow architectural patterns?

API contracts define interfaces between system components and external consumers. This Skill generates API contract references aligned with your chosen pattern, ensuring consistency with your architecture's boundaries and interaction model.

What architectural anti-patterns should I avoid in system design?

Anti-pattern guidance identifies common pitfalls in layered, microservices, event-driven, and other patterns. Recognizing these traps helps prevent design flaws that lead to maintainability and scalability problems later.

Can I use CQRS or event-driven patterns for my domain?

CQRS and event-driven patterns suit systems requiring clear separation of read and write concerns or loose coupling across services. This Skill assesses your domain requirements and provides implementation-ready guidance with examples for patterns that fit your use case.