nais2-mobile-sync-planning

Plan Tauri Android releases and encrypted metadata sync for NAIS2.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/JaCha00/nais2-integration-complete --skill nais2-mobile-sync-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nais2-mobile-sync-planning
Source: https://github.com/JaCha00/nais2-integration-complete/tree/main/.codex/skills/nais2-mobile-sync-planning
Command: npx skills add https://github.com/JaCha00/nais2-integration-complete --skill nais2-mobile-sync-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit helps with planning and reviewing release bundles, Android porting, APK/AAB readiness, PC/mobile sync, sync sanitization, LAN sync server, Supabase relay, pairing, and mobile release checklists for NAIS2 mobile.

Core Features & Use Cases

  • Release and Sync Planning: Captures a reusable workflow for planning NAIS2 Tauri Android release and PC sync plans.
  • Task Management: Defines a workflow with multiple phases and specific actions for mobile packaging and sync processes.
  • Documentation Compliance: Provides guidelines on required documentation and verification processes.

Quick Start

Review the nais2-mobile-sync-planning skill for baseline repository preservation constraints and verifier expectations.

Frequently Asked Questions about nais2-mobile-sync-planning

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

FAQPage Schema
How do I plan a Tauri Android release and PC sync for NAIS2?

To plan a Tauri Android release and PC sync for NAIS2, this skill captures a reusable workflow covering APK/AAB readiness, mobile packaging, and encrypted metadata synchronization across multiple defined phases.

What is the process for NAIS2 mobile sync sanitization and pairing?

NAIS2 mobile sync sanitization and pairing involves verifying encrypted metadata exchanges between PC and mobile, ensuring data integrity through LAN sync server or Supabase relay connections during the release readiness checks.

How do I verify APK and AAB readiness for a NAIS2 Android port?

You verify APK and AAB readiness for a NAIS2 Android port by following the skill's mobile release checklists, which define specific verification actions and documentation compliance guidelines for Tauri Android packaging.

Does NAIS2 mobile sync support both LAN server and Supabase relay connections?

Yes, NAIS2 mobile sync supports both LAN sync server and Supabase relay connections, allowing flexible encrypted metadata synchronization and pairing between desktop and Android devices during release workflows.

What are the limitations when porting a NAIS2 Tauri application to Android?

Limitations when porting a NAIS2 Tauri application to Android include baseline repository preservation constraints and strict documentation compliance requirements that must be verified before APK or AAB packaging completion.

Do I need a release checklist for NAIS2 mobile packaging and encrypted metadata sync?

Yes, you need a release checklist for NAIS2 mobile packaging and encrypted metadata sync to ensure task management across multiple phases, verify sync sanitization, and maintain baseline repository preservation constraints.