Troubleshooting

Animations not playing, wrong fonts, an agent that re-themed your screen. The five real failures.

The animations do not play

This is the most common one by a distance. Reanimated needs its Babel plugin, and it must be last in the plugins array. Without it, animated components render at their final values and nothing moves, with no error anywhere.

// babel.config.js
module.exports = function (api) {
  api.cache(true)
  return {
    presets: ['babel-preset-expo'],
    plugins: ['react-native-reanimated/plugin'], // must be LAST
  }
}

Then restart the bundler with the cache cleared: npx expo start -c. A plain restart is not enough.

The fonts look wrong

Fonts load once at the app root, not inside a screen. Each design exports a fonts object; spread it into useFonts in your root and hold the splash screen until it resolves. If you skip this, text falls back to the system face and every weight looks slightly off.

import { useFonts } from 'expo-font'
import * as SplashScreen from 'expo-splash-screen'
import { fonts } from './components/clean-settings/screen'

SplashScreen.preventAutoHideAsync()

export default function App() {
  const [loaded, error] = useFonts({ ...fonts })
  useEffect(() => {
    if (loaded || error) SplashScreen.hideAsync()
  }, [loaded, error])
  if (!loaded && !error) return null
  return <YourApp />
}

The agent re-themed it to match my app

Tell it to revert and paste the prompt into a fresh conversation. The instruction not to adapt is in every prompt, but a long session where the agent has absorbed your conventions can override it. A clean context is the reliable fix.

It crashes in Expo Go

Check the design's badge. A few use native modules that Expo Go does not bundle, and those need a development build. The badge on the card, the badge on the detail page and the prompt itself all say so before you copy.

npx expo run:ios

The agent stopped halfway and left a placeholder

Ask it to finish the file it truncated, naming the file. The prompt bans placeholders explicitly, but agents under context pressure still do it occasionally, and long flows are the usual culprit. Nothing is lost; the rest of the paste is intact.

Still stuck
Email support@clevens.com with the design slug and what your agent did. A prompt that fails the same way twice is a bug in the prompt, not in your setup, and it gets fixed.