with one click
arkcompiler_runtime_core
arkcompiler_runtime_core contains 13 collected skills from openharmony, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
PCRE2 library integration for RegExp implementation in ETS stdlib. Use when implementing regex features, adding new regex flags, optimizing pattern matching, debugging native regex code, or extending RegExp API. Covers PCRE2 C API, pattern compilation, match execution, capture groups, UTF-8/UTF-16 handling, and native-ETS boundary.
Comprehensive RegExp implementation covering both ETS managed API and native C++ bindings. Use when implementing, debugging, or extending RegExp functionality. Covers the full stack from ETS stdlib API through ANI bindings to PCRE2 backend.
Run ets_func_tests using the Universal Runner (urunner) tool. Use when executing stdlib tests, running test suites, or testing ETS functionality. Handles running tests with runner.sh from ../../../tests/tests-u-runner-2/, selecting workflows and test suites, configuring test options, and running specific tests or full test suites.
Work with Ark static_core AOT PGO flows using `.ap` profiles, runtime saver flags, `ark_aptool dump`, and `ark_aot --paoc-use-profile:path=...`. Use when collecting profile data, validating saved profiles, reusing them in AOT compilation, or debugging class-context mismatch and current AOT PGO limitations.
Reproduce Ark static_core failures through checked tests or URunner v1/v2. Use when narrowing CI regressions, capturing exact `checker.rb`, `ark`, or `ark_aot` commands, authoring `RUN` or `RUN_PAOC` style repros, or deciding whether a bug belongs in checked, URunner, or raw tool-level reproduction.
Triage Ark static_core compiler issues with IR dumps, disassembly, `ark_aot --paoc-mode=jit|osr|aot|llvm`, `ark_aotdump`, compiler logs, and method narrowing through `--compiler-regex`. Use when comparing pass-local behavior, verifying code generation, or deciding whether a failure is compiler-local or belongs to the runtime boundary.
Reproduce Ark static_core issues across interpreter, JIT, AOT, and offline paoc flows. Use when you need exact `ark` or `ark_aot` commands, explicit `--interpreter-type`, `--compiler-regex` minimization, current `--paoc-*` flags, or a fast choice between interpreter-only, force-JIT, runtime AOT, and offline paoc validation.
Investigate Ark static_core performance regressions with current benchmark layers, explicit runtime mode selection, GC control, IR and disassembly inspection, AOT symbol generation, and external profiler handoff. Use when comparing `int`, `jit`, and `aot`, running VMB or ETS micro-benchmarks, or preparing a clean profiling workflow.
Build the ArkTS stdlib project using CMake. Use when compiling the stdlib, building project from ../../../, running cmake configuration, or compiling with ninja. Handles CMake configuration from project root, Ninja compilation, build directory management, and clean rebuilds.
Generate ArkTest unit tests for stdlib APIs. Use when creating tests for ArkTS/ETS stdlib APIs, writing test cases, or generating test code. This skill handles the ArkTest framework including test suite creation with ArkTestsuite, test functions with assertions (assertEQ, assertTrue, expectError), proper main() returning suite.run(), async tests with addAsyncTest, and error handling tests. Places tests in ../tests/ets_func_tests/std/.
Update copyright years in changed source files according to Huawei code style
Important skill covering Unicode (UTF-8, UTF-16), ICU4C library, locale handling, collation, number/date formatting, and i18n APIs for ETS stdlib. Use this skill when: (1) Implementing i18n features, (2) Using ICU library, (3) Formatting for locales, (4) Handling Unicode text, (5) Supporting RTL languages, or (6) Designing locale-aware APIs.
Essential skill covering C++ programming, FFI (Foreign Function Interface), ANI (Ark Native Interface), ICU4C integration for internationalization, and native method implementation for ETS stdlib. Use this skill when: (1) Implementing native methods, (2) Integrating with C++ code, (3) Using ICU for i18n, (4) Handling native/ETS boundary, (5) Debugging native crashes, or (6) Optimizing native code.