ios-sync

Regenerate the iOS debug bridge against upstream gstack templates.

Updated Jun 18, 2026

Search Tags:#instrumentation #gstack #viewmodels #ios-sync #state-accessors #ios-instrumentation #bridge-regeneration

Ready to run

npx skills add https://github.com/abhishekmmgn/didactic-invention --skill ios-sync-abhishekmmgn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/ios-sync
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill ios-sync-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the iOS debug bridge against the latest upstream gstack templates to maintain accurate instrumentation and accessors.

Core Features & Use Cases

Update StateServer.swift, DebugOverlay.swift, and Package.swift to reflect upstream templates.
Regenerate the typed @Observable state accessors when ViewModels or properties change.
Use after upgrading gstack or adding new ViewModels/properties that require accessor coverage.

Quick Start

Invoke ios-sync to regenerate the iOS bridge against the latest gstack templates.

Frequently Asked Questions about ios-sync

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

FAQPage Schema

How do I regenerate iOS debug bridge files after upgrading gstack templates?▼

To regenerate the iOS debug bridge after a gstack upgrade, run ios-sync to rewrite StateServer.swift, DebugOverlay.swift, and Package.swift, ensuring native instrumentation aligns with current upstream templates.

When do I need to regenerate typed @Observable state accessors in iOS?▼

You need to regenerate typed @Observable state accessors when adding new ViewModels or properties that require accessor coverage, ensuring the iOS debug bridge maintains accurate state instrumentation.

Can I update StateServer.swift and DebugOverlay.swift to match upstream gstack templates?▼

Yes, you can update StateServer.swift and DebugOverlay.swift by running ios-sync, which rewrites these native iOS instrumentation files to match the latest upstream gstack templates.

What's the best way to add accessor coverage for new ViewModels in an iOS debug bridge?▼

The best way to add accessor coverage for new ViewModels is invoking ios-sync, which regenerates the typed @Observable state accessors and updates the iOS debug bridge files for current compatibility.

Do I need a Bash environment and gstack toolchain to regenerate iOS instrumentation?▼

Yes, ios-sync relies on the host's Bash environment and the gstack toolchain to rewrite native iOS instrumentation and regenerate the debug bridge files for template compatibility.

Why are my iOS debug bridge accessors out of sync after adding new properties?▼

iOS debug bridge accessors fall out of sync when new properties are added without regenerating the typed @Observable state accessors, requiring ios-sync to update StateServer.swift and Package.swift.