source-driven-development

Detect project dependencies and enforce code patterns from official documentation.

6|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/farzanmrz/oparax-chirp --skill source-driven-development-farzanmrz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/farzanmrz/oparax-chirp/tree/main/.claude/skills/source-driven-development
Command: npx skills add https://github.com/farzanmrz/oparax-chirp --skill source-driven-development-farzanmrz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ground every implementation decision in official documentation. Don't build from memory or outdated patterns—verify, cite, and show sources to ensure trust and maintainability.

Core Features & Use Cases

  • Detects project stack from dependency files and specified versions.
  • Fetches official documentation pages for relevant patterns and enforces usage from sources.
  • Surfaces conflicts or ambiguities for user validation and safe migration.

Quick Start

Start by identifying the project's stack with its dependency files, fetch the relevant docs, and implement patterns strictly following the cited sources.

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 framework-specific code patterns against official documentation?

To verify framework-specific code patterns, you can detect project dependencies from configuration files, fetch the relevant official documentation, and enforce code patterns strictly from those cited sources.

What is the best way to ensure code quality during framework migrations?

Ensuring code quality during migrations involves fetching official documentation for the target framework, verifying each pattern against canonical sources, and surfacing any conflicts or ambiguities for user validation before applying changes.

How does dependency analysis from project files improve code reviews?

Dependency analysis improves code reviews by automatically detecting the specified project stack and versions, fetching the corresponding official documentation, and enforcing verified framework patterns to ensure every implementation decision is grounded.

Does this approach work for boilerplate generation across different programming languages?

Yes, this approach applies to boilerplates, migrations, and code reviews across languages by detecting dependencies from project files and enforcing framework-specific patterns strictly verified against official documentation sources.

What happens when official docs conflict with existing project patterns?

When official docs conflict with existing project patterns, the process surfaces those conflicts or ambiguities explicitly for user validation, ensuring safe migration and maintainability rather than silently overwriting implementation decisions.