ios-sync

Regenerate iOS debug bridge components and state accessors from gstack templates.

Updated Jun 5, 2026

Search Tags:#debug #swift #ios #instrumentation #sync #gstack

Ready to run

npx skills add https://github.com/smarmen86/claude-code-kit --skill ios-sync-smarmen86

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ios-sync
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/ios-sync
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill ios-sync-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves synchronization issues between your local iOS instrumentation and the upstream gstack templates, ensuring your debug bridge and state accessors remain functional after project updates.

Core Features & Use Cases

Bridge Regeneration: Automatically updates StateServer.swift, DebugOverlay.swift, and Package.swift to match the latest gstack standards.
Accessor Coverage: Refreshes typed @Observable state accessors whenever new ViewModels or properties are introduced.
Use Case: After upgrading your gstack version or adding new UI state properties, run this skill to ensure the iOS debug overlay correctly reflects your current application state without manual code adjustments.

Quick Start

Invoke the ios-sync skill to regenerate the iOS accessors and resync the debug bridge.

Frequently Asked Questions about ios-sync

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

FAQPage Schema

How do I synchronize iOS debug bridge components after updating dependencies?▼

To synchronize iOS debug bridge components, you can regenerate StateServer.swift, DebugOverlay.swift, and Package.swift files to match the latest upstream gstack templates. This ensures your debug bridge remains functional after dependency or model changes.

When do I need to regenerate iOS state accessors in a Swift project?▼

You need to regenerate iOS state accessors whenever you add new ViewModels or UI state properties to your Swift project. This refreshes the typed @Observable accessors so the debug overlay accurately reflects current application state.

How does automated instrumentation update validation work for iOS projects?▼

Automated instrumentation update validation checks architectural consistency by regenerating StateServer, DebugOverlay, and Package definitions against upstream gstack standards. It targets Swift-based iOS projects to maintain sync after dependency or model changes.

Can I use ios-sync to update my debug overlay without manual code adjustments?▼

Yes, you can use ios-sync to automatically update your debug overlay without manual code adjustments. It regenerates iOS accessors and resyncs the debug bridge following gstack version upgrades or the addition of new UI state properties.

Does this Skill require specific dependencies to resync Swift debug bridges?▼

No specific dependencies are required to resync Swift debug bridges with this Skill. It operates using internal scripts to validate and regenerate instrumentation components against upstream gstack templates.

Why does my iOS debug overlay show outdated application state after a model change?▼

Your iOS debug overlay shows outdated state because typed @Observable accessors are not synchronized with new model changes. Running an instrumentation sync regenerates these accessors to correctly reflect your current application state.