Repository navigation
AI Assistants AI Skills
Markdown files that teach your AI coding assistant how to write FxMap code correctly: the real API names, the registration order, and the mistakes to avoid.
General-purpose assistants know FxMap only from whatever was in their training data, so they tend to guess method names (such as MapAsync instead of MapDataAsync) or write expressions in C#. Give them these files and they work from the actual API.
All five files in the folder layout Claude Code expects. Unzip it into your skills directory.
Everything merged into one file, for tools that accept a single instructions file.
SKILL.md
Entry point with the rules that prevent most mistakes and a map of the other files.
fxmap-core.md
Distributed keys, entity configs, profiles, registration, the mapper and configuration options.
fxmap-transports.md
gRPC (including Kestrel / HTTP/2), NATS, RabbitMQ, Kafka, Azure Service Bus and Amazon SQS.
fxmap-providers.md
Entity Framework Core, MongoDB, HotChocolate and the Roslyn analyzers.
fxmap-expressions.md
The complete expression language: navigation, filters, indexers, functions, aggregations, projections.
Put the fxmap folder in .claude/skills/ of your repository (shared with the team) or in ~/.claude/skills/ (just for you). Claude loads it when a task involves FxMap.
mkdir -p .claude/skills
curl -L https://fxmapper.net/ai-skills/fxmap-ai-skills.zip -o fxmap-ai-skills.zip
unzip fxmap-ai-skills.zip -d .claude/skills
rm fxmap-ai-skills.zipSave the single file as .github/copilot-instructions.md.
mkdir -p .github
curl -L https://fxmapper.net/ai-skills/fxmap-all.md -o .github/copilot-instructions.mdMost tools read a project instructions file. Download the single file and save it where your tool looks for rules (for example AGENTS.md in the repository root, or a rule file in .cursor/rules/). If your tool has a context or "docs" feature, you can attach the individual files instead.
curl -L https://fxmapper.net/ai-skills/fxmap-all.md -o AGENTS.md- The files describe the current FxMap API. Download them again when you upgrade FxMap.
- They are guidance, not a guarantee: still review generated code and run your tests.
- Add the
FxMap.Analyzerspackage so the compiler also catches misconfigured profiles and expressions.
Source: https://fxmapper.net/docs/ai-skills/ — the website is always the most up to date version.
Introduction
Getting Started
Configuration
- Service Registration
- Entities & Profiles
- Handlers
- Pipelines
- Strongly Typed IDs
- Error Handling
- Retry Policy
- Supervisor
- Telemetry
- Kestrel (HTTP/2)
- Analyzers
Expressions
- Overview
- Property Access
- Filters, Sorting & Paging
- Functions
- Aggregations
- Projections
- Coalesce & Ternary
- GroupBy
Data Providers
Transports
Integrations
Quality
AI Assistants
Migration
Release Notes