Guide ArkTS syntax, type semantics, and TypeScript migration strategies.
npx skills add https://github.com/shirulot/codex-skill --skill arkts-skill
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
This skill resolves ambiguity in ArkTS syntax, type-system constraints, and migration challenges by providing direct, specification-backed answers to complex development questions.
Use the arkts-skill to analyze the provided code snippet and suggest the necessary refactoring to comply with ArkTS strict typing rules.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
thucpruGuide Claude Code installation, configuration, and troubleshooting.
SummerKazeConvert unsafe TypeScript patterns into compileable ArkTS code for .ets files.
openharmonyinsightAnswer ArkTS static-semantics and TypeScript migration questions from official documentation.
spearwolfProvide a zero-dependency synchronous event emitter API for JavaScript and TypeScript objects.
