skills.rest
moberghr
moberghrOFFICIAL
Explore all skills by this author →
WebsiteGitHub

source-driven-development

Validate unfamiliar APIs against authoritative documentation with cited sources.

6|Updated Mar 30, 2026
Search Tags:#documentation#api#framework#best-practices#verify#version-sensitive
One-click install
npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill source-driven-development-moberghr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/moberghr/mtk-agent-toolkit/tree/main/.claude/skills/source-driven-development
Command: npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill source-driven-development-moberghr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unfamiliar or version-sensitive API behavior can lead to incorrect implementations. This skill helps verify APIs against official sources before integration, reducing risk and guiding safe choices.

Core Features & Use Cases

  • Verify unfamiliar framework, SDK, or library APIs against authoritative documentation.
  • Surface clearly whether behavior is verified, inferred, or uncertain with cited sources.
  • Provide guidance for safe implementation when official guidance varies across versions or environments.

Quick Start

Verify a specific API against its official documentation before implementing.

Frequently Asked Questions about source-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify unfamiliar APIs against official documentation before implementation?▼

Verifying unfamiliar APIs against official documentation involves validating behavior against authoritative sources, distinguishing verified facts from uncertain inferences, and citing sources to drive safe implementation decisions.

Why does version-sensitive API behavior lead to incorrect implementations?▼

Version-sensitive API behavior causes incorrect implementations because official guidance varies across versions and environments, making verified facts from authoritative sources critical for safe decisions.

What is the best way to check SDK updates for safe integration?▼

The best way to check SDK updates for safe integration is to validate new features against authoritative documentation, surface verified versus uncertain behavior, and document sources to guide correct usage.

When do I need to validate external library changes against authoritative sources?▼

You need to validate external library changes against authoritative sources when integrating new framework features, SDK updates, or version-sensitive APIs where official guidance is critical for correctness and security.

Does verifying framework APIs against official docs help prevent implementation errors?▼

Verifying framework APIs against official docs prevents implementation errors by surfacing verified facts, distinguishing uncertain behavior, and providing guidance when official documentation varies across versions or environments.

What are the limitations of relying on inferred API behavior instead of verified sources?▼

Relying on inferred API behavior instead of verified sources risks incorrect implementations, because uncertain behavior lacks cited official guidance and may vary across versions, compromising correctness and security.

Related Skills

Explore More Software Engineering Skills→
dinhhuy258dinhhuy258
16

documentation-research

Fetch version-specific official documentation for public libraries and frameworks.

Community
Intermediate
archonai-labarchonai-lab
1

zig-0.15

Provide verified Zig 0.15.x API references and migration guidance.

Official
Advanced
Rwb3nRwb3n
1

design-review-validation

Validate implemented software against its Detailed Design using COMPARE, VERIFY, L4_ALIGN, and APPROVE.

Community
Advanced
zhenzhizhi12zhenzhizhi12
2

common-skill-l2

Retrieve Cangjie language knowledge via hybrid RAG and official documentation search.

Community
Advanced