umbraco-kinds

Generate Umbraco backoffice extension configurations using reusable Kind manifests.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-kinds-kraftvaerk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-kinds
Source: https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy/tree/main/Kraftvaerk.Umbraco.Alchemy.Frontend/.agents/skills/umbraco-kinds
Command: npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-kinds-kraftvaerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of Umbraco backoffice extensions by leveraging the "Kind" system, reducing redundancy and ensuring consistency across different extension types.

Core Features & Use Cases

  • Kind Definition: Create reusable "Kind" manifests that define default properties and configurations for extensions.
  • Extension Implementation: Generate new extensions that inherit from defined Kinds, simplifying their manifest definitions.
  • Use Case: You need to create several new header app buttons for your Umbraco backoffice. Instead of repeating common properties like elementName and default meta values for each button, you can define a "button" Kind and have each new button extension inherit from it.

Quick Start

Use the umbraco-kinds skill to create a new 'button' kind for header apps and then create a new header app extension that uses this kind.

Frequently Asked Questions about umbraco-kinds

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

FAQPage Schema
How do I reduce boilerplate code when creating multiple Umbraco backoffice extensions?

To reduce boilerplate in Umbraco extensions, define reusable "Kind" manifests that specify default properties like elementName and meta values. New extensions inherit these properties, ensuring configuration consistency across your TypeScript Umbraco backoffice projects.

What are Umbraco Kinds and how do they standardize backoffice extension development?

Umbraco Kinds are reusable manifest configurations that define default properties for backoffice extensions. By creating extensions that inherit from a defined Kind, you standardize extension implementation and eliminate redundant configuration code across your project.

How do I create a new Umbraco header app extension using a Kind manifest?

To create an Umbraco header app extension using a Kind, first define a reusable button Kind manifest with default properties. Then, generate the new header app extension to inherit from this Kind, simplifying its manifest definition.

Do I need TypeScript to implement Kinds for Umbraco backoffice extensions?

Yes, TypeScript is required to implement Kinds for Umbraco backoffice extensions. The Skill generates TypeScript-based manifest configurations and extension definitions, ensuring typed consistency within your Umbraco project development workflow.

Can I define default meta values for multiple Umbraco extension types using a single configuration?

Yes, you can define default meta values for multiple Umbraco extension types by creating a reusable Kind manifest. Once a Kind is defined with specific default properties, multiple new extensions can inherit from it to maintain consistent configurations.