跳到正文
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(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.RateLimiting302026年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.RateLimiting302026年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.RateLimiting302026年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.RateLimiting302026年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.RateLimiting302026年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.RateLimiting302026年10月11日 更新

查看 managedcode 的全部技能

报告此技能的问题