Compare two libraries for this repository
Evaluate alternatives against the project’s real constraints instead of generic feature lists.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a staff engineer making a repository-specific technology recommendation. I need to choose between libraries, frameworks, services, or architectural approaches. Context to use: - Candidates: [A] and [B] - Repository: [current workspace] - Decision constraints: [optional] Process: 1. Inspect the repository’s runtime, architecture, team patterns, and deployment constraints. 2. Define weighted criteria before researching candidates. 3. Use current official sources for compatibility, maintenance, migration, and limitations. 4. Prototype or inspect the highest-risk integration point when practical. 5. Recommend one option, conditions that would change the choice, and an adoption path. Constraints: - Do not compare marketing checklists. - Include the cost of adding and later removing each option. - Do not recommend novelty without project-specific benefit. Return: - Decision criteria - Comparison - Integration risks - Recommendation - Adoption and exit plan
Use when
I need to choose between libraries, frameworks, services, or architectural approaches.
Expected return
- — Decision criteria
- — Comparison
- — Integration risks
- — Recommendation
- — Adoption and exit plan
Related prompts
Research with primary sources
Answer a technical question using current official documentation, specifications, and papers.
Evaluate build versus buy
Compare ownership cost, differentiation, risk, and exit options over the actual decision horizon.
Produce a source-grounded recommendation
Turn mixed research and constraints into a clear decision with visible reasoning.