skills.rest
jonnymuir
jonnymuirCOMMUNITY
Explore all skills by this author →
Website𝕏@jonnymooGitHub

workflow-mixed-content-regression

Identify regressions where explanatory content is misidentified as interactive form fields.

1|Updated Dec 23, 2025
Search Tags:#workflow#testing#validation#forms#regression#umbraco
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-mixed-content-regression
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-mixed-content-regression
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/workflow-mixed-content-regression
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-mixed-content-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents regressions where explanatory copy in workflow forms is incorrectly treated as fillable input fields by the engine.

Core Features & Use Cases

  • Boundary Inference Testing: Ensures the engine correctly distinguishes between structural shells and content-only fields.
  • Semantic Validation: Verifies that non-input elements like inset-text or warnings do not emit form controls or trigger validation errors.
  • Use Case: Use this when modifying form rendering logic to ensure that adding explanatory text to a page does not break existing form validation or field mapping.

Quick Start

Run the workflow mixed content regression test suite against the current core engine build to verify form field integrity.

Frequently Asked Questions about workflow-mixed-content-regression

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

FAQPage Schema
Why does explanatory text in workflow forms trigger validation errors?▼

Explanatory text triggers validation errors when the workflow engine misidentifies non-input elements like inset-text or warnings as fillable input fields. Semantic validation ensures structural content-only fields do not emit form controls or interfere with field mapping.

How do I test form rendering logic for mixed-content regressions?▼

Run a boundary inference test suite against your engine build to verify field metadata and component-to-input mapping. This testing verifies the engine correctly distinguishes between structural shells and content-only fields.

Does this regression testing work with GDS-compliant form components?▼

This regression testing is designed for GDS-compliant form components. It verifies field metadata and error wiring within the workflow engine to ensure server-side validation logic functions correctly during form rendering modifications.

What is the best way to prevent regressions when adding warnings to workflow forms?▼

The best way to prevent regressions is applying semantic validation to verify warnings and inset-text do not emit form controls. This ensures adding explanatory copy does not break existing form validation or field mapping.

Can I verify field metadata and error wiring without breaking existing form validation?▼

Yes, you can verify field metadata and error wiring by testing component-to-input mapping within the workflow engine. This process prevents regressions by ensuring structural shells are correctly distinguished from interactive input fields.

Related Skills

Explore More Software Engineering Skills→
jasonku09jasonku09
10

start-project

Interview users to define project scope, MVP, and core components.

Community
Intermediate
abdallhMoukdadabdallhMoukdad

flutter-bloc-forms

Model Flutter form inputs as Formz value objects orchestrated by a Bloc.

Community
Advanced
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
serverpodserverpod
8

shadcn_ui-checkbox

Integrate ShadCheckbox and ShadCheckboxFormField into Flutter forms.

Official
Basic