api-documentation-discoverylisted

# API Documentation Discovery ## Overview When your training data conflicts with current API versions, STOP guessing and START discovering. This skill guides you to find current, accurate documentation using language-specific tools. **Core principle:** Training data ages. Installed versions are truth. Use discovery tools to find what's actually there. ## When to Use ### Reactive Triggers (MUST use after these): - ✅ 2+ failed attempts with same library/API - ✅ Error patterns: "method not found", "wrong number of arguments", "unknown flag", "undefined method" - ✅ Version mismatch symptoms in stack traces ### Proactive Red Flags (STOP and check docs when you notice): - ⚠️ You're confident about API usage but haven't verified current version - ⚠️ User is confident but their syntax keeps failing - ⚠️ You're making "one more tweak" to syntax - ⚠️ You're using phrases like "should work", "likely correct", "probably just" - ⚠️ You're pattern-matching from training data without verification - ⚠️ You're about to claim something is "documented" without checking **When NOT to use:** - First attempt with clear error message pointing to fix - Errors unrelated to API usage (logic bugs, type errors in your code) ## The Discovery Workflow ### Step 1: STOP Guessing Recognize the trigger. Don't make another attempt based on patterns or user confidence. ### Step 2: Identify Context - What library/framework is failing? (check imports, stack traces, go.mod/Gemfile) - What version is inst