architecture-patterns

Document architecture decisions and patterns using ADR templates.

16|4|Updated Feb 10, 2024
One-click install
npx skills add https://github.com/LetPeopleWork/Lighthouse --skill architecture-patterns-letpeoplework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/LetPeopleWork/Lighthouse/tree/main/.github/.github/agents/skills/architecture-patterns
Command: npx skills add https://github.com/LetPeopleWork/Lighthouse --skill architecture-patterns-letpeoplework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides reference materials, templates, and guidance to standardize software architecture decisions, system documentation, and design governance across projects.

Core Features & Use Cases

  • ADR templates: Structured formats for recording decisions, contexts, and consequences to ensure traceability.
  • Common architectural patterns: Layered Architecture, Repository Pattern, Service Layer, Event-Driven Architecture, Dependency Injection, and more to guide design.
  • Anti-pattern detection & governance: Heuristics and checks to identify risky patterns and enforce best practices.
  • Documentation references: Centralized patterns and decision documentation to support reviews and onboarding.

Quick Start

Review the ADR templates and the Pattern sections to begin documenting a new architectural decision for a system component.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
How do I document architecture decisions to standardize system design?

This Skill provides ADR templates that record contexts, decisions, and consequences, allowing you to document architecture decisions and standardize system design across software projects.

What are common software architecture patterns for guiding design?

Common software architecture patterns include Layered Architecture, Repository Pattern, Service Layer, Event-Driven Architecture, and Dependency Injection, which are provided to guide your system design.

How do I detect anti-patterns during an architecture review?

You can detect anti-patterns during architecture reviews using provided heuristics and checks designed to identify risky patterns, enforce best practices, and support governance.

When do I need to create an Architecture Decision Record for a software component?

You need to create an Architecture Decision Record during architecture reviews, system documentation, or when making design decisions to ensure traceability and support future maintenance for a software component.

What is the best way to centralize architectural patterns and decision documentation?

The best way to centralize architectural patterns and decision documentation is to use reference materials and templates to support reviews, design governance, and onboarding across software projects.