add-options-class
Skill234 starsChanged 3 months agoMITView on GitHub
Add a typed options/configuration class with validation
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- init-verifySkill
- manage-file-storageSkill
- new-endpointSkill
- new-entitySkill
- new-featureSkill
- new-pageSkill
- polish-uiSkill
- review-dependabotSkill
- review-designSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create in the appropriate layer:
- Very specific: line 29
Add section to appsettings.json (and appsettings.Development.json if dev differs - dev/test appsettings excluded from production publish …
- Very specific: line 37
Update docs/before-you-ship.md if this is a must-configure production setting
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Adds a typed options/configuration class.
Steps
- Create in the appropriate layer:
- Infrastructure:
src/backend/MyProject.Infrastructure/{Area}/Options/{Name}Options.cs - WebApi:
src/backend/MyProject.WebApi/Options/{Name}Options.cs
- Infrastructure:
- Structure:
/// <summary> /// Configuration for {area}. Maps to "{SectionName}" in appsettings.json. /// </summary> public sealed class {Name}Options { public const string SectionName = "{Section}"; /// <summary> /// Gets or sets the ... /// </summary> [Required] public string Value { get; init; } = string.Empty; } - Add section to
appsettings.json(andappsettings.Development.jsonif dev differs - dev/test appsettings excluded from production publish viaStripDevConfig) - Register in DI extension:
services.AddOptions<{Name}Options>() .BindConfiguration({Name}Options.SectionName) .ValidateDataAnnotations() .ValidateOnStart(); - Update
docs/before-you-ship.mdif this is a must-configure production setting
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

