本文へ移動
cccskills
無料GitHub で公開

managedcode-orleans-signalr

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md1.6 KB
  • manifest.json158 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

ManagedCode.Orleans.SignalR

Trigger On

  • integrating ManagedCode.Orleans.SignalR into a real-time distributed application
  • coordinating SignalR delivery from Orleans grains
  • reviewing grain-to-hub push flows and connection routing
  • documenting how Orleans state or events become SignalR messages

Workflow

  1. Confirm the application genuinely needs both Orleans and SignalR in the same flow.
  2. Identify which grain events or workflows should publish to connected clients.
  3. Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
  4. Document how user, group, or connection targeting is resolved.
  5. Validate end-to-end message delivery from grain event to connected client.
flowchart LR
  A["Orleans grain event"] --> B["ManagedCode.Orleans.SignalR integration"]
  B --> C["SignalR hub delivery"]
  C --> D["Connected client or group"]

Deliver

  • guidance on where the Orleans-to-SignalR bridge belongs
  • separation between grain logic and transport concerns
  • validation expectations for real-time distributed delivery

Validate

  • the integration is justified instead of mixing Orleans and SignalR casually
  • grain logic stays focused on domain or orchestration concerns
  • real-time delivery is verified end to end, not only through registration code

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

Calculates CRAP (Change Risk Anti-Patterns) score for .NET methods, classes, or files. Use when the user asks to assess test quality, identify risky untested code, compute CRAP scores, or evaluate whether complex methods have sufficient test coverage. Requires code coverage data (Cobertura XML) and cyclomatic complexity analysis. DO NOT USE FOR: writing tests, general test execution unrelated to coverage/CRAP analysis, or general code coverage reporting without CRAP context.

日本語の概要は準備中です。原文の説明を表示しています。

managedcode/Orleans.RateLimiting292026年10月11日 更新

managedcode のスキルをすべて見る

このスキルの問題を報告する