oh-interfaces-ipc-to-service

Implement graphic_2d ToService IPC interfaces with proxy/stub handling and authorization.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-interfaces-ipc-to-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-interfaces-ipc-to-service
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/oh-interfaces-ipc-to-service
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-interfaces-ipc-to-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you extend the OpenHarmony graphic_2d IPC interface layer by adding a new ToService transparent channel from the Client side to the Service side, so your new rs_interfaces API can be wired through the full C/S + IPC + authorization chain.

Core Features & Use Cases

  • Client-to-Service IPC wiring: Adds corresponding declarations and proxy/stub IPC handling to carry your interface parameters and return values across processes.
  • End-to-end ToService path: Connects the request flow from the Client entry to rs_screen (Service implementation layer) using the expected call-chain patterns.
  • Auth integration: Updates IPC interface codes and enforces either @System or @Foundation authorization in the access verifier path.
  • Use Case: You need to add a new RSInterface in graphic_2d that is marked as ToService; use this Skill to generate the required plumbing up through IPC and rs_screen so the underlying hardware-specific behavior can be implemented later.

Quick Start

Ask the AI to add a new graphic_2d RSInterface ToService C++ API by providing the exact interface declaration and choosing whether it uses @System or @Foundation authentication.

Frequently Asked Questions about oh-interfaces-ipc-to-service

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

FAQPage Schema
How do I add a new OpenHarmony graphic_2d IPC interface from client to service?

You add a new ToService transparent channel end-to-end by implementing proxy/stub handling to carry parameters across processes and connecting the Client request flow to the rs_screen Service implementation layer.

What is a ToService pass in OpenHarmony graphic_2d IPC?

A ToService pass in OpenHarmony graphic_2d IPC is a transparent channel that transports a new RSInterface from the Client side to the Service side, ensuring requests reach the underlying implementation layer and return results correctly.

How do I enforce @System or @Foundation authorization for a new IPC interface in OpenHarmony?

You enforce authorization for a new IPC interface by updating IPC interface codes, adding descriptor checks, and routing the access verifier path to validate System or Foundation permissions.

Does the graphic_2d ToService IPC wiring support C++17?

Yes, the graphic_2d ToService IPC wiring supports C++17 by ensuring C++17-compatible naming and structure throughout the proxy/stub declarations and rs_screen call chain modifications.

When do I need to update proxy stub handling for an rs_interfaces API?

You update proxy stub handling for an rs_interfaces API when adding a new RSInterface marked as ToService, requiring IPC interface codes and declarations to carry parameters and return values across processes.