ios-sync

Regenerate the iOS debug bridge and typed state accessors for gstack projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill regenerates the iOS debug bridge and typed state accessors so your gstack app stays aligned with upstream templates and evolving app state.

Core Features & Use Cases

  • Bridge regeneration: Updates the iOS debug bridge files after gstack upgrades or template changes.
  • Accessor coverage: Rebuilds typed @Observable state accessors when new ViewModels or properties are added.
  • Project alignment: Keeps StateServer.swift, DebugOverlay.swift, and Package.swift synchronized with the current repo shape.

Quick Start

Ask the Skill to resync the iOS debug bridge for the current project so it regenerates the required Swift files 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 regenerate the iOS debug bridge after a gstack template upgrade?

You need to regenerate typed state accessors for new ViewModels when adding observable properties to your gstack project, ensuring StateServer.swift and DebugOverlay.swift stay synchronized with the current repo structure.

What is the best way to keep StateServer.swift and DebugOverlay.swift synchronized with my repo?

Yes, you can use this Skill to update the iOS debug bridge for Swift projects by regenerating typed @Observable state accessors and keeping Package.swift aligned with your evolving app state.

When do I need to regenerate typed state accessors in my iOS project?

You need to regenerate typed state accessors for new ViewModels when adding observable properties to your gstack project, ensuring StateServer.swift and DebugOverlay.swift stay synchronized with the current repo structure.

Does this Skill require any external dependencies to update the iOS debug bridge?

No external dependencies are required to update the iOS debug bridge. The Skill operates independently using local repo-aware update checks and guarded workflow prompts to regenerate Swift files.

Why does my iOS debug bridge break after updating gstack templates?

Your iOS debug bridge breaks after updating gstack templates because StateServer.swift and DebugOverlay.swift lose alignment with the new upstream structure, requiring a regeneration of typed state accessors to fix.