01
Navigate .NET solutions
Understand solutions, projects, target frameworks, central package management, analyzers, generated code, build properties, and shared configuration.
.NET development
CategorySoftware Development
Codex Skills for .NET
Codex Skills for .NET give Codex a version-aware workflow for building and maintaining C#, F#, ASP.NET Core, worker, desktop, cloud, library, and test projects. Download the skills for solution navigation, dependency management, APIs, data access, asynchronous code, testing, performance, packaging, and deployment.
.NETASP.NET CoreC# and F#Testing
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete .net development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A .NET change can compile locally while breaking target frameworks, dependency injection, configuration, serialization, migrations, trimming, packaging, or runtime behavior.
Reliable .NET work begins with the SDK, target frameworks, solution structure, project files, language versions, workloads, packages, analyzers, runtime identifiers, and deployment model.
These skills help Codex inspect the actual solution before choosing framework APIs, project settings, test levels, asynchronous patterns, or compatibility changes.
What the downloadable skills can do
What Codex Skills for .NET can help accomplish
02
Build applications and services
Develop ASP.NET Core APIs, background services, command-line tools, desktop apps, libraries, configuration, logging, and dependency injection.
03
Work with data and concurrency
Use Entity Framework Core or project data access, transactions, validation, serialization, cancellation, tasks, streams, and thread-safe patterns.
04
Test and ship reliably
Create unit and integration tests, run analyzers and builds, handle migrations, measure performance, package libraries, publish applications, and verify deployment.
A repeatable working process
How the .net development workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Inspect the .NET environment
Read global.json, SDK and target frameworks, solution and project files, package sources, workloads, analyzers, tests, and deployment targets.
02
Trace application behavior
Follow dependency injection, configuration, middleware, data, serialization, asynchronous flow, resources, and failure handling.
03
Implement a compatible scoped change
Follow language and framework conventions, preserve public APIs where required, handle cancellation, and update project configuration deliberately.
04
Run proportionate verification
Restore, build, test affected levels, run analyzers, inspect migrations and packages, publish relevant targets, and exercise runtime behavior.
Useful across real projects
Where Codex Skills for .NET fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
ASP.NET Core
Build APIs, Razor or MVC applications, middleware, authentication, authorization, validation, data access, and integration tests.
Services and workers
Develop background services, queues, scheduled work, hosted processes, resilience, telemetry, and graceful shutdown.
Libraries and tools
Create packages, command-line tools, source generators, analyzers, multi-targeted libraries, documentation, and compatibility tests.
Desktop and cross-platform apps
Work with supported .NET UI stacks, platform APIs, packaging, configuration, data, testing, and deployment.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create a .NET project
02Build an ASP.NET Core API
03Implement a background worker
04Add Entity Framework Core data access
05Fix asynchronous code
06Write unit and integration tests
07Update NuGet packages safely
08Publish a .NET application
Who benefits most
Who Is This For?
These skills are designed for people who need dependable .net development work with a visible process.
.NET developers
Build maintainable applications, services, libraries, tests, and tooling against declared framework versions.
Backend teams
Develop ASP.NET Core APIs and workers with clear configuration, data, security, and operations.
Enterprise teams
Maintain large multi-project solutions, compatibility promises, analyzers, packages, migrations, and deployment processes.
Library authors
Design stable APIs, multi-targeted packages, documentation, tests, performance, and release artifacts.
Good to know:
The skills assist .NET development but cannot guarantee production compatibility without the actual SDK, workloads, package sources, target platforms, external services, deployment environment, and qualified security review.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the .NET skills
Keep SKILL.md with solution, framework, data, concurrency, testing, packaging, and deployment guidance.
Use project scope
Install with the solution so the skills follow global.json, project files, target frameworks, analyzers, and repository conventions.
Record platform constraints
Provide SDK, target frameworks, C# or F# versions, workloads, operating systems, databases, packages, and deployment model.
List verification commands
Add restore, format, build, analyzer, unit, integration, migration, publish, performance, and deployment checks.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Do the skills support modern .NET and .NET Framework?+
They adapt to the target frameworks declared by the solution and avoid assuming modern APIs are available in legacy projects.
Can they build ASP.NET Core applications?+
Yes. They cover routing, middleware, dependency injection, configuration, authentication, data access, testing, and deployment.
Do they support C# and F#?+
Yes, when the project language, version, style, and tooling are provided.
Can they write integration tests?+
Yes. They can use the project's test framework and suitable application or infrastructure test hosts.
Will they update NuGet packages?+
They can prepare and verify targeted updates while checking framework compatibility, transitive changes, advisories, builds, tests, and runtime behavior.
Make the work repeatable
Give Codex a .NET workflow that respects the solution graph, target frameworks, runtime behavior, and evidence from the complete toolchain.
Clear context. Purposeful work. Relevant checks. A result others can understand.