arch-identify

One-line summary

Diagnose which architecture style or cross-cutting pattern fits a stated problem — or route to a simpler DDD / design-pattern skill when an architecture-level answer is overkill.

When to use this skill

• Greenfield system, picking a macro architecture style (monolith / microservices / event-driven / serverless).
• Existing system facing scalability, integration, or transactional-consistency pressure and asking "what pattern fits".
• Architecture-review framing: "should we have used X instead of Y".

When NOT to use this skill

• Domain modeling question → route to ddd-design.
• Code-level pattern question → route to gof-identify.
• Kotlin-specific pattern question → route to kp-identify.

Core content

Walk the problem through these diagnostic questions, in this order: