How do I install the Openharmony Cpp skill?

Run npx skillmds@latest add openharmonyinsight/openharmony-cpp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openharmony Cpp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openharmony Cpp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openharmony Cpp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openharmony Cpp?

openharmonyinsight (@openharmonyinsight) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openharmony Cpp by openharmonyinsight

Name: Openharmony Cpp
Author: openharmonyinsight

Openharmony Cpp

Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).

openharmonyinsight 8fa5555 5 files · 6.4 KB Updated Sep 17, 2026

File contents

OpenHarmony C++ Coding Skills

Core Mandates (Common Pitfalls)

These rules are strictly enforced in OpenHarmony and often differ from general C++ projects.

1. Strict Naming & Formatting

Extensions: Always use .cpp and .h.
Files: Filenames must match class names (Unix-like, e.g., my_class.cpp).
Variables: Global vars must start with g_ (e.g., g_config). Class members must end with _ (e.g., value_).
Braces: K&R Style is mandatory (opening brace on the same line).
Details: See naming_formatting.md.

2. Header Management

Guards: Use #ifndef guards. #pragma once is FORBIDDEN.
Includes: Prefer #include over forward declarations to prevent hidden dependencies.
Details: See headers_scopes.md.

3. Critical Security Requirements

Input Validation: All external data must be validated before use (indices, sizes, loops).
Memory Safety: Pointers must be set to nullptr immediately after deletion.
Bitwise: Only on unsigned types.
Details: See secure_coding.md.

Usage Guide

When to use

New Code: Generating new classes or modules.
Refactoring: Cleaning up legacy code.
Review: Checking code against OpenHarmony standards.

Reference Map

naming_formatting.md: Naming conventions (g_, _), braces (K&R), line length.
secure_coding.md: Input validation, integer safety, memory management, prohibited functions.
class_function_design.md: Constructors, inheritance, modern C++ (nullptr, const), function size.
headers_scopes.md: Header guards, namespaces, include rules.

---name: openharmony-cppdescription: Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).---# OpenHarmony C++ Coding Skills## Core Mandates (Common Pitfalls)These rules are strictly enforced in OpenHarmony and often differ from general C++ projects.### 1. Strict Naming & Formatting- **Extensions:** Always use `.cpp` and `.h`.- **Files:** Filenames **must** match class names (Unix-like, e.g., `my_class.cpp`).- **Variables:** Global vars must start with `g_` (e.g., `g_config`). Class members must end with `_` (e.g., `value_`).- **Braces:** **K&R Style** is mandatory (opening brace on the same line).- **Details:** See [naming_formatting.md](references/naming_formatting.md).### 2. Header Management- **Guards:** Use `#ifndef` guards. **#pragma once is FORBIDDEN.**- **Includes:** Prefer `#include` over forward declarations to prevent hidden dependencies.- **Details:** See [headers_scopes.md](references/headers_scopes.md).### 3. Critical Security Requirements- **Input Validation:** All external data must be validated before use (indices, sizes, loops).- **Memory Safety:** Pointers must be set to `nullptr` **immediately** after deletion.- **Bitwise:** Only on **unsigned** types.- **Details:** See [secure_coding.md](references/secure_coding.md).## Usage Guide### When to use- **New Code:** Generating new classes or modules.- **Refactoring:** Cleaning up legacy code.- **Review:** Checking code against OpenHarmony standards.### Reference Map- **[naming_formatting.md](references/naming_formatting.md)**: Naming conventions (g_, _), braces (K&R), line length.- **[secure_coding.md](references/secure_coding.md)**: Input validation, integer safety, memory management, prohibited functions.- **[class_function_design.md](references/class_function_design.md)**: Constructors, inheritance, modern C++ (nullptr, const), function size.- **[headers_scopes.md](references/headers_scopes.md)**: Header guards, namespaces, include rules.

Frequently asked questions