umbraco-package-view

Generates Umbraco package view manifests and foundation-compliant UI elements for modal/panel display.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-package-view-albanistrefi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-package-view
Source: https://github.com/albanistrefi/umbraco_CLI/tree/main/skills/extensions/umbraco-package-view
Command: npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-package-view-albanistrefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Umbraco package developers need a reliable way to add custom backoffice UI panels for their installed packages, but the correct extension registry and foundation patterns are easy to get wrong or outdated.

Core Features & Use Cases

  • Package Views via official patterns: Generate a working packageView manifest that registers a UI panel for a specific installed package.
  • Foundation-aligned UI implementation: Create the corresponding UI element using the recommended backoffice foundation base classes (modal/panel context).
  • Documentation-first workflow: Fetch current documentation and then implement the manifest + element in the style Umbraco expects.
  • Use Case: Build a dedicated configuration modal for your Umbraco package so editors can configure package settings directly from the Packages section.

Quick Start

Use the umbraco-package-view skill to implement a packageView modal for your package by first fetching the latest Umbraco docs, then generating the package view manifest and its element so it appears in the backoffice for your installed package.

Frequently Asked Questions about umbraco-package-view

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

FAQPage Schema
How do I add a custom UI panel for an Umbraco package in the backoffice?

To add a custom Umbraco backoffice UI panel, register a packageView extension in the extension registry and implement a foundation-compliant UI element for modal or panel display. The element must match the packageName defined in umbraco-package.json.

What is a packageView extension in Umbraco and when do I need one?

A packageView extension in Umbraco registers a dedicated UI panel for an installed package within the backoffice. You need one when building editor-facing configuration or information modals directly accessible from the Packages section.

How do I create a configuration modal for an Umbraco package using Lit?

To create a configuration modal for an Umbraco package, generate a packageView manifest and implement the corresponding UI element using the recommended backoffice foundation base classes and Lit for modal context display.

Does an Umbraco package view require a matching packageName in umbraco-package.json?

Yes, an Umbraco package view requires the meta.packageName in the generated manifest to match the packageName specified in your umbraco-package.json file for the backoffice to correctly wire the panel to your installed package.

What is the best way to ensure my Umbraco package view manifest follows current foundation patterns?

The best way to ensure your Umbraco package view manifest follows current foundation patterns is to use a documentation-first workflow that fetches the latest Umbraco docs before deterministically generating the manifest and element implementation details.

Can I use the extension registry to display package information panels without manual manifest coding?

Yes, you can use the extension registry to display package information panels by leveraging a documentation-guided generation process that automatically produces the required packageView manifest and foundation-aligned UI element implementation.