umbraco-kinds

Create reusable kind manifests for Umbraco backoffice extensions.

26|13|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills --skill umbraco-kinds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-kinds
Source: https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills/tree/main/plugins/umbraco-backoffice-skills/skills/umbraco-kinds
Command: npx skills add https://github.com/umbraco/Umbraco-CMS-Backoffice-Skills --skill umbraco-kinds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create and manage "kinds" in Umbraco, which are preset configurations that ensure consistency and reduce redundancy across different backoffice extensions.

Core Features & Use Cases

  • Kind Definition: Create reusable kind manifests that define default properties for extension types.
  • Extension Integration: Show how new extensions can inherit and override properties from defined kinds.
  • Use Case: Standardize all custom dashboard cards to have a default size and color, while allowing individual cards to specify unique labels and paths.

Quick Start

Use the umbraco-kinds skill to generate a new kind manifest for a 'headerApp' extension type with the alias 'My.Kind.HeaderAppButton'.

Frequently Asked Questions about umbraco-kinds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize default properties for custom Umbraco backoffice extensions?

You can define a reusable kind manifest to establish default properties for specific extension types. This approach standardizes configurations like default dashboard card sizes and colors, ensuring consistency while reducing redundancy across custom backoffice extensions.

What is a kind in Umbraco and when do I need it?

A kind in Umbraco is a preset configuration that defines default properties for extension types. You need it when creating custom backoffice extensions to ensure consistency and reduce redundancy across multiple extensions while adhering to the extension API for manifest creation.

How do I create a kind manifest for an Umbraco extension type?

To create a kind manifest, define a reusable kind with an alias like 'My.Kind.HeaderAppButton' for your extension type. New extensions can then inherit and override properties from this defined kind following Umbraco's extension API for manifest creation and inheritance.

Can I override default properties inherited from an Umbraco kind?

Yes, extensions can inherit default properties from a defined kind while specifying unique values. For example, custom dashboard cards can inherit a default size and color from a kind while allowing individual cards to specify unique labels and paths.

Do I need to follow the Umbraco extension API to configure kinds?

Yes, configuring kinds requires adherence to Umbraco's extension API for manifest creation and inheritance. This ensures your kind manifests are properly structured and extensions can correctly inherit and override the defined preset configurations.