pact-architecture-patterns
ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance. Provides proven architectural patterns including microservices, layered architecture, event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns. Use when: designing system architecture, creating component diagrams, defining interfaces, planning component boundaries, choosing architectural patterns, organizing system modules, or when user mentions: architecture, components, system design, diagrams, C4, microservices, API contracts, service boundaries, architectural patterns. Use for: component design, interface definition, system boundaries, dependency management, architecture documentation, design patterns, integration patterns. DO NOT use for: code implementation details, specific framework syntax, database schema design, frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance. Provides proven architectural patterns including microservices, layered architecture, event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns. Use when: designing system architecture, creating component diagrams, defining interfaces, planning component boundaries, choosing architectural patterns, organizing system modules, or when user mentions: architecture, components, system design, diagrams, C4, microservices, API contracts, service boundaries, architectural patterns. Use for: component design, interface definition, system boundaries, dependency management, architecture documentation, design patterns, integration patterns. DO NOT use for: code implementation details, specific framework syntax, database schema design, frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!