tech-selectionlisted

## When to use - Choosing or comparing a technology stack, library, framework, open-source project, or GitHub repository for a concrete requirement. - User says "技术选型", "方案对比", "选哪个", "tech stack", "library comparison", or "技术对比". - Need a defensible selection backed by GitHub evidence and official docs, not a popularity contest. **Not for:** market sizing or competitor business analysis (use `market-research`); cited deep research report (use `research`). ## Steps 1. **Clarify the requirement.** - Restate goal, constraints, platform, language/runtime, scale, budget, deadline, team skill, must-haves, and non-goals. - Ask one concise question only if the requirement is too broad to search usefully; otherwise state assumptions and proceed. 2. **Split the selection problem.** - Identify decision dimensions: capability fit, integration cost, maturity, maintenance, license, ecosystem, performance/scalability, security, deployment complexity, lock-in. - Define what "效果如何" means: expected result, user/business impact, performance, maintainability, delivery speed, validation plan. 3. **Search GitHub first.** - Use multiple angles: requirement keywords, domain terms, language/framework terms, "awesome" lists, example apps, benchmark repos, known alternatives. - Collect at least five credible candidates before narrowing; if fewer exist, state why and compare the credible set. - For each candidate, collect: repo URL, description, primary language, license, sta