skills.rest
seanspiesman
seanspiesmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-patterns

Identify and standardize architectural decisions using ADR templates and common patterns.

Updated Jan 12, 2026
Search Tags:#anti-patterns#adr#event-driven#architecture-patterns#software-design#layered-architecture#repository-pattern
One-click install
npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill architecture-patterns-seanspiesman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/seanspiesman/Agents-and-Workflows/tree/main/custom-agents/skills/architecture-patterns
Command: npx skills add https://github.com/seanspiesman/Agents-and-Workflows --skill architecture-patterns-seanspiesman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Common software architectures often suffer from inconsistent patterns, undocumented decisions, and scattered guidance, making design reviews slower and riskier.

Core Features & Use Cases

  • ADR Templates: Standardized formats for recording decisions, contexts, and consequences.
  • Common Patterns: Layered Architecture, Repository Pattern, Service Layer, Event-Driven Architecture with concise explanations.
  • Anti-Patterns: Detection guidance and remediation suggestions.
  • Use Cases: Architecture reviews, system design planning, and documentation generation.

Quick Start

Provide a project goal and constraints to generate ADR-backed architecture guidance.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
How do I document software architecture decisions consistently?▼

You can document software architecture decisions using standardized Architecture Decision Record (ADR) templates to record contexts, decisions, and consequences for design reviews. This ensures consistent patterns and maintains system design quality.

What is the best way to identify anti-patterns in a layered architecture?▼

Identifying anti-patterns in a layered architecture involves using detection guidance to flag inconsistent patterns across layers, repositories, and services, then applying remediation suggestions to guide engineers toward robust architectures.

How does event-driven architecture compare to the repository pattern for system design?▼

Event-driven architecture handles asynchronous communication between services, while the repository pattern standardizes data access layers. Comparing them helps standardize architectural decisions using ADR templates during integration planning.

When do I need an ADR for software design?▼

You need an ADR for software design when you must standardize architectural decisions and record contexts during design reviews. It is applicable for integration planning across layers, repositories, services, and events.

Related Skills

Explore More Software Engineering Skills→
edumesonesedumesones

architecture-designer

Creates Architecture Decision Records and architecture overviews from project requirements.

Community
Intermediate
carlheathcarlheath
9

architecture

Design system architectures and generate Architecture Decision Records.

Community
Advanced
kabradshaw1kabradshaw1

go-service

Automates Go service layer implementation and review with clean-architecture standards.

Community
Advanced
groupzer0groupzer0
284

architecture-patterns

Standardize architecture patterns, ADRs, and anti-pattern detection for design reviews.

Community
Advanced