What problem does it solve? Foldable HarmonyOS devices introduce layout and state challenges that standard responsive design cannot handle: hover-mode split screens, content falling into the crease region, orientation flapping, and lost scroll/input/playback state after folding or unfolding. This Skill provides a phase-based (REQ/DEV/FIX/VAL) workflow with scene routing to design, implement, fix, and verify fold-state adaptation correctly. ## Core Features & Use Cases - Scene-based routing: Four P0 scenes cover hover-mode split-screen and multi-form-factor mapping (FOLD-01), crease-region avoidance (FOLD-02), fold/unfold continuity for scroll, input, image, and video state (FOLD-03), and fold-related bug remediation (FOLD-04). - Concrete implementation guidance: References detail FoldStatus/foldDisplayMode detection via @ohos.display, FolderStack vs FoldSplitContainer selection, crease coordinate mapping with direction scoring, delayed orientation scheduling, and video continuity via snapshot-restore with onPrepared plus timer fallback. - Multi-form-factor support: Covers tri-fold F/M/G form mapping, inner/outer screen ratio differences (e.g. Pura X 1:1 outer screen), and small-square-screen immersive browsing. - Use Case: A video app shows a black screen in hover mode because the crease band was miscalculated. The skill routes to FOLD-04, applies the thickness-clamping and axis-detection fixes from the bug-fix case library, and defines the verification evidence required. ## Quick Start Ask the agent to adapt my HarmonyOS page for foldable hover mode with crease avoidance and continuous video playback across fold and unfold.