page-transition-and-rendering-flow

What problem does it solve?

This skill provides a clear blueprint for the end-to-end data flow from server-side rendering to client navigation in GROWI, including how global state atoms are hydrated and kept in sync across navigations, to prevent hydration mismatches and render-time state updates.

Core Features & Use Cases

• Document the roles of the dynamic route entry, SSR props, hydration hooks, and global atoms, and describe safe hydration patterns that avoid writing to atoms during render.
• Provide use cases for when editing page transition logic or global atom synchronization, with a focus on maintaining invariant rendering across navigations.

Quick Start

Review and adopt the hydration-safe pattern for global atoms during route transitions.