umbraco-validation-context

Implement Umbraco backoffice form validation with UmbValidationContext and JSON Path bindings.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-validation-context-1k-off
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: umbraco-validation-context
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/umbraco-validation-context
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-validation-context-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of implementing consistent, multi-field, multi-step form validation in the Umbraco backoffice without manually wiring error messages per input or per tab.

Core Features & Use Cases

  • Centralized validation state: Use UmbValidationContext to manage validation messages for complex form UIs (including workspace editors and multi-step forms).
  • JSON Path-based targeting: Attach validation bindings and messages using JSON Path (for example, $.form.tab1.email) to keep rules organized.
  • Reactive error counting: Observe validation message streams and compute error counts per tab/section to drive UI badges and navigation.
  • Client + server validation integration: Run client-side validation, then add server-side validation errors into the same context after API responses (and clear outdated server errors between attempts).

Quick Start

Ask an AI agent to implement a custom Umbraco backoffice form component that binds fields to UmbValidationContext using JSON Path and shows per-tab error badges.

Frequently Asked Questions about umbraco-validation-context

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

FAQPage Schema
How do I centralize form validation in the Umbraco backoffice?▼

Use UmbValidationContext to orchestrate validation across complex Umbraco backoffice UIs like multi-step forms. It binds validation to individual inputs reactively, eliminating the need to manually wire error messages for each field or tab.

What is the best way to show per-tab error badges in an Umbraco workspace editor?▼

Observe validation message streams with messagesOfPathAndDescendant to compute reactive error counts per section. This approach drives UI badge displays in Umbraco workspace editors by tracking JSON Path-targeted validation messages.

How do I bind server-side validation errors to an Umbraco client-side form?▼

Add server-side validation errors directly into the UmbValidationContext after an API response. This integrates them with client-side errors in the same context, allowing you to clear outdated server errors between submission attempts.

How does JSON Path targeting work for Umbraco backoffice validation rules?▼

JSON Path targeting attaches validation bindings and messages to specific paths like $.form.tab1.email. This structure keeps validation organized across multi-step forms and allows precise observation of descendant validation states.

Can I use umbBindToValidation for multi-step Umbraco form components?▼

Yes, umbBindToValidation supports multi-step Umbraco form components. It binds fields directly to the centralized UmbValidationContext, ensuring validation state is accurately tracked and observed reactively across all steps.

Why does my Umbraco validation context not clear old server errors on new submissions?▼

Ensure you actively remove outdated server-side validation messages from the UmbValidationContext between API response attempts. This maintains a clean validation state and prevents stale errors from persisting across new submissions.