Tech Selection
Gated checklist to choose or review a library, framework, storage, data format, model...
Install
npx skills add daymade/claude-code-skills --skill tech-selection -g -a claude-code -y- Repository
- daymade/claude-code-skills1.5k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Gated checklist to choose or review a library, framework, storage, data format, model, build-vs-buy or architecture. Run favorites-search before external research when installed. Compare candidates and trade-offs; select within authorization or return user-owned choices. Use for 用哪个 / 选什么框架 / 要不要自建 / A 还是 B / 这个方案行不行 and before committing to one. Research reports → deep-research.
Tech Selection, Gated Checklist
A checklist for choosing between technologies, not a scoring rubric. The core insight: these criteria are filters, not sorters, they kill candidates that violate a principle. Keep the candidates and trade-offs visible, then apply the current authorization: choose and verify an authorized reversible implementation; return unresolved business, product or preference trade-offs to the user. Candidate count, duration and confidence language do not determine who decides.
These outcomes end the protocol early:
- User-owned choice, missing authorization or a genuine unresolved business, product or preference trade-off. Return the evidence and recommendation.
- Unverified completion claim, withhold the claim, execute authorized verification, and report any remaining acceptance gap.
Not This
- Not for research reports (use deep-research), debugging or bug fixes in already-settled code, or price comparisons between vendors, none of these is choosing a technology.
- Not an interview framework, the user delegates implementation, not direction. Don't ask "which do you prefer" when you can probe and decide.
- Not a scoring rubric, no weighted scores, no "winner" ranking. Filters, then business anchor.
- Not self-certifying, the "why this isn't garbage" defense is written by this skill but must be independently checkable, not self-approved.
- Not a cost gate, budget sets execution tier (which model runs), never whether to do it. Don't use cost as a rejection reason for the user's own projects.
- Not a scope expander, no unrequested features, frameworks, or complexity.
- Not package-size-driven, line count and bundle size are proxies, not quality.
