hmos-multidevice-fold-state

Validate and route HarmonyOS foldable-device adaptation tasks through a declarative scene and resource index.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/shirulot/codex-skill --skill hmos-multidevice-fold-state-shirulot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmos-multidevice-fold-state
Source: https://github.com/shirulot/codex-skill/tree/main/hmos-multidevice-fold-state
Command: npx skills add https://github.com/shirulot/codex-skill --skill hmos-multidevice-fold-state-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the fragmentation in foldable device adaptation by providing a unified, declarative framework for handling complex foldable states, crease avoidance, and cross-state continuity.

Core Features & Use Cases

  • State-Aware Routing: Automatically routes tasks based on FoldStatus, display modes, and device form factors (F/M/G).
  • Crease & Layout Management: Implements precise crease avoidance and hover-state interaction (e.g., upper-display/lower-control) using official UX standards.
  • Use Case: When developing a video player for a foldable device, use this Skill to ensure the video remains in the upper screen during hover mode, the controls are safely placed in the lower screen, and playback continuity is maintained during folding/unfolding.

Quick Start

Use the hmos-multidevice-fold-state skill to analyze the current foldable device layout and apply the official crease avoidance and hover-state interaction patterns to the video player component.

Frequently Asked Questions about hmos-multidevice-fold-state

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

FAQPage Schema
How do I handle HarmonyOS foldable device adaptation for crease avoidance and hover states?

HarmonyOS foldable device adaptation is handled through a declarative scene and resource index that validates and routes tasks involving crease avoidance, hover layouts, and FoldStatus mapping to ensure consistent UX constraints across device form factors.

What is the best way to maintain video playback continuity during folding and unfolding on HarmonyOS?

Video playback continuity during folding and unfolding is maintained by applying official hover-state interaction patterns, keeping the video in the upper screen and controls in the lower screen during hover mode through state-aware task routing.

How does state-aware routing work for foldable device form factors in HarmonyOS?

State-aware routing automatically directs foldable adaptation tasks based on FoldStatus, display modes, and device form factors like F, M, and G to apply precise crease avoidance and layout management constraints.

Can I use this to standardize multi-fold state mapping and capability boundaries across different devices?

Multi-fold state mapping and capability boundaries are standardized by validating device-specific constraints and verification matrices through a declarative framework, ensuring consistent behavior across all foldable form factors.

When do I need to implement crease avoidance patterns for HarmonyOS foldable applications?

Crease avoidance patterns are needed when developing applications for foldable devices requiring hover-state interactions, such as upper-display and lower-control layouts, to prevent UI elements from being obscured by the physical screen crease.

Why does my foldable device layout break when transitioning between hover and fully unfolded states?

Foldable device layouts break during state transitions when cross-state continuity and official UX standards for crease avoidance are not applied, which this framework resolves by routing tasks through a declarative scene and resource index.