skills.rest
kraftvaerk
kraftvaerkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

umbraco-review-checks

Validate Umbraco backoffice extensions against code quality, architecture, and UI standards.

Updated Mar 6, 2026
Search Tags:#architecture#quality assurance#code review#best practices#extension development#ui patterns#umbraco
One-click install
npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-review-checks-kraftvaerk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: umbraco-review-checks
Source: https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy/tree/main/Kraftvaerk.Umbraco.Alchemy.Frontend/.agents/skills/umbraco-review-checks
Command: npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-review-checks-kraftvaerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive checklist and reference for ensuring Umbraco backoffice extensions meet quality, architectural, and UI pattern standards, streamlining the review process.

Core Features & Use Cases

  • Code Quality Checks: Ensures adherence to Umbraco's coding standards and best practices.
  • Architecture Validation: Verifies that extensions follow established architectural patterns like the repository pattern and context API usage.
  • UI Pattern Compliance: Guides developers to use Umbraco UI (UUI) components and accessibility best practices.
  • Use Case: A developer is building a new dashboard for Umbraco and needs to ensure it's well-structured, maintainable, and follows Umbraco's guidelines before submitting it for review. They would use this skill to check against all relevant criteria.

Quick Start

Review the code-quality-checks.md file for details on code quality standards.

Frequently Asked Questions about umbraco-review-checks

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

FAQPage Schema
How do I validate Umbraco backoffice extensions against best practices?▼

To validate Umbraco backoffice extensions, check them against structured code quality, architectural, and UI pattern standards. This process verifies compliance with Umbraco development best practices using specific checks and severity levels.

What architectural patterns should Umbraco extension development follow?▼

Umbraco extension development should follow established architectural patterns like the repository pattern and context API usage. Validating architecture ensures your backoffice extensions meet structural standards for maintainability.

How do I ensure code quality when building an Umbraco dashboard?▼

Ensure code quality for an Umbraco dashboard by reviewing it against Umbraco's coding standards. A structured validation reference provides specific checks and auto-fix possibilities to guarantee your extension is well-structured before submission.

Do I need to use Umbraco UI components for backoffice extensions?▼

Yes, using Umbraco UI (UUI) components is required for UI pattern compliance. Validating your extension ensures adherence to UUI components and accessibility best practices within the Umbraco backoffice.

What is included in an Umbraco code review checklist?▼

An Umbraco code review checklist includes specific checks for code quality, architecture validation, and UI pattern compliance. It details severity levels and auto-fix possibilities to streamline the review process for backoffice extensions.

Related Skills

Explore More Software Engineering Skills→
kraftvaerkkraftvaerk

umbraco-testing

Route Umbraco backoffice extension testing to specialized skills by testing level.

Official
Intermediate
nthnclrknthnclrk
11

proposal-rfp-orchestrator

Coordinate proposal responses across owners, deadlines, and review gates.

Community
Advanced
kraftvaerkkraftvaerk

umbraco-backoffice

Create Umbraco backoffice extensions using UUI components and blueprints.

Official
Advanced
HenquewlHenquewl
7

requesting-code-review

Dispatch a subagent to review git-based changes across commit ranges.

Community
Intermediate