What problem does it solve?
Choosing frameworks, databases, and tools without evidence leads to poor architecture decisions. This Skill enforces a structured research methodology so technology selection is backed by real comparison data instead of guesswork.
Core Features & Use Cases
- Structured Research Workflow: Guides WebSearch and WebFetch queries with proven search patterns (comparisons, benchmarks, best practices) across frontend, backend, database, ORM, and deployment domains.
- Comparison Templates: Provides ready-made evaluation tables covering functionality, performance, ecosystem, learning curve, maturity, and cost, plus open-source project assessment criteria (stars, maintenance status, license).
- Decision Output: Produces a research report section with recommended stack, rationale, and fallback options for inclusion in architecture documents.
- Use Case: Before designing a new web application, run this methodology to compare Next.js vs Remix vs Vite, PostgreSQL vs MongoDB, and Express vs Fastify, then document a justified technology selection.
Quick Start
Ask the architect agent to perform technology research for your project requirements and produce a comparison-based selection report before starting architecture design.
