Install & Use Skills
For first-time Cresc integration, the recommended path is to install the react-native-update Skill and let your AI coding tool adapt the integration to your existing project. Fall back to the manual docs only when your app has unusual native structure, strict review requirements, or edge cases the generated changes do not cover well.
Skill Information
- Skill Name:
react-native-update - Source Repo:
reactnativecn/react-native-update-skill
Recommended workflow
- Install the
react-native-updateSkill. - Open your React Native or Expo app root directory inside the AI tool.
- Ask AI to integrate Cresc into the current project structure.
- Use Installation & Config and Code Integration as your review checklist.
Installation
Update Skill
Prompts you can give to AI
Following installation, you can assign requests directly to AI assistants, generating outcomes like:
- "Integrate
react-native-updateinside my Expo project." - "Execute integration remodeling over the class component root node."
- "Keep my current navigation structure and wrap the app with
UpdateProvider." - "Configure a controlled whitelist staged rollout mechanism."
- "Diagnose why 'OTA updates aren't deploying correctly' issues."
What the Skill can help automate
- RN CLI / Expo Integration flows
- Checking
update.jsonandappKeyconfiguration parameters - Essential iOS / Android native intervention warnings
- Polling update strategy recommendations (
checkStrategy/updateStrategy) - Diagnostics tackling familiar conflicts (like
expo-updates) - Examples combining class instances manipulating user whitelists
When to switch back to the manual docs
- Your app is brownfield, monorepo-based, or heavily customized at the native layer.
- Auto-linking or native compilation is already failing and needs isolated debugging.
- Your team wants to compare generated edits against the manual baseline step by step.