Validate .NET/C# code against comprehensive best practices for your solution and project.
Works with
Covers 10+ practice areas including XML documentation, design patterns, dependency injection, async/await, testing standards, and error handling
Enforces specific patterns: primary constructors for DI, Command Handler pattern with generics, interface segregation, and Factory pattern for object creation
Includes resource management with ResourceManager for localization, structured logging via Mic
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondotnet-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches dotnet-best-practices from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dotnet-best-practices. Access via /dotnet-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
17
total installs
17
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
17
installs
17
this week
28.7K
stars
Your task is to ensure .NET/C# code in ${selection} meets the best practices specific to this solution/project. This includes:
public class MyClass(IDependency dependency))CommandHandler<TOptions>)_resourceManager.GetString("MessageKey")Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
β Do
β Don't
π‘ Pro Tips
β Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
β Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kadajett/agent-nestjs-skills
github/awesome-copilot
jwynia/agent-skills
asyrafhussin/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
Registry listing for dotnet-best-practices matched our evaluation β installs cleanly and behaves as described in the markdown.
dotnet-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in dotnet-best-practices β fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend dotnet-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for dotnet-best-practices matched our evaluation β installs cleanly and behaves as described in the markdown.
dotnet-best-practices fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
We added dotnet-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for dotnet-best-practices matched our evaluation β installs cleanly and behaves as described in the markdown.
Keeps context tight: dotnet-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added dotnet-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 43