ios-sync

Regenerate iOS debug bridge components and typed state accessors from gstack templates.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill ios-sync-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/yocxy2/gstack3/tree/main/ios-sync
Command: npx skills add https://github.com/yocxy2/gstack3 --skill ios-sync-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the synchronization of iOS instrumentation, ensuring that your debug bridge, state accessors, and project configuration remain consistent with the latest gstack upstream templates.

Core Features & Use Cases

  • Bridge Regeneration: Updates StateServer.swift, DebugOverlay.swift, and Package.swift to match current architecture.
  • Accessor Coverage: Automatically generates typed @Observable state accessors for new ViewModels or properties.
  • Use Case: After upgrading your gstack version or adding new features to your iOS app, run this skill to ensure your debug overlay and state management remain fully functional and aligned with the latest tooling.

Quick Start

Ask the assistant to resync the ios debug bridge to update your instrumentation and accessors.

Frequently Asked Questions about ios-sync

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

FAQPage Schema
How do I sync my iOS debug bridge after a dependency upgrade?

Run an automated synchronization to regenerate StateServer.swift, DebugOverlay.swift, and Package.swift. This updates your iOS debug bridge to match current gstack upstream templates, ensuring instrumentation and state management remain fully functional after dependency upgrades.

How do I generate typed state accessors for new Swift ViewModels?

Generating typed state accessors for new Swift ViewModels is handled automatically during the debug bridge synchronization process. The tool creates typed @Observable state accessors for new properties to maintain consistent instrumentation and state access.

When do I need to regenerate my iOS debug overlay code?

You need to regenerate your iOS debug overlay code after upgrading your gstack version or adding new features to your iOS app. This maintains alignment between your debug bridge, state accessors, and upstream template architecture.

Does this automated synchronization work with Swift @Observable state management?

Yes, the synchronization directly supports Swift @Observable state management by automatically generating typed state accessors. It updates your debug bridge components to maintain consistent instrumentation across your iOS project architecture.

What is the best way to maintain consistent iOS instrumentation after architectural changes?

The best way to maintain consistent iOS instrumentation after architectural changes is to resync your debug bridge with upstream gstack templates. This regenerates StateServer.swift and DebugOverlay.swift while updating typed state accessors automatically.