excalidash-hexagonal-architecture-mapper

Describe the application core, its driving adapters (REST, CLI, consumers), driven adapters (repositories, payment clients, mailers), and the ports between them. The skill calls apply_architecture_skill with pattern hexagonal, then lints, scores, and validates the result.

Use the create_from_repo_analysis path with an analysis object listing modules, entrypoints, database, services, and integrations. Domain modules collapse into the core, entrypoints become left-side driving adapters, and infrastructure becomes right-side driven adapters.

Use the hexagonal diagram when you need the explicit left/right driving versus driven adapter split with ports on the boundary. Use the Clean Architecture skill for concentric rings of entities, use cases, adapters, and frameworks without that split.

The validate_architecture tool checks that every cross-boundary edge points toward the hexagon, the core depends only on driven ports it owns, no framework type sits inside the core, and no adapter is orphaned or port unbound.

The repair loop is mandatory: repair_drawing runs for each blocker or penalty, followed by re-linting and re-scoring until the score reaches at least 95 with zero hard blockers. Any pass that lowers the score is rolled back to the last saved version.

No. Secrets such as Postgres connection strings, SaaS API keys, and webhook secrets must be redacted into typed placeholders before any tool call, and the exported drawing is re-scanned to confirm no real values leaked.