Skip to content
Back to skills

Architecture Patterns

ASecurity

This skill should be used when designing system architecture, making architectural decisions, or evaluating design patterns. It provides guidance on common patterns, ADR templates, design principles, and tradeoff analysis.

  • 34 stars
  • 0 votes
  • 1 copy
  • 47 views
  • Added December 19, 2025
developmentdocumentation

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add akaszubski/autonomous-dev --skill architecture-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Architecture Patterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Architecture Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/akaszubski-architecture-patterns/badge)](https://www.skillsdirectory.com/skills/akaszubski-architecture-patterns)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: architecture-patterns
version: 1.0.0
type: knowledge
description: This skill should be used when designing system architecture, making architectural decisions, or evaluating design patterns. It provides guidance on common patterns, ADR templates, design principles, and tradeoff analysis.
keywords: architecture, design, pattern, decision, tradeoffs, adr, system design, scalability, microservices, mvc, design patterns, solid
auto_activate: true
allowed-tools: [Read]
---

# Architecture Patterns Skill

Architectural design patterns, decision frameworks, and system design principles.

## When This Skill Activates


- Designing system architecture
- Writing Architecture Decision Records (ADRs)
- Evaluating design patterns
- Making architectural tradeoffs
- System design questions
- Keywords: "architecture", "design", "pattern", "adr", "system design", "scalability"


---

## Core Concepts

### Overview

This skill provides comprehensive guidance on architecture patterns. For detailed patterns and implementation examples, see the documentation files in `docs/`.

**Key Topics**:
- Detailed methodologies and best practices
- Implementation patterns and examples
- Common pitfalls and anti-patterns
- Cross-references to related skills

**See**: Documentation files in `docs/` directory for complete details


---

## Quick Reference

| Topic | Details |
|-------|---------|
| Detailed Guide 1 | `docs/detailed-guide-1.md` |
| Detailed Guide 2 | `docs/detailed-guide-2.md` |
| Detailed Guide 3 | `docs/detailed-guide-3.md` |
| Detailed Guide 4 | `docs/detailed-guide-4.md` |

---

## Progressive Disclosure

This skill uses progressive disclosure to prevent context bloat:

- **Index** (this file): High-level concepts and quick reference (<500 lines)
- **Detailed docs**: `docs/*.md` files with implementation details (loaded on-demand)

**Available Documentation**:
- `docs/detailed-guide-1.md` - Detailed implementation guide
- `docs/detailed-guide-2.md` - Detailed implementation guide
- `docs/detailed-guide-3.md` - Detailed implementation guide
- `docs/detailed-guide-4.md` - Detailed implementation guide

---

## Cross-References

**Related Skills**:
- See PROJECT.md for complete skill dependencies

**Related Tools**:
- See documentation files for tool-specific guidance


---

## Key Takeaways

1. Research existing patterns before implementing
2. Follow established best practices
3. Refer to detailed documentation for implementation specifics
4. Cross-reference related skills for comprehensive understanding

Files in this skill

  • SKILL.md2.5 KB
  • docs/detailed-guide-1.md1.3 KB
  • docs/detailed-guide-2.md1.1 KB
  • docs/detailed-guide-3.md13.3 KB
  • docs/detailed-guide-4.md1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.