addy-source-driven-development

Cite official documentation for every implementation decision in software projects.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill addy-source-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-source-driven-development
Source: https://github.com/japurcell/skills/tree/main/skills/addy-source-driven-development
Command: npx skills add https://github.com/japurcell/skills --skill addy-source-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grounds every implementation decision in official documentation. Avoids outdated patterns by requiring explicit citations.

Core Features & Use Cases

  • Enforces source-backed decision making across software projects.
  • Generates verifiable citations for APIs, patterns, and best practices.
  • Helps teams maintain reproducible, documentation-driven workflows.
  • Use Case: When starting a new feature, verify against official docs and record sources to support future maintenance.

Quick Start

Invoke this skill at the outset of a coding task to ensure every implementation cites official sources.

Frequently Asked Questions about addy-source-driven-development

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

FAQPage Schema
What is source-driven development for software engineering?▼

Source-driven development grounds implementation decisions in official documentation, requiring explicit citations to verify framework-specific patterns and APIs against authoritative sources.

How do I verify framework best practices against official documentation?▼

Invoke a source-driven development workflow at the outset of a coding task to collect and cite official sources, verifying framework best practices and recording them for future maintenance.

Why does citing official docs help maintain reproducible software workflows?▼

Citing official docs helps maintain reproducible software workflows by ensuring every implementation decision is backed by authoritative sources, preventing the use of outdated patterns.

Can I use source-driven development to verify APIs for any software project?▼

Yes, source-driven development applies across software projects to verify framework-specific patterns, APIs, and best practices against official documentation for reproducible results.

What's the best way to avoid outdated coding patterns in framework implementations?▼

The best way to avoid outdated patterns is enforcing source-backed decision making, generating verifiable citations for APIs and patterns to support reproducible, documentation-driven workflows.