umbraco-kinds

Name: umbraco-kinds
Availability: InStock
Author: albanist

Generate Umbraco Kind manifests and consuming extension examples from official documentation.

4|Updated Mar 6, 2026

Search Tags:#typescript #umbraco #backoffice #extension registry #manifest generation #extension kinds #documentation driven

Ready to run

npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-kinds-albanistrefi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: umbraco-kinds
Source: https://github.com/albanistrefi/umbraco_CLI/tree/main/skills/extensions/umbraco-kinds
Command: npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-kinds-albanistrefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you implement Umbraco backoffice extension Kinds correctly and consistently by turning the official documentation into ready-to-use manifests and extension examples.

Core Features & Use Cases

Guides implementation from the latest docs: Fetches current official references for Kinds, foundation concepts, and the extension registry so your solution matches Umbraco’s expected structure.
Creates reusable Kind manifests: Produces a Kind definition that other extensions can inherit to reduce duplication and enforce standardized configuration.
Shows how to consume a Kind in extensions: Generates an example extension manifest that references a Kind via kind, ensuring default meta values and structure work as intended.

Quick Start

Ask the AI to fetch the latest Umbraco docs and generate a complete Kind manifest plus one consuming extension example for your specified extension type and shared default meta properties.

Frequently Asked Questions about umbraco-kinds

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

FAQPage Schema

How do I create reusable Umbraco backoffice extension Kinds with shared defaults?▼

Umbraco backoffice extension Kinds let you define reusable manifests with shared default meta values. This Skill fetches official documentation and generates a Kind definition plus consuming extension examples that enforce standardized configuration and reduce duplication across multiple extensions.

What is an Umbraco extension Kind and when do I need to use it?▼

An Umbraco extension Kind is a manifest definition that provides shared defaults and standardized configuration for multiple backoffice extensions. You need it when multiple extensions require reusable meta behavior, ensuring consistency and reducing duplicated configuration across your extension registry.

How do I generate Umbraco extension manifests that follow the correct naming and alias conventions?▼

To generate Umbraco extension manifests, fetch the latest Kind, foundation, and extension registry documentation. This Skill aligns with current official references to produce manifests and consuming extension artifacts that match the required schema and naming conventions for the backoffice extension registry.

Can I use TypeScript to implement Umbraco backoffice extension Kinds for multiple extensions?▼

Yes, TypeScript is used to implement Umbraco backoffice extension Kinds. This Skill converts official documentation into working TypeScript manifests and extension examples, allowing you to generate kind and consuming extension artifacts that follow the required manifest schema.

Does this approach require fetching the latest Umbraco documentation before generating Kind manifests?▼

Fetching the latest Umbraco documentation is required before generating Kind manifests. This Skill aligns with current Kind, foundation, and extension registry docs to ensure your backoffice extension manifests and consuming examples match Umbraco’s expected structure and configuration.

What's the best way to standardize configuration across multiple Umbraco backoffice extensions?▼

The best way to standardize configuration across Umbraco backoffice extensions is by using extension Kinds. This Skill produces Kind definitions that other extensions can inherit, enforcing standardized meta behavior and reducing configuration duplication across your extension registry.