ios-sync

Regenerate the iOS debug bridge against latest gstack templates.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill ios-sync-sakshamkandel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/ios-sync
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill ios-sync-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The iOS debug bridge often becomes out-of-sync after upstream template changes, leading to manual drift and brittle instrumentation. This skill regenerates the iOS debug bridge against the latest gstack templates to ensure consistent behavior.

Core Features & Use Cases

  • Regenerate StateServer.swift, DebugOverlay.swift, and Package.swift to align with current gstack templates.
  • Update the typed @Observable state accessors used by iOS ViewModels and properties.
  • Provide a deterministic workflow to re-instrument iOS components after gstack upgrades or ViewModel changes.

Quick Start

Run the ios-sync skill to regenerate the iOS debug 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 the iOS debug bridge after a gstack template update?

To regenerate the iOS debug bridge after a gstack template update, run the ios-sync skill to apply deterministic changes across StateServer.swift, DebugOverlay.swift, and Package.swift. This ensures your debug bridge aligns with the latest upstream templates.

Why does my iOS debug bridge become out-of-sync with upstream gstack templates?

The iOS debug bridge becomes out-of-sync with upstream gstack templates due to manual drift after template changes. Regenerating the bridge and associated accessors ensures consistent behavior and eliminates brittle instrumentation.

Do I need the iOS tooling in the gstack environment to regenerate state accessors?

Yes, you need the iOS tooling in the gstack environment and access to upstream templates to regenerate typed @Observable state accessors. These prerequisites allow the skill to apply deterministic updates to iOS ViewModels.

Can I update typed @Observable state accessors in iOS ViewModels automatically?

Yes, you can update typed @Observable state accessors in iOS ViewModels automatically by running the ios-sync skill. It re-instruments iOS components deterministically after ViewModel changes or gstack upgrades.

What is the best way to fix manual drift in iOS debug bridge instrumentation?

The best way to fix manual drift in iOS debug bridge instrumentation is regenerating it against current gstack templates. This workflow updates StateServer.swift and DebugOverlay.swift to ensure consistent behavior.