frontend-workflow-ui

Build React and TypeScript workflow UI with query hooks, view-models, and browser verification.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill frontend-workflow-ui-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-workflow-ui
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/frontend-workflow-ui
Command: npx skills add https://github.com/vovanostm-public/multica --skill frontend-workflow-ui-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building workflow user interfaces often leads to tangled server state, inconsistent module boundaries, and unverified browser behavior. This Skill provides a structured procedure for implementing React/TypeScript workflow UI that keeps API logic in core hooks, views as presentation plus view-models, and every user-visible flow covered by tests. ## Core Features & Use Cases - Structured UI Architecture: Separates process, studio, operations, and admin UI modules while routing server state through TanStack Query core hooks and derived state through view-models. - Semantic Workflow Rendering: Renders blockers, artifacts, questions, and next safe actions semantically, with raw JSON fallback for artifacts and critical/optional question splitting. - Verification & Quality Gates: Enforces RTL/unit tests, Playwright browser scenarios, accessibility via native controls, and typed evidence outputs with blockers and confidence. - Use Case: When adding an issue detail page with an operator cockpit to a workflow product, use this Skill to wire query hooks, build the process view, render artifacts and questions, and produce a browser verification plan. ## Quick Start Use the frontend-workflow-ui skill to implement the issue detail process cockpit with artifacts, questions, and a Playwright verification scenario.

Frequently Asked Questions about frontend-workflow-ui

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

FAQPage Schema
How do I structure React workflow UI with TanStack Query?▼

Put all API and query logic in core hooks using TanStack Query, and keep views as pure presentation plus view-models. Derived UI state belongs in the view-model layer, never duplicated into client stores like Zustand.

How to test workflow UI with Playwright and React Testing Library?▼

Write RTL unit tests for components and view-models, then add a Playwright scenario covering each user-visible flow such as the issue page process cockpit. Every UI change should ship with a browser verification plan.

Should workflow server state go in Zustand or TanStack Query?▼

Server state belongs in TanStack Query accessed through core hooks, not Zustand. Zustand or similar client stores should only hold genuinely client-side state, and duplicating server state there is an explicit quality gate violation.

How do I render workflow artifacts and questions accessibly?▼

Render artifacts with semantic renderers and a raw JSON fallback, and split questions into critical, optional, and answered groups. Prefer native HTML controls with labelled actions rather than custom widgets when accessibility is unclear.

What are the boundaries of this frontend workflow approach?▼

It does not perform unrelated workflow stages, overwrite evidence owned by other stages, or execute privileged actions directly. Privileged operations must go through the approved action pipeline, and writes stay within the assigned worktree.