architecture-intelligence

Organize and validate architecture decisions for multi-layer software systems.

Updated Apr 10, 2026

Search Tags:#architecture #validation #reasoning #clean-architecture #software-design #system-design #domain-driven

Ready to run

npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill architecture-intelligence-majedsiefalnasr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-intelligence
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/architecture-intelligence
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill architecture-intelligence-majedsiefalnasr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured approach to reason about, validate, and govern software architecture decisions across frontend, API, and data layers.

Core Features & Use Cases

Layered architecture guidance: outlines a clean architecture pattern with clear separation between frontend, API, business logic, and data access.
Domain-driven design insights: defines domain separation for construction management, e-commerce, and shared services, including authentication and RBAC.
Validation & governance: offers a set of validation commands and a documented module registration process to ensure architecture consistency.

Quick Start

Follow the architecture intelligence guide to review your system design and align teams on the architecture map.

Frequently Asked Questions about architecture-intelligence

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

FAQPage Schema

How do I validate clean architecture decisions across frontend and API layers?▼

You validate clean architecture decisions by applying a structured reasoning layer that enforces domain separation and module mapping across frontend, API, and data layers. This ensures consistent architectural governance and validates functional requirements.

What is the best way to enforce domain-driven design separation in a multi-layer application?▼

Enforcing domain-driven design separation requires outlining clear boundaries between business logic and data access layers. This approach provides domain separation insights for shared services, including authentication and RBAC governance, to maintain system integrity.

How do I set up architecture validation commands for backend and frontend components?▼

You set up architecture validation by registering modules through a documented process and executing lint, typecheck, and test commands. These commands validate both backend and frontend components to ensure architectural consistency.

Can I use a single architectural reasoning layer for construction management and e-commerce domains?▼

Yes, a single architectural reasoning layer supports domain separation for both construction management and e-commerce domains. It defines shared services and RBAC governance to validate functional requirements across distinct business logic boundaries.

When do I need an architectural reasoning layer for system design?▼

You need an architectural reasoning layer when organizing and validating architecture decisions for complex, multi-layer software systems. It is essential when implementing clean architecture, domain-driven design, and RBAC governance across frontend, API, and data layers.