hexagonal-architecture-analysis

Map hexagonal architecture components and analyze layer tensions in Spatial-Iteration-Engine.

Updated Feb 4, 2026

Search Tags:#architecture #migration #hexagonal #analyze #ports-and-adapters #dependency-map

Ready to run

npx skills add https://github.com/FacundoDuranDev/Spatial-Iteration-Engine --skill hexagonal-architecture-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hexagonal-architecture-analysis
Source: https://github.com/FacundoDuranDev/Spatial-Iteration-Engine/tree/main/.claude/skills/hexagonal-architecture-analysis
Command: npx skills add https://github.com/FacundoDuranDev/Spatial-Iteration-Engine --skill hexagonal-architecture-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits and inventories the current hexagonal architecture to reveal limitations, misalignments, and architectural debt that impede safe migrations.

Core Features & Use Cases

Component inventory mapping: identify domain, ports, adapters, application, and infrastructure elements.
Dependency and layer tension analysis: reveal misplacements such as TemporalManager ownership, FilterContext wrapping, and hardcoded pipeline order.
Migration surface assessment: produce migration-ready inventories and debt reports that guide refactors.

Quick Start

Run a hexagonal-architecture audit of Spatial-Iteration-Engine to generate migration-ready inventories and debt reports.

Frequently Asked Questions about hexagonal-architecture-analysis

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

FAQPage Schema

How do I audit hexagonal architecture for technical debt before a migration?▼

A hexagonal architecture audit inventories domain, ports, adapters, application, and infrastructure layers to reveal layer tensions and architectural debt. It produces migration-ready reports identifying component misplacements that impede safe migrations.

What causes layer tension in ports and adapters architecture?▼

Layer tension in a ports and adapters architecture is caused by misplacements like TemporalManager ownership, FilterContext wrapping, and hardcoded pipeline order. These architectural deviations introduce strain and violate true hexagonal boundaries.

How do I generate a component inventory for a hexagonal architecture migration?▼

Generate a component inventory by mapping spatial architecture elements like domain, ports, and adapters. This produces an evidence-backed artifact with explicit file references detailing data flows and constraints for migration readiness.

Can I get a data flow map for hexagonal architecture components?▼

Yes, a data flow map is generated by analyzing hexagonal architecture components. The map traces data flows, constraints, and layer tensions across domain, application, and infrastructure layers with explicit file references like application/engine.py.

What artifacts do I need to assess migration surface in a hexagonal architecture?▼

To assess migration surface in a hexagonal architecture, you need evidence-backed artifacts: a component inventory, data flow map, tension report, and migration surface report. These identify architectural debt and explicitly guide refactors.

When should I not use a hexagonal architecture audit?▼

You should avoid a hexagonal architecture audit when your project lacks explicit ports and adapters layers or when complex layer tensions like hardcoded pipeline order are absent, meaning migration-ready debt analysis is unnecessary.