programming-advisorlisted

# Programming Advisor - "Reinventing the Wheel" Detector ## Triggers | Trigger Phrase | Action | |----------------|--------| | "should I build X or use a library" | Search internal prior-art first (Step 2a), then external solutions, provide comparison | | "find existing solutions for X" | Search internal prior-art first (Step 2a), then web search, categorize findings | | "is there a package for X" | Check existing dependencies first (Step 2a), then search npm/pip/cargo/etc | | "build vs buy for X" | Tactical: generate cost comparison table; Strategic (>$50K, multi-year, partner/defer options): delegate to `buy-vs-build-framework` | | "check if X exists before building" | Run full wheel detection workflow | | "do we already have X" / "is there existing code for X in this repo" | Search internal prior-art first (leverage/extend), then external | ## Core Philosophy Before writing a single line of code, determine if the wheel already exists. Vibe coding burns tokens, time, and creates maintenance burden. Existing solutions often provide better quality, security patches, and community support. ## Workflow ### Step 1: Capture Intent Extract from user request: - **What**: Core functionality needed - **Why**: Use case / problem being solved - **Constraints**: Language, platform, budget, licensing requirements ### Step 2: Search for Existing Solutions **Search internal prior-art FIRST (leverage/extend), then external.** The cheapest option is code you already have. #### 2a.