ios-sync

Regenerate the iOS debug bridge against latest gstack templates.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill ios-sync-alejandrofigini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/ios-sync
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill ios-sync-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the iOS debug bridge against the latest upstream gstack templates to keep instrumentation in sync with the latest ViewModels and properties, reducing drift and manual rework.

Core Features & Use Cases

  • Regenerate iOS accessors and bridge wiring to match new templates
  • Sync instrumentation and state accessors to latest gstack changes
  • Use case: after upgrading gstack or adding new ViewModels, run ios-sync to refresh the bridge

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 sync iOS instrumentation after adding new ViewModels?

To sync iOS instrumentation after adding new ViewModels, you need to regenerate the iOS debug bridge against the latest gstack templates. This updates StateServer.swift, DebugOverlay.swift, and typed @Observable state accessors to prevent property drift.

When do I need to regenerate the iOS debug bridge?

You need to regenerate the iOS debug bridge after upgrading gstack or when adding new ViewModels and properties that require accessor coverage. Running this refresh ensures your iOS integration matches the latest upstream template changes.

Does ios-sync require local gstack tooling installed?

Yes, regenerating the iOS debug bridge relies on local gstack tooling installed in your environment. The process updates Package.swift and bridge wiring by pulling from the latest upstream gstack templates available locally.

What is the best way to refresh iOS state accessors after a gstack upgrade?

The best way to refresh iOS state accessors after a gstack upgrade is to regenerate the debug bridge using template synchronization. This updates the typed @Observable accessors and core Swift files to match upstream changes automatically.

Which iOS files are updated when syncing gstack instrumentation?

Syncing gstack instrumentation updates StateServer.swift, DebugOverlay.swift, Package.swift, and the typed @Observable state accessors. These files are regenerated to align with the latest upstream gstack templates.