Menu
Place reusable auth components in the shared layer without breaking ASP.NET Core consumers or tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Authorization Code Flow for web applications using MSAL.NET confidential client to sign in users and access APIs on their behalf
Handle MSAL distributed token cache collisions and stale entries in ASP.NET Core applications
On-Behalf-Of (OBO) Flow for web APIs to call downstream APIs while preserving user identity in MSAL.NET
{what this skill teaches agents}
Review API DTO implementations for contract/domain separation, mapping patterns, and REST compliance
This skill should be used when the user asks to "build a feature", "fix a bug", "implement something", "start a dev cycle", types "/dev", or describes a software task that requires design, implementation, testing, and shipping. Orchestrates the full software development lifecycle from interrogation through shipping, with self-learning that improves over time.
| name | shared-auth-component-placement |
| description | Place reusable auth components in the shared layer without breaking ASP.NET Core consumers or tests. |
| domain | authentication |
| confidence | high |
| source | earned |
Use this when an authentication or authorization component is being extracted from a host project into a shared library such as Managers.
JosephGuadagno.Broadcasting.Managers instead of duplicating it per
host.IClaimsTransformation, add
<FrameworkReference Include="Microsoft.AspNetCore.App" /> to that
class library.src\JosephGuadagno.Broadcasting.Managers\EntraClaimsTransformation.cssrc\JosephGuadagno.Broadcasting.Managers\JosephGuadagno.Broadcasting.Managers.csprojsrc\JosephGuadagno.Broadcasting.Web.Tests\EntraClaimsTransformationTests.cs