Identifies architectural and anti-patterns from container, component, and data-model evidence.
npx skills add https://github.com/vishalkhondre/unearth --skill 08-patterns
Please help me install this Agent Skill. Skill: 08-patterns Source: https://github.com/vishalkhondre/unearth/tree/main/skills/08-patterns Command: npx skills add https://github.com/vishalkhondre/unearth --skill 08-patterns
Detects architecture patterns and anti-patterns from structural and knowledge outputs. Covers structural patterns (N-tier, clean architecture, CQRS, microservices, BFF, event-driven), domain patterns (anemic model, rich model, DDD), and anti-patterns (god classes, circular dependencies, shared databases, missing abstractions). Each detection requires evidence from at least two upstream outputs. Use after 07-data-model when you need to characterize the architectural style and identify structural risks.
Run this skill after assembling upstream outputs from containers, components, and the data model to synthesize patterns.
High-intent search queries and answers about installing and using this skill.
To detect architecture anti-patterns in a legacy monolith, synthesize evidence from container structure, component analysis, and domain data to reveal problematic patterns like god classes and circular dependencies for modernization planning.
Architecture patterns identifiable from container and component analysis include N-tier, clean architecture, CQRS, microservices, BFF, and event-driven structures, alongside domain patterns like anemic model, rich model, and DDD.
Evaluate architectural maturity in multi-layer architectures by synthesizing container, component, and data-model signals to identify the presence or absence of key patterns and flag missing abstractions.
Yes, you need upstream data to identify domain model patterns. Pattern detection requires evidence from at least two upstream outputs, such as data models and components, to validate each detected pattern.
Run pattern detection during architecture evaluation after assembling upstream outputs from containers, components, and data models to synthesize structural risks and characterize the overall architectural style.
edteCreate and validate Draw.io diagrams as .drawio or .xml files.
gil00pitaAssess codebase architecture for patterns, anti-patterns, and structural quality.
casmidiAnalyze price, volume, order flow, and news to generate trading signals.
Destynova2Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.
