best-practices-researcher_skill

Overview

This skill helps you research and gather authoritative best practices, documentation, and examples for any technology, framework, or development practice. It synthesizes curated skill knowledge, official docs, and high-quality open source examples to produce concise, actionable guidance. Use it when you need an implementable, source-attributed plan rather than a high-level summary.

How this skill works

First, the skill checks existing curated skill knowledge and internal guidance to reuse proven patterns when available. If gaps remain, it validates that any external APIs or services are not deprecated, then performs targeted online research using official documentation, prominent community guides, and exemplar repositories. Finally, it synthesizes findings into categorized recommendations (Must Have, Recommended, Optional) with examples and source attributions.

When to use it

• You need a practical playbook for implementing a feature to industry standards.
• You want templates and examples (issue templates, config, code snippets) drawn from real projects.
• You must verify an API/SDK is current before recommending it.
• You need a prioritized list of actions with source citations for team adoption.
• You’re creating onboarding docs, style guides, or contribution guidelines.

Best practices

• Start by checking curated internal skill guidance and high-quality prior research to avoid duplicating effort.
• Always run a deprecation check for any external API or service before recommending it.
• Prioritize official documentation and widely-adopted community standards, then corroborate with real-world open source examples.
• Organize recommendations into categories (Must Have, Recommended, Optional) and explain trade-offs when opinions differ.
• Include concrete templates, examples, and links to authoritative sources so teams can implement quickly.

Example use cases

• Researching GitHub issue templates, labeling conventions, and example issues from mature Rails projects.
• Comparing best practices for API authentication flows and verifying any SDK deprecations before proposing a solution.
• Synthesizing frontend component patterns (React/TypeScript) from official docs and top OSS repositories into a team style guide.
• Collecting testing, CI, and release best practices across languages to produce a consolidated checklist for a monorepo migration.