What problem does it solve? HarmonyOS multi-device adaptation spans many distinct problem domains—responsive layouts, fold states, safe-area avoidance, input methods, orientation semantics, and hardware capabilities—and developers often don't know which specialized guidance applies to their issue. This Skill acts as the entry router: it classifies a request by development phase (REQ/DEV/FIX/VAL) and scenario type, then directs the agent to the correct scenario skill files instead of guessing at implementation details. ## Core Features & Use Cases - Phase and scenario classification: Maps user requests to active phases (requirement analysis, development, bug fixing, validation) and to one primary plus up to two secondary scenarios (SCENE-01 through SCENE-07). - Structured routing output: Produces stable fields such as primary_scene, secondary_scenes, route_reason, and next_scene_refs so downstream scenario skills can take over with clear handoff context. - On-demand remote skill loading: Uses scripts/remote_load.sh to download and cache whitelisted scenario skills from the Matrix registry when the target scenario file is missing locally. - Use Case: A developer reports that a foldable video detail page breaks in hover mode, the keyboard hides the comment input, and rotation desynchronizes the layout. The Skill routes this composite problem to the fold-state, avoid-areas, and screen-window-size scenario skills with a defined handoff order. ## Quick Start Ask the agent to classify your HarmonyOS multi-device adaptation problem, for example: "My foldable app's layout breaks in hover mode and the keyboard covers my input field—which adaptation scenarios should handle this?"
