managedcode-orleans-signalr

Name: managedcode-orleans-signalr
Author: managedcode

461stars35forks

How to install managedcode-orleans-signalr?

managedcode/dotnet-skills/managedcode-orleans-signalr

$npx -y skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr

Installs into the current project.

Summary

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating

Files · 1

View on GitHub

SKILL.md

1	# ManagedCode.Orleans.SignalR
2
3	## Trigger On
4
5	- integrating `ManagedCode.Orleans.SignalR` into a real-time distributed application
6	- coordinating SignalR delivery from Orleans grains
7	- reviewing grain-to-hub push flows and connection routing
8	- documenting how Orleans state or events become SignalR messages
9
10	## Workflow
11
12	1. Confirm the application genuinely needs both Orleans and SignalR in the same flow.
13	2. Identify which grain events or workflows should publish to connected clients.
14	3. Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
15	4. Document how user, group, or connection targeting is resolved.
16	5. Validate end-to-end message delivery from grain event to connected client.
17
18	```mermaid
19	flowchart LR
20	A["Orleans grain event"] --> B["ManagedCode.Orleans.SignalR integration"]
21	B --> C["SignalR hub delivery"]
22	C --> D["Connected client or group"]
23	```
24
25	## Deliver
26
27	- guidance on where the Orleans-to-SignalR bridge belongs
28	- separation between grain logic and transport concerns
29	- validation expectations for real-time distributed delivery
30
31	## Validate
32
33	- the integration is justified instead of mixing Orleans and SignalR casually
34	- grain logic stays focused on domain or orchestration concerns
35	- real-time delivery is verified end to end, not only through registration code

People who liked this also viewed

6 picks

Type

managedcode-orleans-signalr

461stars35forks

View on GitHub

How to install managedcode-orleans-signalr?

managedcode/dotnet-skills/managedcode-orleans-signalr

$npx -y skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# ManagedCode.Orleans.SignalR
2
3	## Trigger On
4
5	- integrating `ManagedCode.Orleans.SignalR` into a real-time distributed application
6	- coordinating SignalR delivery from Orleans grains
7	- reviewing grain-to-hub push flows and connection routing
8	- documenting how Orleans state or events become SignalR messages
9
10	## Workflow
11
12	1. Confirm the application genuinely needs both Orleans and SignalR in the same flow.
13	2. Identify which grain events or workflows should publish to connected clients.
14	3. Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
15	4. Document how user, group, or connection targeting is resolved.
16	5. Validate end-to-end message delivery from grain event to connected client.
17
18	```mermaid
19	flowchart LR
20	A["Orleans grain event"] --> B["ManagedCode.Orleans.SignalR integration"]
21	B --> C["SignalR hub delivery"]
22	C --> D["Connected client or group"]
23	```
24
25	## Deliver
26
27	- guidance on where the Orleans-to-SignalR bridge belongs
28	- separation between grain logic and transport concerns
29	- validation expectations for real-time distributed delivery
30
31	## Validate
32
33	- the integration is justified instead of mixing Orleans and SignalR casually
34	- grain logic stays focused on domain or orchestration concerns
35	- real-time delivery is verified end to end, not only through registration code

People who liked this also viewed

6 picks

Type