result-pattern
Skill109 starsChanged 5 months agoNo licenceView on GitHub
Implement or use our Result<T> failure model in the .NET API — return Result from handlers, build Error values, compose with Map/Then/Match, catch domain exceptions into Result, and map Result→RFC 9457 ProblemDetails. Use when adding an operation that can fail or wiring an endpoint's error contract.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-domain-entitySkill
- add-endpointSkill
- cqrs-kommandSkill
- dotnet-ai-stackSkill
- dotnet-performance-reviewSkill
- efcore-patternsSkill
- efcore-query-performanceSkill
- explain-codebaseSkill
- mcp-csharpSkill
- microbenchmarkingSkill
- onboardSkill
- otel-instrumentationSkill
- pushSkill
- query-postgresSkill
- query-telemetrySkill
- run-impl-loopSkill
- security-backendSkill
- validation-scopesSkill
- write-testsSkill
The file
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.