arch

Guide engineers to select architectural references for system design decisions.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/oornnery/skills --skill arch-oornnery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch
Source: https://github.com/oornnery/skills/tree/main/skills/arch
Command: npx skills add https://github.com/oornnery/skills --skill arch-oornnery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture guidance for selecting architectural lenses, patterns, and reference materials to inform system design decisions.

Core Features & Use Cases

  • Reference-driven decision support for DDD, Clean Architecture, SOLID, and system-design patterns
  • Workflow guidance to identify boundaries, layers, adapters, and dependencies
  • Quick mapping to relevant reference files (ddd.md, clean-arch.md, solid.md, patterns.md, sdd.md)

Quick Start

Describe the current architectural problem and map it to the appropriate reference set.

Frequently Asked Questions about arch

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

FAQPage Schema
How do I choose the right architecture pattern for domain boundaries and layering?

To choose the right architecture pattern, describe your current system design problem and map it to relevant references like DDD, Clean Architecture, and SOLID principles. This Skill guides you in comparing options to identify clear boundaries, layers, and dependencies for scalable systems.

How do I apply SOLID principles when designing system boundaries?

Apply SOLID principles when designing system boundaries by using the provided solid.md reference to guide dependency direction and interface segregation. The Skill helps you identify layers and map dependencies to maintain scalable architecture patterns across projects.

What is the best way to start mapping domain boundaries for a new software project?

The best way to start mapping domain boundaries is to describe your architectural problem and select a reference set like ddd.md or patterns.md. This workflow helps you identify problems, compare options, and establish clear architectural boundaries for your project.

When should I use Clean Architecture instead of other system design patterns?

Use Clean Architecture when you need strict dependency rules and clear separation between domain layers and adapters. This Skill leverages clean-arch.md and related patterns to help you decide if this lens effectively solves your specific boundary and layering problems.

Can I use this architectural guidance for existing projects with established dependencies?

Yes, you can use this guidance for existing projects by analyzing current dependencies and boundaries. The Skill applies architectural lenses like DDD and SOLID to compare options and map boundaries, informing decisions for refactoring and scaling established systems.