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. Existing usage in the codebase is not verification either: the codebase may be on an older version, and a passing test proves the code runs, not that the API is current. 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 a documentation MCP server such as Context7 is available: resolve the library to its ID, query it for the specific API or pattern you need at the installed version, and read the returned snippets. Use the tool names the server exposes in this session rather than assuming them.