web-research
Research technical problems across GitHub issues, Stack Overflow, Reddit, and documentation. Gathers solutions from multiple community sources with structured findings. Triggers on search for solutions, find examples, research problem, community solutions, debug research.
What this skill does
# Web Research **Audience:** Developers debugging issues or researching solutions who need comprehensive findings from multiple sources. **Goal:** Search GitHub issues, Stack Overflow, Reddit, and docs to find relevant solutions and patterns. ## Research Process ### 1. Query Generation - Generate 5-10 search query variations for the given topic - Include technical terms, error messages, library names - Consider how different people might describe the same issue - Search for both the problem AND potential solutions ### 2. Source Exploration | Source | What to Look For | |--------|-----------------| | GitHub Issues | Open and closed issues with matching symptoms | | Stack Overflow | Accepted answers and high-vote alternatives | | Reddit | r/programming, r/webdev, topic-specific subreddits | | Official docs | Changelogs, migration guides, known issues | | Blog posts | Tutorials, deep dives, experience reports | | Hacker News | Technical discussions and alternative perspectives | ### 3. Information Gathering - Read beyond the first few results - Look for patterns in solutions across different sources - Pay attention to dates to ensure relevance - Note different approaches to the same problem - Identify authoritative sources and experienced contributors ### 4. Quality Verification - Cross-reference information across multiple sources - Clearly indicate when information is speculative or unverified - Date-stamp findings to indicate currency - Distinguish between official solutions and community workarounds ## Search Techniques - Use exact error messages in quotes for debugging issues - Use `site:` operator for targeted source searching - Use `inurl:`, `intitle:`, `filetype:` for precise results - Check archived/cached content for removed or updated information - Search in multiple languages if initial results are limited ## Output Format ```markdown ### Executive Summary [Key findings in 2-3 sentences] ### Detailed Findings #### Option 1: [Solution/Approach Name] - Description - Implementation details - Pros and cons - Source credibility #### Option 2: [Alternative Solution] [Continue as needed] ### Sources and References [Direct links with brief descriptions] ### Recommendations [Best approach based on research with trade-offs noted] ```
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.