frontend-state-and-form-management

Frontend State and Form Management

Purpose

Implement the approved state ownership model and form behaviour. Runs ONLY when a Transactional/Hybrid component genuinely needs forms or shared cross-component state. A read-only transactional card does not need this skill.

⚠️ This skill embeds the project's complete state management guideline. No external lookup required.

⚠️ WRITE FILES, NOT DESCRIPTIONS

The PRIMARY deliverable is actual .ts/.tsx source files written to disk at the exact paths specified.

1. Server-First Philosophy

The frontend follows a server-first, distributed state management approach aligned with Next.js and Sitecore's server-driven rendering model. The objective is to minimise client-side state, keep components self-contained, and maintain clear separation between server-rendered content, local UI state, and shared application state.