What problem does it solve? Sitecore SXA View Renderings fail outside the normal page-rendering pipeline (Web API controllers, background jobs) with an InvalidOperationException about an empty ViewContext stack. This Skill wires a .cshtml up as a Controller Rendering with a custom RenderingViewPath so it renders reliably from any context, without writing new controller code. ## Core Features & Use Cases - Controller Rendering setup: Reuses the existing Sitecore.XA.Foundation.Mvc.Controllers.StandardController with Controller Action Index and a RenderingViewPath field pointing at your .cshtml — no new C# required. - SPE-based template conversion: Converts an existing View Rendering item to the Controller Rendering template via Sitecore PowerShell Extensions, including the static TemplateManager.ChangeTemplate overload and the gotcha that the old Path value does not carry over to RenderingViewPath. - View location convention: Places the .cshtml under ~/Areas/$mvc_area$/Views/{FeatureName}/ so RenderingViewResolver can resolve the virtual path, with .csproj registration guidance. - Use Case: A search result variant rendered by SXA's Web API SearchController throws "Attempt to retrieve context object of type System.Web.Mvc.ViewContext from empty stack" — convert its View Rendering item to a Controller Rendering pointing at the same .cshtml and it renders immediately. ## Quick Start Convert my existing SXA View Rendering item at /sitecore/content/.../SearchResultVariant into a Controller Rendering that uses the .cshtml at /Areas/v1/Views/Search/SearchResultVariant.cshtml.
