kata-mobile-implement

Implement mobile features with offline-first behavior and iOS/Android parity.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-mobile-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-mobile-implement
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-mobile-implement
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-mobile-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams implement a new mobile feature that behaves correctly when users are offline, remains consistent across iOS and Android, and meets accessibility, testing, and observability expectations.

Core Features & Use Cases

  • Offline-first behavior: Defines per-action behavior for online, cached/TTL reads, optimistic creation/editing, and explicit handling for destructive actions without network.
  • Layered implementation: Implements feature logic using a service + hook/viewmodel + screen + reusable components separation aligned to the mobile architecture patterns.
  • Quality gates: Adds accessibility coverage (VoiceOver and TalkBack), unit/component/integration/E2E tests with acceptance criteria traceability, and telemetry for crashes, analytics, and performance.

Quick Start

Use the kata-mobile-implement workflow to plan offline behavior, implement the feature layers, add accessibility and tests, then run iOS and Android smoke builds and produce parity-focused release notes.

Frequently Asked Questions about kata-mobile-implement

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

FAQPage Schema
How do I implement offline-first mobile features with iOS and Android parity?

Offline-first mobile feature implementation with iOS and Android parity is achieved by defining per-action behavior for online, cached/TTL reads, and optimistic creation, while explicitly handling destructive actions without a network connection.

How do I handle destructive actions in an offline-first mobile app when the network is unavailable?

Destructive actions in an offline-first mobile app require explicit handling when the network is unavailable, ensuring that service contracts and local queues prevent unintended data loss until connectivity is restored.

What is the best way to structure mobile feature logic for accessibility and E2E testing?

Structuring mobile feature logic for accessibility and E2E testing involves a layered separation using service, viewmodel, screen, and reusable components, enabling acceptance criteria traceability across unit, component, integration, and E2E tests.

Does this mobile implementation approach include telemetry for crashes and performance?

This mobile implementation approach includes telemetry instrumentation for crashes, analytics, and performance monitoring, ensuring release parities are validated through comprehensive parity checklists and smoke builds.

How do I validate VoiceOver and TalkBack accessibility in a new mobile screen flow?

VoiceOver and TalkBack accessibility validation in new mobile screen flows is handled through dedicated accessibility coverage gates, ensuring user-facing accessibility meets requirements across both iOS and Android platforms.