ios-sync

Regenerate the iOS debug bridge files against the latest upstream gstack templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After installing the iOS QA debug bridge, your Swift project drifts out of sync whenever you upgrade gstack, add new @Observable ViewModels or properties, or move the @Snapshotable generator marker. This Skill regenerates the bridge artifacts in place so the debug instrumentation always matches your current code and the latest upstream templates. ## Core Features & Use Cases - Bridge Regeneration: Updates StateServer.swift, DebugOverlay.swift, Package.swift, and the typed @Observable state accessors from upstream gstack templates. - Post-Upgrade Sync: Reapplies hardening fixes after a gstack version upgrade without manual file edits. - Accessor Coverage: Adds typed accessors for newly introduced ViewModels and properties. - Use Case: You added two new @Observable classes to your iOS app and upgraded gstack; run this Skill to regenerate the debug bridge so the new state is inspectable through the overlay. ## Quick Start Ask the assistant to resync the iOS debug bridge and regenerate the gstack iOS accessors for the current project.

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 upgrading gstack?

Run the ios-sync skill, which invokes the gstack-ios-qa-regen launcher to copy the latest upstream templates into your project. It updates StateServer.swift, DebugOverlay.swift, Package.swift, and the typed state accessors in place.

How do I add accessor coverage for new @Observable ViewModels?

Trigger ios-sync after adding new @Observable classes or properties. The regeneration step produces typed accessors for the new state so it becomes inspectable through the debug overlay.

When should I run ios-sync instead of editing the Swift files manually?

Run it after a gstack upgrade, after adding ViewModels or properties needing accessor coverage, or after moving the @Snapshotable generator marker. Manual edits are overwritten by the template-based regeneration.

Does ios-sync work if the gstack install is stale?

The skill detects a stale install through its preamble check and continues in degraded mode, telling you to run ./setup or /gstack-upgrade. Telemetry and onboarding steps are deferred, but the regeneration task still proceeds.

What files does the iOS debug bridge regeneration modify?

It modifies StateServer.swift, DebugOverlay.swift, Package.swift, and the typed @Observable state accessor files. Templates are sourced from the upstream gstack installation resolved by the regen launcher.