VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:mobile-development

iOS, Android, and cross-platform apps

Build iOS, Android, and cross-platform mobile apps with mobile-first UX, performance budgets, offline sync, security, testing, and store deployment.

01

Define target

02

Choose framework

03

Set budgets

04

Design architecture

Rule 01

Performance is foundation, not a feature

Rule 02

Offline-first by default because mobile networks fail

Rule 03

Respect platform conventions without over-locking the product

Rule 04

Security and accessibility must be designed in from the start

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Define target Clarify iOS, Android, cross-platform, feature scope, store target, offline needs, and performance constraints.
  2. 2 Choose framework Pick React Native, Flutter, Swift/SwiftUI, or Kotlin/Compose based on team skills, performance, platform reach, and UI needs.
02

Work

Agent / skill execution

  1. 3 Set budgets Use mobile budgets for launch time, memory, network, battery, frame rate, app size, and screen load.
  2. 4 Design architecture Choose MVVM or Clean Architecture, state management, navigation, API layer, persistence, logging, and error handling.
03

Verify

Gate, review, validation

  1. 5 Build mobile UX Respect iOS HIG or Material Design 3, safe areas, gestures, dark mode, localization, animations, and accessibility.
  2. 6 Implement core features Add auth, persistence, API integration, offline sync, push notifications, deep links, analytics, and secure storage.
04

Close

Report, handoff, artifact

  1. 7 Test and profile Run unit, integration, E2E, accessibility, security, and performance checks on real devices.
  2. 8 Release safely Prepare icons, screenshots, privacy policy, CI/CD, Fastlane, internal testing, staged rollouts, and monitoring.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:mobile-development [platform] [feature]

Arguments

[platform]

Mobile stack

Primary stack such as react-native, flutter, ios, or android. Include framework, SDK or build-tool version, minimum OS, device classes, native modules, and store channel when known; the Skill does not assume device or signing access.

/ak:mobile-development "react-native Add an offline-capable saved-articles screen"
[feature] Required

Mobile outcome

Natural-language mobile feature, debugging, performance, security, or release-readiness request. Include supported OS/device matrix, network behavior, state contract, data and security boundaries, allowed mutations, tests, and release limits.

/ak:mobile-development "flutter Build offline-first inspection sync; test low connectivity; do not sign, upload, or release"

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Platform decision Recommended 
/ak:mobile-development iOS and Android field service app
Use when:
Use when choosing native versus cross-platform for an iOS or Android app.
Expected:
Compares React Native, Flutter, SwiftUI, and Kotlin/Compose against team skills, performance needs, offline constraints, and release targets before recommending a path.
Offline sync 
/ak:mobile-development React Native offline-first inspection sync
Use when:
Use for unreliable-network workflows that need persistence and conflict handling.
Expected:
Designs an offline-first architecture with local persistence, hybrid push/pull sync, API boundaries, error handling, and conflict guidance for the target mobile stack.
Performance and security 
/ak:mobile-development Flutter app performance and mobile security review
Use when:
Use when optimizing mobile constraints or hardening auth and sensitive data handling.
Expected:
Applies launch, memory, network, battery, frame-rate, and app-size budgets alongside OWASP Mobile checks for secure storage, credentials, sessions, and transport security.
Store rollout 
/ak:mobile-development Android and iOS staged rollout plan
Use when:
Use before TestFlight, internal testing, Google Play, App Store, or production rollout.
Expected:
Produces a release path covering store assets, privacy policy, Fastlane or CI/CD automation, real-device testing, staged rollout phases, and post-release monitoring.

Handled Scope

  • React Native and Expo
  • Flutter and Dart
  • SwiftUI iOS apps
  • Kotlin Jetpack Compose
  • Offline-first sync
  • Mobile performance and release

Artifacts Produced

Mobile Deliverable

Pattern

Framework choice, implementation plan, or production-ready app changes

Output should name target platforms, framework rationale, mobile budgets, testing on real devices, and release path.

Next