@vodailoc/kilo-kit-mcp 1.1.0

package/skills/engineering/aspnet-core/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/engineering/aspnet-core/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: aspnet-core
+description: Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.
+---
+
+# ASP.NET Core
+
+## Overview
+
+Choose the right ASP.NET Core application model, compose the host and request pipeline correctly, and implement features in the framework style Microsoft documents today.
+
+Load the smallest set of references that fits the task. Do not load every reference by default.
+
+## Workflow
+
+1. Confirm the target framework, SDK, and current app model.
+2. Open [references/stack-selection.md](references/stack-selection.md) first for new apps or major refactors.
+3. Open [references/program-and-pipeline.md](references/program-and-pipeline.md) next for `Program.cs`, DI, configuration, middleware, routing, logging, and static assets.
+4. Open exactly one primary app-model reference:
+   - [references/ui-blazor.md](references/ui-blazor.md)
+   - [references/ui-razor-pages.md](references/ui-razor-pages.md)
+   - [references/ui-mvc.md](references/ui-mvc.md)
+   - [references/apis-minimal-and-controllers.md](references/apis-minimal-and-controllers.md)
+5. Add cross-cutting references only as needed:
+   - [references/data-state-and-services.md](references/data-state-and-services.md)
+   - [references/security-and-identity.md](references/security-and-identity.md)
+   - [references/realtime-grpc-and-background-work.md](references/realtime-grpc-and-background-work.md)
+   - [references/testing-performance-and-operations.md](references/testing-performance-and-operations.md)
+6. Open [references/versioning-and-upgrades.md](references/versioning-and-upgrades.md) before introducing new platform APIs into an older solution or when migrating between major versions.
+7. Use [references/source-map.md](references/source-map.md) when you need the Microsoft Learn section that corresponds to a task not already covered by the focused references.
+
+## Default Operating Assumptions
+
+- Prefer the latest stable ASP.NET Core and .NET unless the repository or user request pins an older target.
+- As of March 2026, prefer .NET 10 / ASP.NET Core 10 for new production work. Treat ASP.NET Core 11 as preview unless the user explicitly asks for preview features.
+- Prefer `WebApplicationBuilder` and `WebApplication`. Avoid older `Startup` and `WebHost` patterns unless the codebase already uses them or the task is migration.
+- Prefer built-in DI, options/configuration, logging, ProblemDetails, OpenAPI, health checks, rate limiting, output caching, and Identity before adding third-party infrastructure.
+- Keep feature slices cohesive so the page, component, endpoint, controller, validation, service, data access, and tests are easy to trace.
+- Respect the existing app model. Do not rewrite Razor Pages to MVC or controllers to Minimal APIs without a clear reason.
+
+## Reference Guide
+
+- [references/_sections.md](references/_sections.md): Quick index and reading order.
+- [references/stack-selection.md](references/stack-selection.md): Choose the right ASP.NET Core application model and template.
+- [references/program-and-pipeline.md](references/program-and-pipeline.md): Structure `Program.cs`, services, middleware, routing, configuration, logging, and static assets.
+- [references/ui-blazor.md](references/ui-blazor.md): Build Blazor Web Apps, choose render modes, and use components, forms, and JS interop correctly.
+- [references/ui-razor-pages.md](references/ui-razor-pages.md): Build page-focused server-rendered apps with handlers, model binding, and conventions.
+- [references/ui-mvc.md](references/ui-mvc.md): Build controller/view applications with clear separation of concerns.
+- [references/apis-minimal-and-controllers.md](references/apis-minimal-and-controllers.md): Build HTTP APIs with Minimal APIs or controllers, including validation and response patterns.
+- [references/data-state-and-services.md](references/data-state-and-services.md): Use EF Core, `DbContext`, options, `IHttpClientFactory`, session, temp data, and app state responsibly.
+- [references/security-and-identity.md](references/security-and-identity.md): Apply authentication, authorization, Identity, secrets, data protection, CORS, CSRF, and HTTPS guidance.
+- [references/realtime-grpc-and-background-work.md](references/realtime-grpc-and-background-work.md): Use SignalR, gRPC, and hosted services.
+- [references/testing-performance-and-operations.md](references/testing-performance-and-operations.md): Add integration tests, browser tests, caching, compression, health checks, rate limits, and deployment concerns.
+- [references/versioning-and-upgrades.md](references/versioning-and-upgrades.md): Handle target frameworks, breaking changes, obsolete APIs, and migrations.
+- [references/source-map.md](references/source-map.md): Map the official ASP.NET Core documentation tree to the references in this skill.
+
+## Execution Notes
+
+- When generating new code, start from the correct `dotnet new` template and keep the generated structure recognizable.
+- When editing an existing solution, follow the solution's conventions first and use these references to avoid framework misuse or outdated patterns.
+- When a task mentions "latest", verify the feature on Microsoft Learn or the ASP.NET Core docs repo before relying on memory.

package/skills/engineering/aspnet-core/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "ASP.NET Core"
+  short_description: "[Windows only] Build and review ASP.NET Core web apps"
+  icon_large: "./assets/dotnet-logo.png"
+  default_prompt: "Create a new $aspnet-core website for me."

package/skills/engineering/aspnet-core/references/_sections.md

@@ -0,0 +1,40 @@
+# Reference Sections
+
+Use this file as the routing table for the rest of the skill.
+
+## Start Here
+
+- New app or major redesign: `stack-selection.md` -> `program-and-pipeline.md` -> one primary app-model reference -> `security-and-identity.md` -> `testing-performance-and-operations.md`
+- Existing app feature work: primary app-model reference -> `program-and-pipeline.md` -> any needed cross-cutting references
+- API-first work: `apis-minimal-and-controllers.md` -> `security-and-identity.md` -> `data-state-and-services.md` -> `testing-performance-and-operations.md`
+- Authentication, authorization, or secrets: `security-and-identity.md`
+- Realtime, streaming, or background processing: `realtime-grpc-and-background-work.md`
+- Upgrade or migration work: `versioning-and-upgrades.md`
+
+## Primary References
+
+| File | Open when |
+| --- | --- |
+| `stack-selection.md` | Choose Blazor, Razor Pages, MVC, Minimal APIs, controllers, SignalR, or gRPC |
+| `program-and-pipeline.md` | Structure `Program.cs`, services, configuration, middleware, routing, logging, static files, and app startup |
+| `ui-blazor.md` | Build or review Blazor Web Apps and component-based UI |
+| `ui-razor-pages.md` | Build or review page-focused server-rendered applications |
+| `ui-mvc.md` | Build or review controller/view applications |
+| `apis-minimal-and-controllers.md` | Build or review HTTP APIs |
+
+## Cross-Cutting References
+
+| File | Open when |
+| --- | --- |
+| `data-state-and-services.md` | Register services, use EF Core, handle options/configuration, or manage app state |
+| `security-and-identity.md` | Add Identity, cookies, bearer auth, policies, CORS, CSRF, HTTPS, or secrets handling |
+| `realtime-grpc-and-background-work.md` | Add SignalR, gRPC, streaming, or hosted services |
+| `testing-performance-and-operations.md` | Add tests, caching, compression, health checks, rate limits, deployment, or proxy configuration |
+| `versioning-and-upgrades.md` | Migrate across ASP.NET Core versions, avoid obsolete APIs, or target preview features deliberately |
+| `source-map.md` | Map a task to the official ASP.NET Core documentation tree |
+
+## Reading Strategy
+
+- Open one app-model reference at a time unless the codebase genuinely mixes models.
+- Prefer the framework's built-in abstractions first.
+- Check `versioning-and-upgrades.md` before introducing APIs that might not exist in the repository's target framework.

package/skills/engineering/aspnet-core/references/apis-minimal-and-controllers.md

@@ -0,0 +1,81 @@
+# APIs: Minimal And Controllers
+
+Primary docs:
+- https://learn.microsoft.com/aspnet/core/fundamentals/minimal-apis
+- https://learn.microsoft.com/aspnet/core/web-api/
+- https://learn.microsoft.com/aspnet/core/fundamentals/error-handling-api
+
+## First Decision
+
+Choose between:
+
+- Minimal APIs for focused, low-ceremony HTTP endpoints
+- controller-based APIs for richer MVC conventions and attribute-driven behavior
+
+Do not mix both styles in the same feature unless that split is genuinely useful.
+
+## Minimal API Guidance
+
+Prefer Minimal APIs when the surface is small to medium and you want concise endpoint definitions.
+
+Good defaults:
+
+- organize endpoints with route groups
+- keep route handlers thin
+- move business logic into services
+- prefer `TypedResults` over untyped results
+- use endpoint filters when cross-cutting behavior belongs at the endpoint layer
+- use built-in validation support on supported target frameworks
+
+Minimal API reminders:
+
+- handler parameters can be bound from route, query, headers, body, form, or DI
+- authorization can be applied with `RequireAuthorization`
+- return `IResult` or `TypedResults` when response shape matters
+- use OpenAPI support for discoverable contracts
+
+On .NET 10, Minimal APIs support built-in validation with `AddValidation()`. Use that instead of inventing parallel validation infrastructure when the target framework supports it.
+
+## Controller API Guidance
+
+Prefer controllers when the API needs:
+
+- `[ApiController]` behaviors
+- attribute routing and conventions
+- filters
+- custom formatters
+- mature controller organization in an existing codebase
+
+Controller defaults:
+
+- derive API controllers from `ControllerBase`
+- annotate with `[ApiController]`
+- use attribute routing
+- return ProblemDetails-compatible failures
+- let automatic model validation handle invalid requests unless there is a concrete override requirement
+
+Key `[ApiController]` behaviors:
+
+- attribute routing is required
+- invalid model state automatically becomes HTTP 400
+- binding source inference applies
+- error responses use ProblemDetails patterns
+
+## Shared API Practices
+
+- Keep request and response DTOs separate from persistence models
+- Use version-stable route and payload contracts
+- Use `CreatedAt...` patterns for resource creation
+- Prefer explicit status codes and typed results over implicit behavior
+- Apply authorization at the endpoint or controller boundary, not only inside service methods
+- Use `ProblemDetails` for errors instead of ad hoc JSON shapes
+
+## Browser-Facing Notes
+
+- Be careful with cookie-authenticated API endpoints and CORS
+- For browser-based form or file upload endpoints, account for antiforgery requirements
+- In ASP.NET Core 10, known API endpoints no longer use cookie-login redirects by default; rely on API-appropriate unauthorized responses instead
+
+## Native AOT
+
+Use `dotnet new webapiaot` only when native AOT is an explicit deployment requirement. Treat it as a constraint that affects library choice, reflection, JSON patterns, and compatibility.

package/skills/engineering/aspnet-core/references/data-state-and-services.md

@@ -0,0 +1,69 @@
+# Data, State, And Services
+
+Primary docs:
+- https://learn.microsoft.com/aspnet/core/data/
+- https://learn.microsoft.com/aspnet/core/fundamentals/dependency-injection
+- https://learn.microsoft.com/aspnet/core/fundamentals/http-requests
+- https://learn.microsoft.com/aspnet/core/fundamentals/app-state
+
+## Dependency Injection Defaults
+
+- Register infrastructure and business services in `Program.cs`
+- Inject dependencies through constructors by default
+- Keep scoped services request-bound
+- Avoid resolving scoped services from singletons
+- Use keyed or named patterns only when there is a real need for multiple implementations
+
+## EF Core And DbContext
+
+Use EF Core for common relational data access patterns unless the repository already uses another data layer.
+
+Default guidance:
+
+- register `DbContext` with `AddDbContext`
+- treat `DbContext` as scoped
+- keep queries and transactions in services, not UI code
+- use migrations intentionally
+- keep entities out of public API contracts and UI view models
+
+Use `IDbContextFactory<TContext>` when the execution model is not request-scoped, such as:
+
+- Blazor components with longer-lived scopes
+- background services
+- explicit factory-driven data work
+
+## Options And Configuration
+
+- Bind structured configuration into options classes
+- validate options early when bad configuration should fail fast
+- keep configuration access close to the service that owns it
+- avoid scattering raw configuration keys across the codebase
+
+## Outbound HTTP
+
+Use `IHttpClientFactory` for outbound HTTP calls.
+
+Prefer:
+
+- named clients for distinct external systems
+- typed clients for richer integrations
+- delegating handlers for retries, headers, or telemetry concerns
+
+Avoid manual `new HttpClient()` patterns scattered through request handlers.
+
+## App State
+
+Use the smallest state mechanism that fits:
+
+- query string or route values for transparent request state
+- form posts for user input
+- TempData for short-lived redirect-friendly messages
+- session only when necessary and with an understanding of its server-side and scaling implications
+
+Do not treat session as the primary application data store.
+
+## Caching And State Boundaries
+
+- Keep cached data derivable from a durable source
+- Separate cache shape from persistence shape when it improves safety or performance
+- Revisit session, in-memory cache, and singleton state when the app scales to multiple instances

package/skills/engineering/aspnet-core/references/program-and-pipeline.md

@@ -0,0 +1,103 @@
+# Program And Pipeline
+
+Primary docs:
+- https://learn.microsoft.com/aspnet/core/fundamentals/
+- https://learn.microsoft.com/aspnet/core/fundamentals/minimal-apis/webapplication
+- https://learn.microsoft.com/aspnet/core/fundamentals/middleware/
+- https://learn.microsoft.com/aspnet/core/fundamentals/configuration/
+
+## Startup Shape
+
+Prefer the modern hosting model:
+
+1. Create `var builder = WebApplication.CreateBuilder(args);`
+2. Register services on `builder.Services`
+3. Build `var app = builder.Build();`
+4. Configure middleware in the correct order
+5. Map endpoints
+6. Call `app.Run();`
+
+Use older `Startup` patterns only when the repository already uses them or the task is migration.
+
+## Service Registration
+
+- Register framework services explicitly: Razor Pages, controllers, Razor components, authentication, authorization, health checks, rate limiting, response compression, output caching, EF Core, and `IHttpClientFactory`
+- Keep business logic in services instead of controllers, page models, or route handlers
+- Use constructor injection as the default
+- Use options classes for structured configuration
+- Choose lifetimes intentionally:
+  - singleton: stateless or shared infrastructure
+  - scoped: request-bound work such as `DbContext`
+  - transient: lightweight stateless services
+
+## Configuration Defaults
+
+`WebApplication.CreateBuilder` already loads configuration from common providers such as:
+
+- `appsettings.json`
+- environment-specific `appsettings.{Environment}.json`
+- environment variables
+- command-line arguments
+
+For secrets:
+
+- use Secret Manager in development
+- use a secure external store in production
+- do not commit secrets to source control
+
+## Middleware Order
+
+Middleware order is a frequent source of broken behavior. Favor this shape and adjust only with a concrete reason:
+
+1. Forwarded headers if behind a proxy or load balancer
+2. Exception handling and HSTS for non-development environments
+3. HTTPS redirection
+4. Static files
+5. Routing when explicit routing middleware is needed
+6. CORS when endpoints require it
+7. Authentication
+8. Authorization
+9. Endpoint-specific middleware such as rate limiting or session as required
+10. Endpoint mapping with `MapRazorPages`, `MapControllers`, `MapGet`, `MapHub`, or `MapGrpcService`
+
+Important ordering rules:
+
+- Call `UseAuthentication()` before `UseAuthorization()`
+- Keep proxy/header processing before auth, redirects, and link generation
+- Do not insert custom middleware randomly between auth and authorization without a reason
+- In Minimal API apps, explicit `UseRouting()` is usually unnecessary unless you need to control order
+
+## Routing And Endpoints
+
+- Prefer endpoint routing everywhere
+- Use route groups for larger Minimal API surfaces
+- Keep MVC and API routes explicit and predictable
+- Use areas only when the application is large enough to benefit from bounded sections
+- Keep endpoint names stable when generating links or integrating with clients
+
+## Error Handling
+
+- Use centralized exception handling instead of scattered `try/catch` blocks for ordinary request failures
+- Prefer ProblemDetails-style responses for APIs
+- Keep the developer exception page limited to development
+- Separate user-facing failures from internal exception details
+
+## Logging And Diagnostics
+
+- Use `ILogger<T>` from DI
+- Log structured values, not concatenated strings
+- Put correlation and request diagnostics in middleware or infrastructure, not business logic
+- Enable HTTP logging only when the scenario warrants it and avoid leaking sensitive data
+
+## Static Assets And Web Root
+
+- Keep public assets in `wwwroot`
+- Treat the web root as publicly readable content
+- Prevent publishing local-only static content through project file rules when needed
+- Use Razor Class Libraries for reusable UI assets across apps
+
+## Architectural Defaults
+
+- Keep `Program.cs` readable; extract feature registration to extension methods when it starts accumulating unrelated concerns
+- Prefer vertical slices or feature folders over giant "Controllers", "Services", and "Repositories" buckets with weak boundaries
+- Keep framework configuration close to the host and business logic out of it

package/skills/engineering/aspnet-core/references/realtime-grpc-and-background-work.md

@@ -0,0 +1,58 @@
+# Realtime, gRPC, And Background Work
+
+Primary docs:
+- https://learn.microsoft.com/aspnet/core/signalr/introduction
+- https://learn.microsoft.com/aspnet/core/grpc/
+- https://learn.microsoft.com/aspnet/core/fundamentals/host/hosted-services
+
+## SignalR
+
+Use SignalR when the server must push updates to connected clients in near real time.
+
+Good fits:
+
+- chat
+- dashboards
+- notifications
+- collaborative editing
+- live status streams
+
+Guidance:
+
+- model the hub as a communication boundary, not the home of business logic
+- use groups and user targeting deliberately
+- authenticate connections when data is user-specific
+- plan for scale-out if the app may run on multiple instances
+
+Remember that Blazor interactive server rendering already relies on a real-time connection. Do not add a second realtime channel unless the feature truly needs one.
+
+## gRPC
+
+Use gRPC for efficient service-to-service communication, strongly typed contracts, and streaming over HTTP/2.
+
+Prefer gRPC when:
+
+- both ends are under your control
+- performance and contract fidelity matter
+- streaming is a first-class requirement
+
+Guidance:
+
+- keep `.proto` contracts versioned and stable
+- generate client and server types from contracts
+- keep auth, logging, and DI integrated with the host
+- account for browser interoperability differences before choosing gRPC for public browser clients
+
+## Background Work
+
+Use `IHostedService` or `BackgroundService` for in-process background tasks tied to the application host.
+
+Defaults:
+
+- keep background services small and observable
+- create scopes for scoped dependencies
+- do not capture scoped services directly in singleton hosted services
+- respect cancellation tokens
+- avoid long blocking startup paths
+
+If the work is durable, high-volume, or business-critical, consider whether it belongs in an out-of-process queue or worker instead of only inside the web host.