source-driven-development

Source-Driven Development

Version: 1.0.0 Last Updated: 2026-05-12

Overview

Source-driven development ensures that framework-specific code is written against current official documentation, not stale training data. AI models often generate code using deprecated APIs, wrong parameter orders, or patterns from older versions. This skill enforces a verification loop:

Detect version → Fetch current docs → Write code with citations → Surface conflicts

This skill leverages the Context7 MCP server (if available) to fetch version-specific documentation at build time.

When to Use

• /temper:build or /temper:fix writing framework-specific code (React, Spring Boot, Express, FastAPI, etc.)
• Adding or updating a dependency
• Writing code that uses a library API you haven't used recently
• Whenever the agent says "I believe the API works like..."

Skip when:

• Writing plain logic (no framework dependency)
• Writing tests for code you just read (you already have the source)
• Modifying config files with known structure

Process

Step 1: Read Manifest

Detect the project's dependencies and versions:

1. JavaScript/TypeScript: Read package.json — extract dependencies and devDependencies
2. Java: Read pom.xml or build.gradle — extract dependency versions
3. Python: Read pyproject.toml or requirements.txt — extract pinned versions
4. Go: Read go.mod — extract module versions
5. Rust: Read Cargo.toml — extract dependency versions

For the specific library you're about to use, note the exact version installed.

Step 2: Fetch Current Documentation

If the Context7 MCP server is available:

1. Resolve the library ID: mcp__plugin_context7_context7__resolve-library-id with the library name
2. Query for the specific API: mcp__plugin_context7_context7__query-docs with:
   • libraryId from step 1
   • query describing the specific API or pattern you need
3. Read the returned documentation snippets