ios-sync

Regenerate iOS debug bridge and typed state accessors after gstack upgrades.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill ios-sync-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.claude/skills/gstack/ios-sync
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill ios-sync-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping iOS debugging infrastructure synchronized with the latest upstream gstack templates. After upgrading gstack or adding new ViewModels and properties, developers face broken instrumentation and mismatched state accessors that require tedious manual updates across multiple Swift files.

Core Features & Use Cases

  • Automated Bridge Regeneration: Updates StateServer.swift, DebugOverlay.swift, Package.swift, and typed @Observable state accessors to match the latest gstack templates.
  • Upgrade-Safe Workflow: Designed to run immediately after gstack upgrades or when new ViewModels need accessor coverage, ensuring debug instrumentation stays current without manual file editing.
  • Use Case: An iOS developer just upgraded their gstack dependency and finds the debug overlay broken because StateServer.swift is outdated. Running this skill automatically regenerates all affected files and restores full debugging capability.

Quick Start

Use the ios-sync skill to regenerate the iOS debug bridge and state accessors after upgrading gstack or adding new ViewModels.

Frequently Asked Questions about ios-sync

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

FAQPage Schema
How do I regenerate the iOS debug bridge after upgrading gstack?

To regenerate the iOS debug bridge after a gstack upgrade, run this skill to automatically update StateServer.swift, DebugOverlay.swift, Package.swift, and Observable accessors to align with the latest upstream templates.

Why does my iOS debug overlay break when I add new ViewModels?

iOS debug overlays break when new ViewModels lack typed state accessors or instrumentation becomes outdated. This skill synchronizes @Observable accessors and debug bridge files to restore full debugging capability.

Can I update Swift state accessors without manually editing Package.swift?

Yes, you can update Swift state accessors without manual editing. This skill applies bash scripting and gstack CLI utilities to automatically regenerate Package.swift and @Observable accessors for instrumentation consistency.

Does ios-sync work with existing Xcode debugging workflows?

Yes, ios-sync integrates with Xcode debugging workflows by regenerating StateServer.swift and DebugOverlay.swift. It maintains instrumentation consistency following gstack upgrades without disrupting your existing iOS development environment.

What are the limitations of using automated scripts for iOS debug bridge synchronization?

Automated iOS debug bridge synchronization requires gstack CLI utilities and bash scripting to update Swift source files. It is designed specifically for gstack template alignment and may not cover custom instrumentation outside standard StateServer and DebugOverlay files.