analyze-architecture

Analyze NestJS project architecture against Clean Architecture and DDD boundaries.

13|1|Updated Jun 28, 2023
One-click install
npx skills add https://github.com/jovicon/nestjs-clean-architecture-event-driven-template --skill analyze-architecture-jovicon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-architecture
Source: https://github.com/jovicon/nestjs-clean-architecture-event-driven-template/tree/main/.claude/skills/analyze-architecture
Command: npx skills add https://github.com/jovicon/nestjs-clean-architecture-event-driven-template --skill analyze-architecture-jovicon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This analysis helps teams identify architectural deviations in NestJS projects, guiding them toward Clean Architecture, DDD, and scalable patterns to reduce drift and improve onboarding.

Core Features & Use Cases

  • Comprehensive architectural validation: checks layer boundaries and dependency rules.
  • DDD-aligned domain modeling: enforces domain purity, aggregates, and events.
  • Event-driven & use-case auditing: validates event publishing, handlers, and repository mappings.

Quick Start

Run a full architectural review across your NestJS repository to detect misalignments with Clean Architecture and DDD.

Frequently Asked Questions about analyze-architecture

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

FAQPage Schema
How do I audit a NestJS project for Clean Architecture compliance?

To audit NestJS architecture, run a full review across your codebase to detect misalignments with Clean Architecture. This validates layer boundaries, dependency rules, and module compliance to reduce architectural drift.

How does domain-driven design validation work for NestJS modules?

Domain-driven design validation analyzes your NestJS modules to enforce domain purity, verify aggregates, and check domain events. It ensures business logic remains isolated from infrastructure concerns.

What is the best way to check layer boundaries in a NestJS codebase?

The best way to check layer boundaries is applying an architectural review that validates domain, application, adapters, and infrastructure layers. This detects misalignments and enforces strict dependency rules.

Can I use this to review event-driven use cases in NestJS?

Yes, you can review event-driven use cases in NestJS. The analysis validates event publishing, handler implementations, and repository mappings to ensure proper application layer integration.