Skip to main content
Version: 2.x

Using with AI

These docs are built to be consumed by AI coding assistants, not just humans. Every build publishes machine-readable bundles following the llmstxt.org standard, generated by docusaurus-plugin-llms.

llms.txt bundles​

FileContents
/llms.txtIndex of every documentation section with links.
/llms-full.txtThe entire documentation set concatenated into one file.

Use /llms.txt when you want an assistant to discover the structure and pull only the pages it needs, and /llms-full.txt when you want to drop the whole reference into context at once.

How to use them​

  • Paste a URL. Give your assistant the /llms.txt or /llms-full.txt URL and ask it to read the docs before answering.
  • Let tools fetch automatically. Assistants and editors that understand the llms.txt convention can discover and load these bundles on their own.
  • Attach as context. Download /llms-full.txt and add it to your project or prompt so answers stay grounded in the real API rather than guesses.
tip

Prefer /llms.txt for day-to-day questions to keep context small, and reach for /llms-full.txt only when you need the complete API surface — for example, when migrating a large codebase or generating new pipelines from scratch.

Agent skills​

The NuGet packages ship Agent Skills: SKILL.md files that tell coding agents how to use the library correctly.

PackageSkill
UnambitiousFx.Functionalunambitiousfx-functional
UnambitiousFx.Functional.xunitunambitiousfx-functional-xunit

dotnet restore places them under ~/.nuget/packages/<id>/<version>/skills/, but agents only load skills from their own folders. Set UnambitiousFxSkillsDestination to have the packages copy their skills there on every build:

Directory.Build.props
<Project>
<PropertyGroup>
<UnambitiousFxSkillsDestination>$(MSBuildThisFileDirectory).claude/skills</UnambitiousFxSkillsDestination>
</PropertyGroup>
</Project>
AgentDestination
Claude Code.claude/skills
GitHub Copilot.github/skills
Codex and others, dotnet-package-skills.agents/skills
  • Opt-in. Nothing is written unless the property is set.
  • Always current. The copy runs on build (unchanged files are skipped), so a package update also updates the skill. A skill removed or renamed in a newer version is not deleted from the destination.
  • Transitive. Skills come from every referenced UnambitiousFx package, including ones pulled in by another package.
  • Never breaks the build. A failed copy (read-only or locked destination) is logged as warnings (MSB3021, MSB3026, MSB3027). If you build with -warnaserror / MSBuildTreatWarningsAsErrors, add MSB3021;MSB3026;MSB3027 to MSBuildWarningsNotAsErrors to keep them warnings.

Since the folder is regenerated on build, you can add it to .gitignore; commit it instead if agents should have the skills in a fresh clone before the first build.

A note on accuracy​

The bundles are generated directly from these docs, which are written against the shipped v2.0.0 API (Result, Result<T>, Maybe<T>, the UnambitiousFx.Functional.Failures types, and metadata). Pointing an assistant at them is the most reliable way to get code that compiles against the current library instead of training-data approximations.