mobile-feature

Implement cross-platform mobile features with navigation, data, UI, and state management.

13|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill mobile-feature-heaptracetechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-feature
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/mobile/mobile-feature
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill mobile-feature-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build a unified mobile feature end-to-end that spans navigation scaffolding, data layer, UI, and state management, ensuring a native feel and consistent behavior across React Native, Flutter, and native Swift/SwiftUI implementations.

Core Features & Use Cases

  • Cross-platform feature scaffolding that covers navigation graphs, data models, UI composition, and state flow.
  • Platform-adaptive UI patterns that respect iOS and Android conventions while sharing business logic and data layers.
  • End-to-end lifecycle from planning to ship-ready polish, including offline support, testing, and release readiness.
  • Real-world use: implement a new screen or multi-screen flow that behaves identically on all target platforms.

Quick Start

Define the target platform and framework, map the feature scope to navigation and data layers, and implement the end-to-end feature across platforms.

Frequently Asked Questions about mobile-feature

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

FAQPage Schema
How do I build a cross-platform mobile feature with shared state management and native UI?

To build a cross-platform mobile feature, implement shared navigation scaffolding and data layers alongside platform-adaptive UI patterns. This ensures native feel and consistent behavior across React Native, Flutter, and native Swift/SwiftUI.

What is the best way to implement offline support for a new screen across iOS and Android?

Implementing offline support for cross-platform screens involves unifying the data layer and state flow across iOS and Android. Apply platform-adaptive UI patterns while sharing business logic to deliver release-ready functionality with consistent offline behavior.

Can I use this approach for both React Native and native SwiftUI implementations?

Yes, this approach supports React Native, Flutter, and native Swift/SwiftUI implementations. It maps feature scope to navigation graphs and data models, ensuring ship-ready polish and identical behavior across all target mobile platforms.

How do I scaffold end-to-end navigation and data layers for a multi-screen mobile flow?

Scaffolding end-to-end navigation and data layers requires mapping the feature scope to navigation graphs and state flow. This covers UI composition and data models to deliver a unified, ship-ready multi-screen flow across platforms.

Does cross-platform mobile feature development require separate state management for each platform?

No, cross-platform mobile feature development shares business logic and data layers across platforms. It applies platform-adaptive UI patterns that respect iOS and Android conventions while maintaining a unified state flow.