
Dotnet Backend Engineer
Add this marketplace when you build .NET backend services with Claude and want a dedicated plugin tooling surface for backend developer tasks.
Overview
dotnet-backend-engineer is a plugin marketplace for the Build phase that provides a .NET Backend Developer tool plugin for Claude-assisted server-side work.
What is this marketplace?
- Single plugin dotnet-backend-engineer with tools aimed at .NET backend development
- Claude plugin bundle from Adria Manzano focused on server-side workflows
- Supports indie and small-team API/service work without switching stacks
- Marketplace packaging for discoverable install vs scattered repo skills
- 1 plugin in marketplace: dotnet-backend-engineer
- Owner: Adria Manzano
What problem does it solve?
.NET solo builders repeat boilerplate explanations to the agent because generic skills do not encode backend-specific conventions and tools.
Who is it for?
Indie developers building APIs or services on .NET who use Claude Code and want backend-scoped plugin tools.
Skip if: Frontend-only stacks, mobile-first shops, or teams not using .NET on the backend.
What do I get? / Deliverables
After install, Claude gains dotnet-backend-engineer plugin tools tuned for .NET backend development tasks in your repo.
- Installed dotnet-backend-engineer Claude plugin
- Agent-accessible tools oriented to .NET backend development
- Faster backend-scoped sessions without re-explaining stack defaults
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Backend engineering plugins belong on the build shelf where APIs, services, and server-side patterns are implemented. Backend subphase is the precise fit for a .NET Backend Developer tool pack rather than generic agent tooling.
How it compares
Stack-specific Claude backend plugin marketplace, not a universal LLM integration or database MCP server.
Common Questions / FAQ
Who is Dotnet Backend Engineer for?
It is for solo builders and small teams developing .NET backends with Claude who want a dedicated plugin marketplace instead of generic coding prompts.
When should I use Dotnet Backend Engineer?
Use it during build when you are implementing or refactoring ASP.NET/Core services, APIs, or backend modules and want agent tools aligned to .NET backend work.
How do I add Dotnet Backend Engineer to my agent?
Register adriamanzano/net-backend-claude-plugin in Claude Code, install the Dotnet Backend Engineer plugin from the marketplace, and invoke its tools while working in your .NET solution.