sync-studio-schema

Generate a studio schema-mirror prompt from git diffs of ComposableScreen types.

2|1|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/Rocapine/react-native-onboarding --skill sync-studio-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-studio-schema
Source: https://github.com/Rocapine/react-native-onboarding/tree/main/.claude/skills/sync-studio-schema
Command: npx skills add https://github.com/Rocapine/react-native-onboarding --skill sync-studio-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a ready-to-use studio prompt by reading local changes to ComposableScreen types and emitting a schema-mirror that can be pasted into the onboarding-studio repository.

Core Features & Use Cases

  • Detects scope of changes across ComposableScreen types.ts and related UIElement definitions.
  • Classifies edits (new, modified, deleted) and builds a structured prompt for studio synchronization.
  • Outputs a copy-ready prompt plus guidance for downstream migrations and editor updates.

Quick Start

Run after editing UIElement types to generate the studio sync prompt and copy it into onboarding-studio.

Frequently Asked Questions about sync-studio-schema

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

FAQPage Schema
How do I generate a studio prompt from TypeScript UI type changes?

You generate a studio prompt from TypeScript UI type changes by inspecting git diffs for ComposableScreen types.ts and UIElement files, then emitting a structured, copy-ready prompt to paste into the onboarding-studio repository.

What is a schema-mirror prompt for onboarding-studio synchronization?

A schema-mirror prompt for onboarding-studio synchronization is a structured text output that classifies UIElement type edits as new, modified, or deleted, ensuring local ComposableScreen changes stay aligned with the studio repository.

How do I sync ComposableScreen types with the onboarding-studio repository?

You sync ComposableScreen types with the onboarding-studio repository by running the schema-mirror workflow after editing UIElement types, copying the generated prompt, and pasting it into your onboarding-studio project to apply downstream migrations.

Does the studio prompt generation require a specific Git environment?

Yes, studio prompt generation requires a Git-enabled project environment to inspect local git diffs for ComposableScreen types.ts and related UIElement definitions, which is necessary to detect and classify the scope of recent edits.

What's the best way to handle onboarding-studio migrations after UIElement deletions?

The best way to handle onboarding-studio migrations after UIElement deletions is to use the generated schema-mirror prompt, which includes specific guidance for downstream editor updates and migrations triggered by deleted or modified types.