arkts-skill

Name: arkts-skill
Availability: InStock
Author: shirulot

Guide ArkTS syntax, type semantics, and TypeScript migration strategies.

Updated Jul 6, 2026

Search Tags:#typescript #specification #migration #compiler #harmonyos #arkts

Ready to run

npx skills add https://github.com/shirulot/codex-skill --skill arkts-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arkts-skill
Source: https://github.com/shirulot/codex-skill/tree/main/arkts-agent-skill
Command: npx skills add https://github.com/shirulot/codex-skill --skill arkts-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, pandoc, rg, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves ambiguity in ArkTS syntax, type-system constraints, and migration challenges by providing direct, specification-backed answers to complex development questions.

Core Features & Use Cases

Spec-Backed Guidance: Provides precise answers based on the official ArkTS Specification 1.2.0.
Migration Support: Offers a local-first workflow for migrating TypeScript code to ArkTS, including handling of unsupported features like dynamic property indexing.
Error Resolution: Includes a field-tested playbook for fixing common compiler diagnostics like arkts-no-untyped-obj-literals and arkts-no-props-by-index.

Quick Start

Use the arkts-skill to analyze the provided code snippet and suggest the necessary refactoring to comply with ArkTS strict typing rules.

Frequently Asked Questions about arkts-skill

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

FAQPage Schema

How do I migrate TypeScript code to ArkTS for HarmonyOS development?▼

To migrate TypeScript code to ArkTS for HarmonyOS, you must adapt unsupported features like dynamic property indexing to comply with strict typing rules. This involves analyzing code snippets and refactoring them based on the official ArkTS specification.

Why does the ArkTS compiler throw arkts-no-untyped-obj-literals errors?▼

The ArkTS compiler throws arkts-no-untyped-obj-literals errors to enforce strict typing constraints and prevent ambiguity in object literals. You can resolve this diagnostic by applying specific architectural adaptations and explicitly typing your object structures.

What is the best way to resolve arkts-no-props-by-index compiler diagnostics in ArkTS?▼

The best way to resolve arkts-no-props-by-index diagnostics is to replace dynamic property indexing with spec-backed architectural patterns. This ensures deterministic code generation and full compliance with ArkTS type system semantics.

Does ArkTS support dynamic property indexing like standard TypeScript?▼

ArkTS does not support dynamic property indexing like standard TypeScript due to its strict type system constraints. You must refactor these unsupported features to ensure deterministic behavior and compliance with the ArkTS specification.

How do I fix dynamic property indexing errors when adapting TypeScript to ArkTS?▼

To fix dynamic property indexing errors when adapting TypeScript to ArkTS, you must refactor the dynamic accesses into strictly typed architectural patterns. This resolves the compiler diagnostics and aligns with ArkTS type system semantics.

What are the limitations of using TypeScript features in ArkTS specification 1.2.0?▼

Limitations of using TypeScript features in ArkTS specification 1.2.0 include the rejection of dynamic property indexing and untyped object literals. These constraints ensure deterministic execution but require architectural adaptation from standard TypeScript.