workflow-editor-three-plane-architecture

Architect workflow-editor tooling for Umbraco Prism with three-plane separation.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-editor-three-plane-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-editor-three-plane-architecture
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.squad/skills/workflow-editor-three-plane-architecture
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-editor-three-plane-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the architectural challenge of building workflow editors that risk becoming tightly coupled to runtime execution, ensuring the editor remains a flexible authoring tool rather than a rigid runtime authority.

Core Features & Use Cases

  • Three-Plane Separation: Clearly distinguishes between authoring, projection, and agent planes to maintain system modularity.
  • Projection-Based Design: Ensures workflow JSON is treated as a projection target, allowing for deterministic generation and validation.
  • Use Case: Use this framework when designing a new visual workflow editor for Umbraco Prism to ensure that business logic, UI shells, and state progression remain decoupled and maintainable.

Quick Start

Apply the three-plane architecture pattern to the current workflow editor design by mapping the authoring model to the projection target.

Frequently Asked Questions about workflow-editor-three-plane-architecture

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

FAQPage Schema
What is three-plane architecture in workflow editor design?

Three-plane architecture is a design pattern that strictly separates authoring, projection, and agent planes to maintain system modularity. It ensures workflow editors remain flexible authoring tools rather than rigid runtime authorities.

How do I decouple Umbraco Prism workflow editors from runtime execution?

To decouple Umbraco Prism workflow editors from runtime execution, enforce a strict separation between authoring and projection planes. This ensures editors generate projection-ready JSON without assuming runtime authority.

Can I use projection-based design to generate workflow JSON for Umbraco content?

Yes, you can use projection-based design to generate workflow JSON for Umbraco content. This approach treats workflow JSON as a projection target, allowing for deterministic generation while adhering to Umbraco content ownership rules.

When should I use a three-plane separation pattern for scalable workflows?

Use a three-plane separation pattern when designing a new visual workflow editor for Umbraco Prism to ensure business logic, UI shells, and state progression remain decoupled and maintainable.

Why does my workflow editor become tightly coupled to runtime authority?

Workflow editors become tightly coupled to runtime authority when they fail to separate authoring and projection planes. Treating the editor as a flexible authoring tool that generates projection-ready JSON prevents this rigidity.