skills.rest
mi179
mi179COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ios-sync

Regenerate the iOS debug bridge against upstream gstack templates.

1|Updated May 27, 2026
Search Tags:#ios#instrumentation#gstack#viewmodels#debug-bridge#ios-sync#state-accessors
One-click install
npx skills add https://github.com/mi179/claude-skills --skill ios-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/ios-sync
Command: npx skills add https://github.com/mi179/claude-skills --skill ios-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the iOS debug bridge against the latest upstream gstack templates. This keeps StateServer.swift, DebugOverlay.swift, Package.swift, and the typed @Observable state accessors aligned with the current gstack version, ensuring compatibility after upgrades or when new ViewModels or properties are added.

Core Features & Use Cases

  • Synchronizes iOS instrumentation and accessors with upstream gstack templates to reflect changes in ViewModels and state accessors.
  • Updates the debug bridge components (StateServer.swift, DebugOverlay.swift, Package.swift) to maintain compatibility with the iOS-side tooling.
  • Use during post-upgrade maintenance or when tooling requests a resync of the iOS debug bridge.

Quick Start

Run the ios-sync skill to regenerate the iOS debug bridge after upgrading gstack.

Frequently Asked Questions about ios-sync

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

FAQPage Schema
How do I sync iOS debug bridge files after upgrading gstack?▼

To sync the iOS debug bridge after a gstack upgrade, regenerate StateServer.swift, DebugOverlay.swift, and Package.swift against the latest upstream templates to ensure state accessors and instrumentation stay aligned.

Why does my iOS instrumentation break when adding new ViewModels?▼

iOS instrumentation breaks when new ViewModels are added because typed @Observable state accessors become outdated. Regenerating the debug bridge resyncs these accessors with the current gstack templates to restore coverage.

Does gstack state accessor coverage require manual Swift package updates?▼

State accessor coverage requires updating Package.swift along with StateServer.swift and DebugOverlay.swift. Regenerating the debug bridge enforces these updates to maintain iOS-side tooling compatibility.

What is the best way to regenerate iOS debug overlays for gstack?▼

The best way to regenerate iOS debug overlays is running a dedicated sync process that updates DebugOverlay.swift and related components against upstream gstack templates, ensuring all state accessors reflect current ViewModel properties.

Can I update StateServer.swift manually without regenerating the full debug bridge?▼

Updating StateServer.swift manually risks desyncing iOS instrumentation from upstream gstack templates. Regenerating the full debug bridge ensures StateServer.swift, DebugOverlay.swift, and Package.swift stay synchronized with current state accessors.

Related Skills

Explore More Software Engineering Skills→
abhishekmmgnabhishekmmgn

ios-sync

Regenerate the iOS debug bridge against upstream gstack templates.

Community
Advanced
robertzengcnrobertzengcn

ios-sync

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

Community
Advanced
limzivectorlimzivector

ios-sync

Regenerate the iOS debug bridge and state accessors for gstack templates.

Community
Intermediate
cloudofgeorgecloudofgeorge

ios-sync

Regenerate the iOS debug bridge to match latest gstack templates.

Community
Intermediate