infer-design-patterns-from-code

Extract design patterns from a brownfield codebase by mapping scan-index signals like naming suffix counts, framework idioms, and directory layering into canonical patterns with evidence. This generates a structured design-patterns.yaml artifact cataloging what is actually implemented.

Yes, you can infer architecture patterns by analyzing directory-layer trees and naming suffix counts from scan-index data. This maps structural codebase evidence into scoped component and cross-cutting patterns backed by concrete file paths.

Document existing clean architecture patterns by running an inference scan during codify bootstrap to consume architecture proposals. It generates a design-patterns.yaml file with system, layer, component, and cross-cutting scopes backed by evidence.

Yes, pattern inference cross-checks inferred component patterns against physical-architecture runtime tiers. It records a resolution trace and decision manifest to ensure deterministic mapping and provide full auditability for architecture documentation.

The limitation is that pattern inference relies entirely on scan-index.json signals and existing architecture proposals, meaning it cannot deduce patterns from unscanned directories or missing logical and physical architecture grounding proposals.