Stack Compatibility Oracle

A dependency resolver for architectural decisions, not packages. Before building, check whether the chosen technologies across layers actually work well together. npm install succeeding does not mean the architecture is sound.

When to Use

• Starting a new project and evaluating technology choices
• Adding a major component that introduces a new technology layer
• Migrating from one technology to another (e.g., switching databases, frameworks)
• Reviewing a proposed stack from a brainstorming or design phase
• Sanity-checking a client's or team's pre-selected stack before committing to it

When NOT to Use

• Adding a small library within an already-decided stack
• Pure package version compatibility (use dependency managers for that)
• Evaluating a single technology in isolation (this skill checks combinations)

Process