oh-pdd-code-generator

Generate OpenHarmony service code frameworks from PDD design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns design documents (PDD) into OpenHarmony system service code quickly, while keeping generated code consistent with existing repository structure, naming, and architecture.

Core Features & Use Cases

  • Design-to-code framework generation: Create directory layout, IDL interfaces, header/source templates, and service scaffolding.
  • OpenHarmony-style compliance: Analyze existing OpenHarmony modules to match coding style, conventions, and architecture patterns before generation.
  • Build configuration generation: Generate BUILD.gn (including module and deps wiring) plus SA profile related config artifacts (e.g., SA JSON and init config).

Typical uses include: generating a new service module from a functional design document, producing IDL interface definitions for IPC/kit integration, and scaffolding a complete bundle/SA/build setup ready for compilation.

Quick Start

Provide the functional design document path, then ask the assistant to generate a complete OpenHarmony service module for your target module name.

Frequently Asked Questions about oh-pdd-code-generator

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

FAQPage Schema
How do I generate OpenHarmony system service code from a design document?

Generating OpenHarmony system service code from a design document requires providing the PDD file path, after which the tool scaffolds the directory layout, IDL interfaces, C/C++ templates, and build configuration.

What is included in OpenHarmony project scaffolding for system services?

OpenHarmony project scaffolding for system services includes the folder structure, IDL interface files, C/C++ header and source templates, BUILD.gn wiring, and SA profile related configuration artifacts like bundle.json.

Can I generate IDL interfaces and BUILD.gn files automatically for OpenHarmony modules?

Yes, you can generate IDL interfaces and BUILD.gn files automatically for OpenHarmony modules by analyzing existing codebases to learn naming conventions and then producing compliant build configuration artifacts.

Does the generated OpenHarmony service code match existing repository architecture?

Yes, the generated OpenHarmony service code matches existing repository architecture by analyzing your current OpenHarmony modules to learn naming conventions, coding style, and architecture patterns before generating compliant outputs.

How do I overwrite existing files when scaffolding OpenHarmony module structure?

To overwrite existing files when scaffolding OpenHarmony module structure, use the force overwrite option during generation, which replaces current directory layouts and service templates with the newly generated code frameworks.