add-options-class

Generate typed options classes with appsettings.json sections and Dependency Injection registrations for .NET.

230|29|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/fpindej/netrock --skill add-options-class
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-options-class
Source: https://github.com/fpindej/netrock/tree/main/.claude/skills/add-options-class
Command: npx skills add https://github.com/fpindej/netrock --skill add-options-class

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of typed options/configuration classes in a .NET project, ensuring type safety and proper configuration binding.

Core Features & Use Cases

  • Boilerplate Reduction: Generates the C# class, appsettings.json section, and Dependency Injection registration code.
  • Type Safety: Ensures configuration values are strongly typed, reducing runtime errors.
  • Use Case: When adding a new feature that requires external configuration (e.g., an API key for a third-party service), this Skill quickly sets up the necessary configuration structure.

Quick Start

Use the add-options-class skill to add a new options class named 'Email' in the Infrastructure layer with the section name 'EmailSettings'.

Frequently Asked Questions about add-options-class

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

FAQPage Schema
How do I create a typed options class for .NET configuration?

To create a typed options class for .NET, generate the C# configuration class, add a matching appsettings.json section, and register it via Dependency Injection to ensure type safety and structured binding.

What is the options pattern in C# dependency injection?

The options pattern in C# dependency injection uses typed classes to bind configuration settings from appsettings.json, ensuring strongly typed access and reducing runtime errors caused by unstructured configuration management.

How do I validate appsettings.json configuration on startup in .NET?

Validate appsettings.json configuration on startup in .NET by applying ValidateDataAnnotations and ValidateOnStart during Dependency Injection registration, ensuring invalid configuration values trigger immediate application startup failures.

Does generating .NET configuration classes require manual boilerplate for DI registration?

Generating .NET configuration classes does not require manual boilerplate for DI registration, as the process automates creating the C# class, appsettings.json section, and Dependency Injection setup to reduce repetitive code.

When should I use typed configuration classes instead of raw configuration values in C#?

Use typed configuration classes instead of raw configuration values in C# when adding features requiring external settings like API keys, ensuring type safety, structured validation, and eliminating manual configuration access boilerplate.