What problem does it solve? HarmonyOS apps behave inconsistently across phones, foldables, tablets, and PCs because each device form factor has a different natural orientation and rotation capability. This Skill guides requirement analysis, implementation, bug fixing, and verification for screen orientation and rotation, covering setPreferredOrientation, module.json5 orientation config, foldable G-state, and video landscape switching. ## Core Features & Use Cases - Scenario Routing: Four decision-tree scenes (ORIENT-01 to ORIENT-04) covering rotation detection, multi-device adaptation strategy, video landscape switching, and orientation bug fixing. - Bug Fix Case Library: Nine real-world cases including foldable forced-portrait from deviceType misjudgment, Tabs/Swiper lifecycle traps, split-screen rotation failure, and XComponent camera preview black screens. - Reference Guides: Concept quick-reference for the 18 rotation strategies, multi-device adaptation with breakpoint APIs, sensor-based rotation detection, and video rotation with the adaptive_video library. - Use Case: When a foldable device in expanded landscape mode gets forced to portrait on entering a page, the Skill routes to the bug-fix scene, identifies the deviceInfo.deviceType === 'phone' misjudgment, and provides the display.isFoldable() based fix. ## Quick Start Ask the assistant to diagnose why my HarmonyOS app is forced to portrait on a foldable device in expanded landscape mode and provide a fix.