umbraco-composing
Register custom code into an Umbraco 17+ site at startup: composers, IUmbracoBuilder extension methods, collection builders (content finders, URL providers, health checks), composer ordering, disabling or replacing built-in implementations, and startup components gated by runtime level. Use this whenever the user asks to "register a service or notification handler in Umbraco", "create a composer", "add my content finder before Umbraco's", "replace or remove a built-in Umbraco implementation", "make my composer run after another one", "disable a package's composer", "run code when Umbraco starts", "only run this once Umbraco is installed / not during an upgrade", "migrate our composers and components from Umbraco 13", or reports that "IComponent is obsolete" or a startup InvalidOperationException from the CreateUmbracoBuilder() chain. SKIP: non-Umbraco projects, Umbraco < 17, client-side backoffice extensions registered through umbraco-package.json, and plain ASP.NET Core middleware.
Source facts
- Repository
- umbraco/Umbraco-CMS-Implementation-Skills
- Last source activity
- October 20, 2026 at 14:54
- Detected SKILL.md language
- English
- Stars
- 7
- Forks
- 8
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
| name | umbraco-composing |
|---|---|
| description | Register custom code into an Umbraco 17+ site at startup: composers, IUmbracoBuilder extension methods, collection builders (content finders, URL providers, health checks), composer ordering, disabling or replacing built-in implementations, and startup components gated by runtime level. Use this whenever the user asks to "register a service or notification handler in Umbraco", "create a composer", "add my content finder before Umbraco's", "replace or remove a built-in Umbraco implementation", "make my composer run after another one", "disable a package's composer", "run code when Umbraco starts", "only run this once Umbraco is installed / not during an upgrade", "migrate our composers and components from Umbraco 13", or reports that "IComponent is obsolete" or a startup InvalidOperationException from the CreateUmbracoBuilder() chain. SKIP: non-Umbraco projects, Umbraco < 17, client-side backoffice extensions registered through umbraco-package.json, and plain ASP.NET Core middleware. |