# Cursor rules that keep mobile repos shippable under production pressure

Every team using Cursor on a mobile repo hits the same moment. The agent scaffolds a screen beautifully, then imports a web-only library, breaks the Expo Router layout, or rewrites your auth guard with a pattern you banned three sprints ago. The fix is not a better prompt. It is rules checked into the repo that every agent run follows automatically.

This guide shows how to write Cursor rules that keep a React Native or Expo repo shippable: scoped rule files, mobile-specific constraints, and a review loop that catches drift. If you are standardizing conventions more broadly, our [bulletproof .cursorrules walkthrough](/blog/cursor-rules-nextjs) covers the file mechanics — here we go deep on mobile production concerns.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/cursor-rules-mobile-repo-production](https://otf-kit.dev/blog/cursor-rules-mobile-repo-production) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*