Source driven development
Skill charlieviettq/awesome-agent-skill/.cursor/skills/core-workflow/source-driven-development
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. Triggers: "official docs", "verify API", "source-driven", "is this API still valid".From its SKILL.md
npx -y skills add charlieviettq/awesome-agent-skill --skill source-driven-developmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 239 tokens by cl100k_base, as published. Nobody here has run it
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
- Read dependency files (
package.json,pyproject.toml, etc.) - Fetch the specific doc page for the feature (not homepages)
- Match signatures and patterns from docs
- Cite URL for non-obvious choices; flag gaps as UNVERIFIED
Source priority
- Official documentation
- Official changelog / migration guide
- Web standards (MDN, etc.)
- 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.