Skip to content

charlieviettq/awesome-agent-skill / .claude/skills/source-driven-development

source-driven-development

Verified

Ground framework and library decisions in official documentation—detect versions, fetch relevant docs, cite sources, flag unverified patterns. Use when API correctness matters for React, Next.js, Python libs, cloud SDKs, or unfamiliar stacks.

Source-driven development

When to use

  • Framework-specific code (React, Next, FastAPI, sklearn, etc.)
  • User wants documented, version-correct patterns
  • Unsure if training-data API is current

When to relax

  • Pure logic with no external API
  • User explicitly wants speed over doc verification

Process

DETECT versions -> FETCH official docs -> IMPLEMENT -> CITE or FLAG unverified
  1. Read dependency files (package.json, pyproject.toml, etc.)
  2. Fetch the specific doc page for the feature (not homepages)
  3. Match signatures and patterns from docs
  4. Cite URL for non-obvious choices; flag gaps as UNVERIFIED

Source priority

  1. Official documentation
  2. Official changelog / migration guide
  3. Web standards (MDN, etc.)
  4. Not primary: blogs, Stack Overflow, training memory alone

Conflicts

If docs conflict with existing codebase, surface options—do not silently pick one.

Output

Brief citation in comments or PR for framework decisions; UNVERIFIED callouts when docs missing.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall