source-driven-development

Grounds .NET and C# implementation decisions in official documentation with cited sources.

7|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/peterblazejewicz/claude-plugins --skill source-driven-development-peterblazejewicz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/peterblazejewicz/claude-plugins/tree/main/plugins/dotnet-skills/skills/source-driven-development
Command: npx skills add https://github.com/peterblazejewicz/claude-plugins --skill source-driven-development-peterblazejewicz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Framework APIs change between versions, and code written from memory often uses deprecated or incorrect patterns. This Skill ensures every .NET/C# implementation decision is verified against official documentation (Microsoft Learn, EF Core docs, Avalonia docs) and cited with full URLs, so users can trust and audit the code they receive. ## Core Features & Use Cases - Stack Detection: Reads global.json, Directory.Packages.props, .csproj, and Directory.Build.props to identify exact SDK, target framework, and package versions before writing code. - Documentation Fetching: Retrieves the specific official docs page for the feature being implemented, following a strict source hierarchy that excludes Stack Overflow and blog posts. - Source Citation: Adds full-URL citations in code comments and conversation, flags unverifiable patterns explicitly, and surfaces conflicts between docs and existing code. - Use Case: When adding EF Core queries to a net8.0 API, the Skill detects the EF Core version, fetches the current performance guidance, implements AsSplitQuery() per the docs, and cites the Microsoft Learn page so the team can verify the pattern. ## Quick Start Ask the assistant to implement an EF Core or ASP.NET Core feature using source-driven development so every pattern is verified against official documentation and cited.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I make sure .NET code follows current official documentation?

Use source-driven development: detect the project's SDK and package versions from global.json and .csproj files, fetch the relevant Microsoft Learn page for the feature, implement the documented pattern, and cite the full URL in code comments.

What sources are authoritative for .NET API patterns?

Microsoft Learn, official framework docs like docs.avaloniaui.net, API reference pages, and official GitHub release notes are authoritative. Stack Overflow answers, blog posts, and AI training data are explicitly not acceptable as primary citations.

Does this approach work with older .NET versions like net6.0?

Yes. The Skill detects the exact target framework first and fetches version-specific documentation, since patterns valid in net6.0 may be deprecated in net8.0. If versions are ambiguous, it asks the user rather than guessing.

What happens when documentation conflicts with existing project code?

The conflict is surfaced explicitly with both options presented, such as modern async EF Core patterns versus existing synchronous code. The user chooses the approach rather than the Skill silently picking one.

When should I not use source-driven development?

Skip it when correctness does not depend on framework versions, such as renaming variables, fixing typos, or pure logic using standard collections. It is also unnecessary when the user explicitly prioritizes speed over verification.