Agent Plugins Marketplace
← All plugins

dotnet-backend

v1.0.2

Pure .NET 10 backend architecture for Kestrel-hosted REST and SignalR services with DI, data access, and SOLID review

Claude Code1 Skill

By John KozarisLicense: MIT3 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes
Claude Code
Parsed components
1 skill or MCP entry
Source updated
Sep 25, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install dotnet-backend for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dotnet-backend@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mathisk2095/jko-claude-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dotnet-backend/.

Plugin files

plugins/dotnet-backend/
├── .claude-plugin/plugin.json
└── skills/dotnet-backend-expert/SKILL.md

Included Skills1

dotnet-backend-expertskills/dotnet-backend-expert/SKILL.md

This skill should be used when the user is writing, reviewing, debugging, or architecting pure .NET backend code for Kestrel-hosted services. It provides expert critique for REST endpoints, SignalR hubs, TypeScript/React client integration shape, pragmatic Rust interop, application services, AppHost-aware project structure, EF Core and database boundaries, dependency injection lifetimes, OOP and SOLID quality, concurrency, and distributed-architecture tradeoffs. Use when the user asks "critique my .NET backend", "review this service", "should this be singleton or scoped", "structure my solution", "review my SignalR hub", "review my AppHost", "is this clean architecture", "should I use repositories", "fix my DbContext usage", "design my REST endpoints", "review my concurrency", or "should this be microservices".

Plugin manifests1

plugins/dotnet-backend/.claude-plugin/plugin.json
{
  "name": "dotnet-backend",
  "description": "Pure .NET 10 backend architecture for Kestrel-hosted REST and SignalR services with DI, data access, and SOLID review",
  "version": "1.0.2",
  "license": "MIT",
  "author": {
    "name": "John Kozaris"
  },
  "homepage": "https://github.com/johnkozaris/jko-claude-plugins",
  "repository": "https://github.com/johnkozaris/jko-claude-plugins",
  "keywords": [
    "dotnet",
    "dotnet10",
    "csharp",
    "kestrel",
    "backend",
    "rest",
    "signalr",
    "efcore",
    "solid",
    "clean-architecture",
    "dependency-injection",
    "apphost",
    "aspire",
    "architecture",
    "review"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[dotnet-backend on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dotnet-backend)