Fetches microsoft-extensions-configuration from aaronontheweb/dotnet-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/microsoft-extensions-configuration
Restart Cursor to activate microsoft-extensions-configuration. Access via /microsoft-extensions-configuration in your agent's command palette.
⚠
Security Notice
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.
Binding configuration from appsettings.json to strongly-typed classes
Validating configuration at application startup (fail fast)
Implementing complex validation logic for settings
Designing configuration classes that are testable and maintainable
Understanding IOptions, IOptionsSnapshot, and IOptionsMonitor
Reference Files
advanced-patterns.md: Validators with dependencies, named options, complete production example (AkkaSettings), and testing validators
Why Configuration Validation Matters
The Problem: Applications often fail at runtime due to misconfiguration - missing connection strings, invalid URLs, out-of-range values. These failures happen deep in business logic, far from where configuration is loaded.
The Solution: Validate configuration at startup. If invalid, fail immediately with a clear error message.
// BAD: Fails at runtime when someone tries to use the servicepublicclassEmailService{publicEmailService(IOptions<SmtpSettings> options){var settings = options.Value;// Throws NullReferenceException 10 minutes into production _client =newSmtpClient(settings.Host, settings.Port);}}// GOOD: Fails at startup with clear error// "SmtpSettings validation failed: Host is required"
publicclassEmailService{privatereadonlySmtpSettings _settings;// IOptions<T> - singleton, read once at startuppublicEmailService(IOptions<SmtpSettings> options){ _settings = options.Value;}}
Pattern 2: Data Annotations Validation
For simple validation rules, use Data Annotations:
usingSystem.ComponentModel.DataAnnotations;publicclassSmtpSettings{publicconststring SectionName ="Smtp";[Required(ErrorMessage ="SMTP host is required")]publicstring Host {get;set;}=string.Empty;[Range(1,65535, ErrorMessage ="Port must be between 1 and 65535")]publicint Port {get;set;}=587;[EmailAddress(ErrorMessage ="Username must be a valid email address")]publicstring? Username {get;set;}publicstring? Password {get;set;}publicbool UseSsl {get;set;}=true;}
Enable Data Annotations Validation
builder.Services.AddOptions<SmtpSettings>().BindConfiguration(SmtpSettings.SectionName).ValidateDataAnnotations()// Enable attribute-based validation.ValidateOnStart();// Validate immediately at startup
Key Point:.ValidateOnStart() is critical. Without it, validation only runs when the options are first accessed.
Pattern 3: IValidateOptions for Complex Validation
Data Annotations work for simple rules, but complex validation requires IValidateOptions<T>:
Scenario
Data Annotations
IValidateOptions
Required field
Yes
Yes
Range check
Yes
Yes
Cross-property validation
No
Yes
Conditional validation
No
Yes
External service checks
No
Yes
Dependency injection in validator
No
Yes
Implementing IValidateOptions
usingMicrosoft.Extensions.Options;publicclassSmtpSettingsValidator:IValidateOptions<SmtpSettings>{publicValidateOptionsResultValidate(string? name,SmtpSettings options){var failures =newList<string>();if(string.IsNullOrWhiteSpace(options.Host)) failures.Add("Host is required");if(options.Port is<1or>65535) failures.Add($"Port {options.Port} is invalid. Must be between 1 and 65535");// Cross-property validationif(!string.IsNullOrEmpty(options.Username)&&string.IsNullOrEmpty(options.Password)) failures.Add("Password is required when Username is specified");// Conditional validationif(options.UseSsl && options.Port ==25) failures.Add
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
1Basic: user stories, feature specs, status updates
