What problem does it solve? Choosing a tech stack or judging whether an existing project's architecture is right often relies on popularity and guesswork rather than evidence, leading to costly rewrites, surprise operating bills, and mismatched tooling. ## Core Features & Use Cases - Evidence-grounded stack and architecture advice: Gathers comparables, primary documentation, and official pricing pages before recommending anything, with every claim carrying a source and observed date. - Three review modes: Pre-build strategy for new ideas, mid-build course correction for repos in progress, and post-build review for finished or deployed projects. - Read-only repo inspection: Maps and samples repositories by size tier without installing dependencies, running code, or modifying anything, and reports secrets files without reading them. - Use Case: You describe a solo side project and ask which stack to use. The skill asks a short batch of intake questions, researches two comparable projects and real pricing, then delivers a recommendation with alternatives, cost scenarios, and the condition that would make it wrong. ## Quick Start Ask the agent to advise on the right stack and architecture for your project idea, or point it at a repository and request an approach review.
