harmony-hdc
HarmonyOS device control and UI automation via raw HDC commands. Use for device/emulator discovery, USB or TCP connection, app launch/force-stop, tap/swipe/keyevent/text input, screenshots, UI dump, file transfer, and HDC troubleshooting.
What this skill does
# Harmony HDC Reference for controlling HarmonyOS devices with raw `hdc` commands. ## Execution Constraints - Use `hdc -t <device_id>` whenever more than one device is connected. - Confirm screen resolution before coordinate actions: `hdc -t DEVICE shell wm size`. - Ask for missing required inputs before executing (device id, bundle/ability, coordinates, file paths). - Surface actionable stderr on failure (authorization, cable/network, tcp mode). ## Device And Server ```bash # Start HDC server hdc start # Stop HDC server hdc kill # List targets hdc list targets # Target a specific device hdc -t DEVICE <command> ``` ## Connection ```bash # Connect over TCP hdc tconn <ip>:<port> # Disconnect target hdc -t DEVICE tdis ``` ## Device State ```bash # Device model/system info hdc -t DEVICE shell param get const.product.model hdc -t DEVICE shell param get const.ohos.fullname # Screen size hdc -t DEVICE shell wm size # Foreground focus window hdc -t DEVICE shell hidumper -s WindowManagerService -a '-a' # Run raw shell command hdc -t DEVICE shell <command> ``` ## App Lifecycle ```bash # List installed bundles hdc -t DEVICE shell bm dump -a # Start an ability hdc -t DEVICE shell aa start -a <ability_name> -b <bundle_name> # Start by URI hdc -t DEVICE shell aa start -U <uri> # Force-stop app by bundle hdc -t DEVICE shell aa force-stop <bundle_name> ``` ## Input Actions ```bash # Tap hdc -t DEVICE shell uitest uiInput click X Y # Double tap hdc -t DEVICE shell uitest uiInput click X Y && sleep 0.1 && hdc -t DEVICE shell uitest uiInput click X Y # Long press hdc -t DEVICE shell uitest uiInput longClick X Y # Swipe hdc -t DEVICE shell uitest uiInput swipe X1 Y1 X2 Y2 [duration_ms] # Key event hdc -t DEVICE shell uitest uiInput keyEvent Back hdc -t DEVICE shell uitest uiInput keyEvent Home hdc -t DEVICE shell uitest uiInput keyEvent Enter ``` ## Text Input ```bash # Text input (Harmony text input supports UTF-8) hdc -t DEVICE shell uitest uiInput inputText "hello world" ``` ## Screenshot And UI Dump ```bash # Capture screenshot on device hdc -t DEVICE shell snapshot_display -f /data/local/tmp/screen.jpeg # Pull screenshot to local hdc -t DEVICE file recv /data/local/tmp/screen.jpeg ./screen.jpeg # Dump UI tree (JSON) hdc -t DEVICE shell uitest dumpLayout -p /data/local/tmp/layout.json hdc -t DEVICE file recv /data/local/tmp/layout.json ./layout.json ``` ## File Transfer ```bash # Push file to device hdc -t DEVICE file send ./local.file /data/local/tmp/remote.file # Pull file from device hdc -t DEVICE file recv /data/local/tmp/remote.file ./remote.file ``` ## App Install And Uninstall ```bash # Install HAP hdc -t DEVICE install /path/to/app.hap # Install with replace hdc -t DEVICE install -r /path/to/app.hap # Uninstall by bundle hdc -t DEVICE uninstall <bundle_name> ``` ## Common KeyEvents | KeyEvent | Description | |---------|-------------| | `Back` | Back button | | `Home` | Home button | | `Enter` | Enter/confirm | | `Power` | Power button | | `VolumeUp` | Volume up | | `VolumeDown` | Volume down |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.