What problem does it solve? Extending Sitecore's native pipeline engine requires knowing how to patch processors into built-in pipelines, define custom named pipelines, and bind config values to processor properties — patterns that are easy to get wrong without verified reference implementations. ## Core Features & Use Cases - Extend Built-in Pipelines: Patch C# processors into existing Sitecore pipelines (initialize, owin.initialize, httpRequestProcessed, mvc.*) using patch:before/patch:after XML positioning. - Define Custom Pipelines: Create brand-new named pipelines invoked via CorePipeline.Run, either as flat dotted names or domain-scoped groups for per-feature isolation. - Supporting Conventions: Covers config-binding rules (hint="list", hint="raw:AddPropertyMap"), an ambient DI/logging args base pattern, a scoped-logging leading processor, and the standard App_Config/Include/{Feature|Foundation}/{SolutionName}/ config location. - Use Case: When adding a SAML2 authentication flow to a Sitecore solution, use this Skill to define a domain-scoped pipeline group with command and session sub-pipelines, chained processors, and an example config shipped inert until environment values are filled in. ## Quick Start Use the sitecore-pipelines skill to add a new processor to the httpRequestProcessed pipeline with the correct config patch and file location.
