programming-advisor
Evaluate existing solutions (libraries, SaaS, open source) AND internal prior-art before custom development to avoid reinventing the wheel. Use when considering building new features, asking "should I build or use existing", "do we already have this", "is there existing code for X in this repo", "is there a library for this", or need build vs buy cost analysis with token estimates. Checks internal reuse (leverage/extend) before external. Do NOT use for strategic multi-option TCO (use buy-vs-build-framework).
- License
- MIT
Pinned to revision acff1d0a1f21, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/programming-advisor/SKILL.md
- skills/programming-advisor/references/bitter-lesson-llms.md
- skills/programming-advisor/references/common-solutions.md
- skills/programming-advisor/references/integration-patterns.md
- skills/programming-advisor/references/pricing-data.md
- skills/programming-advisor/references/search-before-building.md
- skills/programming-advisor/references/token-estimates.md
Every link opens the file at its source, pinned to the revision this page describes.