forestbook/telegramharmony
Overview
This skill is an expert assistant for developing HarmonyOS NEXT native applications using ArkTS and ArkUI. It produces high-quality, Huawei-compliant ArkTS code, covering UI, state management, animations, networking, persistence, multi-device adaptation, and performance tuning. Use it to get precise, production-ready patterns, components, and optimizations for API 12+ projects.
How this skill works
I inspect your feature requirements or existing code and generate ArkTS/ArkUI implementations that follow strict typing and HarmonyOS conventions. I recommend correct decorators (@State, @Prop, @Link, etc.), component templates, navigation and lifecycle hooks, plus performance patterns like LazyForEach and @Reusable. I can also produce network, storage, and animation snippets and explain trade-offs.
When to use it
- Starting a new HarmonyOS NEXT native app (ArkTS + ArkUI)
- Converting UI/UX designs into ArkTS components and layouts
- Implementing state management and cross-component data flow
- Optimizing long lists, animations, and runtime performance
- Adding multi-device/responsive and distributed capabilities
- Creating network, persistence, and lifecycle integrations
Best practices
- Always declare explicit types; avoid var and any to ensure compile-time safety
- Choose decorators by data flow: @Prop for one-way, @Link for two-way, @StorageLink for app-wide persistence
- Use LazyForEach + @Reusable for large lists and cachedCount() to reduce memory churn
- Prefer Navigation (NavPathStack) for complex routing and use shared geometryTransition for element transitions
- Keep layouts shallow (Row/Column first) and extract reusable styles with @Styles and @Builder
Example use cases
- Generate a responsive ArkTS entry page with Navigation and routing map
- Create a reusable card component with @Prop, @BuilderParam and style reuse
- Implement a paged list backed by an IDataSource using LazyForEach and @Reusable items
- Add a network fetch utility using http.createHttp plus typed response parsing
- Implement shared element transitions and a custom animateTo sequence for interactive UI
FAQ
Yes. Provide the component structure and interactions; I will map layout, state, and animations to ArkUI/ArkTS patterns and suggest equivalent decorators and lifecycle hooks.
How do you ensure performance on low-end devices?
I recommend lazy rendering (LazyForEach), reusable components, limiting binding depth, debouncing network/UI actions, and offloading heavy tasks to TaskPool/Worker. I can profile hotspots and propose targeted refactors.