workflow-authoring-live-seed-contract

Validate authored workflow seed JSON against backend publish logic and editor shell requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents runtime failures in the MockBusinessApp by ensuring that live authored workflow seed files remain synchronized with backend projection logic and editor shell requirements.

Core Features & Use Cases

  • Contract Validation: Verifies the three-way integrity between backend publish tests, the live authoring API, and the editor shell.
  • Drift Detection: Identifies when authored JSON seeds become empty or schema-invalid, preventing 500 errors during workflow loading.
  • Use Case: When updating the workflow-editor or publish-pipeline, use this Skill to verify that the planning workflow seed remains compatible with the live authoring API and the editor's host lookup keys.

Quick Start

Use the workflow-authoring-live-seed-contract skill to audit the current authored workflow seeds against the latest backend projection schema.

Frequently Asked Questions about workflow-authoring-live-seed-contract

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

FAQPage Schema
How do I validate JSON workflow seeds against a backend publish schema?

Drift detection identifies when authored JSON seeds become empty or schema-invalid, preventing 500 errors during workflow loading in the MockBusinessApp by verifying three-way contract integrity.

How do I prevent 500 errors when loading Umbraco Prism workflow seeds?

When updating the workflow-editor or publish-pipeline, you audit the current authored workflow seeds against the latest backend projection schema to verify compatibility with the live authoring API.

What causes schema drift in authored workflow JSON files?

Yes, you can verify editor host lookup keys by auditing workflow seeds against the backend projection schema to maintain consistent three-way integrity between publish tests, the live API, and the editor shell.

Does the MockBusinessApp API require synchronized JSON seed files for testing?

To validate JSON workflow seeds, check authored files against backend publish logic and editor shell requirements to ensure schema validity and synchronized host lookup keys across the publishing lifecycle.

How do I audit authored workflow seeds against a live authoring API?

Drift detection identifies when authored JSON seeds become empty or schema-invalid, preventing 500 errors during workflow loading in the MockBusinessApp by verifying three-way contract integrity.