shiny-mediator

Generate Shiny Mediator handlers, contracts, and middleware scaffolding for .NET applications.

52|6|Updated Apr 27, 2024
One-click install
npx skills add https://github.com/shinyorg/mediator --skill shiny-mediator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shiny-mediator
Source: https://github.com/shinyorg/mediator/tree/main/skills/shiny-mediator
Command: npx skills add https://github.com/shinyorg/mediator --skill shiny-mediator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically generates Shiny Mediator boilerplate, including handlers, contracts, middleware, and scaffolding templates, reducing manual setup and speeding up project bootstrapping.

Core Features & Use Cases

  • Code generation for Contracts (IRequest, ICommand, IEvent, IStreamRequest) and corresponding Handlers, plus middleware wiring.
  • Project scaffolding for common .NET app types (ASP.NET, MAUI, Blazor) with standard folders (Contracts/, Handlers/, Middleware/).
  • Migration support from MediatR and quick-start templates to bootstrap new apps with integrated DI and configuration.

Quick Start

Invoke the Shiny Mediator Skill to generate a complete set of handlers, contracts, middleware, and scaffolding for a new .NET project.

Frequently Asked Questions about shiny-mediator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Shiny Mediator boilerplate for a .NET application?

To generate Shiny Mediator boilerplate, you can use a scaffolding tool that automatically creates contracts, handlers, and middleware. This reduces manual setup and accelerates project bootstrapping by organizing code into structured directories.

Can I scaffold Shiny Mediator code across different .NET project types like Blazor and MAUI?

Yes, you can scaffold Shiny Mediator code across ASP.NET, MAUI, Blazor, and console apps. The scaffolding process creates standard Contracts, Handlers, and Middleware directories tailored for these common .NET app types.

What is the best way to structure Mediator contracts and handlers in a .NET project?

The best way to structure Mediator contracts and handlers is through template-driven code generation. This approach organizes your project with dedicated Contracts, Handlers, and Middleware directories, properly generating IRequest, ICommand, IEvent, and IStreamRequest definitions.

How do I apply middleware attributes when generating Shiny Mediator handlers?

When applying middleware attributes during Shiny Mediator handler generation, you must use proper partial-class guidance. This ensures the template-driven code generation correctly wires the middleware without disrupting the scaffolded handler structure.

Does Shiny Mediator offer migration support from MediatR for existing .NET apps?

Yes, Shiny Mediator offers migration support from MediatR. It provides quick-start templates to bootstrap new apps with integrated dependency injection and configuration, facilitating a smoother transition for existing .NET projects.