hmos-multidevice-scenario-entry

Classify and route HarmonyOS multi-device adaptation requests to technical scenario files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the complexity of navigating HarmonyOS multi-device adaptation by automatically classifying your request and routing it to the correct technical scenario, preventing fragmented or incorrect implementation strategies.

Core Features & Use Cases

  • Intelligent Routing: Analyzes whether your task involves layout, fold states, system area avoidance, or hardware access.
  • Phase-Aware Guidance: Provides specific technical constraints based on whether you are in the Requirement, Development, Fix, or Validation phase.
  • Use Case: If you are struggling with a layout that breaks specifically on a tri-fold device, this Skill identifies the intersection of fold-state and layout scenarios, guiding you to the precise documentation and implementation assets required.

Quick Start

Use the hmos-multidevice-scenario-entry skill to analyze the layout issues occurring on my foldable device during the development phase.

Frequently Asked Questions about hmos-multidevice-scenario-entry

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

FAQPage Schema
How do I handle HarmonyOS multi-device adaptation for responsive layouts?

HarmonyOS multi-device adaptation for responsive layouts is handled by classifying your request and routing it to validated technical scenario files. This ensures consistent layout implementation across different screen-window sizings and device constraints.

What is the best way to fix layout issues on a tri-fold HarmonyOS device?

Fixing layout issues on a tri-fold device requires identifying the intersection of fold-state and layout scenarios. The Skill routes your specific fold-state transition problem to precise reference documentation and asset-based implementation examples.

How do I avoid system areas when adapting a UI for foldable devices?

System area avoidance for foldable devices is managed by routing your adaptation request to specific technical constraints based on your current development phase. This directs you to validated reference documentation for consistent implementation.

Does HarmonyOS multi-device adaptation guidance change based on the development phase?

HarmonyOS multi-device adaptation guidance is phase-aware, providing specific technical constraints whether you are in the Requirement, Development, Fix, or Validation phase. This ensures correct technical implementation strategies throughout your workflow.

Why does my HarmonyOS hardware capability check fail across different devices?

Hardware capability differences across HarmonyOS devices require routing your adaptation request to specific technical scenario files. This prevents fragmented implementation by directing you to validated reference documentation for hardware access constraints.

Can I use this routing entry for all HarmonyOS multi-device screen-window sizing scenarios?

You can use this routing entry for HarmonyOS multi-device screen-window sizing scenarios, as it analyzes whether your task involves layout, fold states, system area avoidance, or hardware access. It ensures consistent technical implementation by directing you to validated assets.