# UnambitiousFx > A collection of lightweight, modular .NET libraries designed to simplify web API development — with Native AOT support and zero unnecessary overhead. > > Version: Functional 4.x This file contains links to documentation sections following the llmstxt.org standard. ## Table of Contents - [ASP.NET Core Integration](https://unambitiousfx.com/functional/aspnetcore/): Convert Result, Result<T>, and Maybe<T> into IResult and IActionResult HTTP responses with centralized failure-to-status mapping. - [Functional](https://unambitiousfx.com/functional/): Lightweight, AOT-ready functional programming for .NET. Result and Maybe types, rich failure modeling, metadata, full async, and ASP.NET Core integ... - [Maybe](https://unambitiousfx.com/functional/maybe/): A type-safe optional value (Some or None) that replaces null and composes cleanly across pipelines. - [Result](https://unambitiousfx.com/functional/result/): Model success and failure as values with Result and Result<T> — railway-oriented programming for .NET, without exceptions for control flow. - [Functional.xunit](https://unambitiousfx.com/functional/xunit/): Fluent, intention-revealing xUnit assertions for Result and Maybe from UnambitiousFx.Functional. - [Getting Started](https://unambitiousfx.com/functional/getting-started): Install UnambitiousFx.Functional, create your first Result, chain operations with Bind and Map, and handle failures. - [Result API Reference](https://unambitiousfx.com/functional/result/api-reference): Terse reference for Result and Result<T> — factories, inspection, matching, transformation, failure handling, side effects, extraction, metad... - [Maybe API Reference](https://unambitiousfx.com/functional/maybe/api-reference): Complete method surface for Maybe<T>, grouped by category, with signatures and descriptions. - [Failures and Metadata](https://unambitiousfx.com/functional/failures-and-metadata): Typed failure objects with stable codes plus an immutable metadata bag for attaching contextual diagnostics. - [Custom Mappers](https://unambitiousfx.com/functional/aspnetcore/custom-mappers): Customize how failures map to HTTP status codes — register typed mappers, write IFailureHttpMapper implementations, and tune adapter policy. - [HTTP Mapping (Minimal API)](https://unambitiousfx.com/functional/aspnetcore/http-mapping): Convert Result and Maybe into IResult for Minimal APIs — builders, status codes, headers, Problem Details, and endpoint patterns. - [MVC Patterns](https://unambitiousfx.com/functional/aspnetcore/mvc-patterns): Convert Result and Maybe into IActionResult for MVC controllers using the AsActionResultBuilder fluent builders. - [Migration from v1](https://unambitiousfx.com/functional/migration-from-v1): Upgrade existing UnambitiousFx.Functional code from v1 to v2 — packages, namespaces, types, and pipeline APIs. - [Migration from v2](https://unambitiousfx.com/functional/migration-from-v2): Upgrade UnambitiousFx.Functional code from v2 to v3 — breaking changes and how to keep the old behaviour. - [Using with AI](https://unambitiousfx.com/functional/using-with-ai): Feed the UnambitiousFx.Functional docs to Claude, Cursor, Copilot, and other AI assistants via llms.txt bundles and the Agent Skills shipped in the... - [Async Assertions](https://unambitiousfx.com/functional/xunit/async-assertions): Assert directly on Task<Result<T>>, ValueTask<Result<T>>, and async Maybe without awaiting first. - [Maybe Assertions](https://unambitiousfx.com/functional/xunit/maybe-assertions): Assert the Some and None branches of Maybe<T> and chain focused checks onto the contained value. - [Result Assertions](https://unambitiousfx.com/functional/xunit/result-assertions): Assert success and failure branches of Result and Result<T>, chain value checks, and narrow to typed failures. - [Test Organization](https://unambitiousfx.com/functional/xunit/test-organization): Structure functional tests with the AAA/Gherkin pattern, descriptive names, theories, and an edge-case checklist.