Umbraco Claude Skills
The Umbraco CMS Backoffice Skills are Claude Code plugins that provide guidance on building Umbraco backoffice extensions. They contain official documentation, patterns, and working examples for each extension type.
Installation
Section titled “Installation”/plugin marketplace add umbraco/Umbraco-CMS-Backoffice-Skills/plugin install umbraco-cms-backoffice-skills@umbraco-backoffice-marketplace/plugin install umbraco-cms-backoffice-testing-skills@umbraco-backoffice-marketplaceAvailable Plugins
Section titled “Available Plugins”umbraco-cms-backoffice-skills (57 skills)
Section titled “umbraco-cms-backoffice-skills (57 skills)”Skills for every Umbraco backoffice extension type:
| Category | Key Skills |
|---|---|
| Actions | umbraco-entity-actions, umbraco-collection-action, umbraco-entity-bulk-actions, umbraco-entity-create-option-action |
| UI | umbraco-dashboard, umbraco-workspace, umbraco-modals, umbraco-sections, umbraco-tree |
| Property Editors | umbraco-property-editor-ui, umbraco-property-editor-schema, umbraco-property-action |
| Foundation | umbraco-context-api, umbraco-extension-registry, umbraco-conditions, umbraco-state-management |
| Rich Text | umbraco-tiptap-extension, umbraco-tiptap-toolbar-extension, umbraco-tiptap-statusbar-extension |
umbraco-cms-backoffice-testing-skills (8 skills)
Section titled “umbraco-cms-backoffice-testing-skills (8 skills)”| Skill | Purpose |
|---|---|
umbraco-testing | Router — helps choose the right testing approach |
umbraco-e2e-testing | Playwright E2E patterns for Umbraco |
umbraco-playwright-testhelpers | @umbraco/playwright-testhelpers reference |
umbraco-unit-testing | Unit/component testing with @open-wc/testing |
umbraco-msw-testing | Mock Service Worker patterns |
umbraco-mocked-backoffice | Run backoffice with mocked APIs |
umbraco-test-builders | JsonModels.Builders for test data |
umbraco-example-generator | Generate testable example extensions |
When to Use Skills
Section titled “When to Use Skills”- Before implementing any extension type — invoke the skill first to see official patterns
- Before writing tests — use
umbraco-testingto choose the right approach - When something doesn’t work — skills may reveal configuration or registration steps you missed
Critical Lesson: Skills Are Supplementary
Section titled “Critical Lesson: Skills Are Supplementary”- How Umbraco itself implements similar features- The actual API signatures and expected behaviour- Edge cases not covered in documentation
**Lesson learned (Feb 2026):** Multiple attempts to implement a collection create option failed because only skills/docs were consulted. The CMS source code revealed the extension point didn't exist in v17. Significant time and tokens were wasted.The Right Workflow
Section titled “The Right Workflow”- Invoke the skill — get the official pattern and example code
- Search the CMS source — find how Umbraco implements the same extension type internally
- Compare and adapt — use the skill’s pattern but verify details against the source
- Implement — with confidence that the approach actually works
Key Source Paths
Section titled “Key Source Paths”Umbraco-CMS/src/Umbraco.Web.UI.Client/src/packages/├── core/ # Core extension types, registries, conditions├── documents/ # Document-related features├── media/ # Media handling├── members/ # Member management└── ...References
Section titled “References”- Umbraco CMS Backoffice Skills — plugin repository
- Umbraco CMS source — definitive reference
- UUI Storybook — base UI primitives
- Umbraco API Docs Storybook — composed components and patterns