react-native-template-obytes
CLAUDE.md4.3k starsChanged 10 months agoMITView on GitHub
This project was generated from the Obytes React Native Template, a production-ready React Native starter with modern tooling and best practices. Essential Commands: Environment-Specific:
Trending
More talk lately.thin dataabout the whole repository
Who's talking about obytes/react-native-template-obytes
- rootstrap/react-native-template“docs: finish rebranding leftovers from obytes”GitHub · Nov 5, 2026
- jondot/awesome-react-native“Add obytes react native starter template”GitHub · Apr 27, 2025
- luke-h1/foam“split up CI into seperate jobs”GitHub · Jan 11, 2025
- rootstrap/react-native-template“chore: add warning in Pull Request template”GitHub · Jun 27, 2024
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
The file
We split this claude.md into the rules it gives an agent
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
Add routes: Create files in src/app/ (file-based routing)
- Very specific: line 55
Forms: Use TanStack Form + Zod (see src/features/auth/components/login-form.tsx)
- Very specific: line 56
Data fetching: Use React Query (see src/features/feed/api.ts)
- Very specific: line 57
Global state: Use Zustand (see src/features/auth/use-auth-store.tsx)
- Very specific: line 59
Storage: Use MMKV via src/lib/storage.tsx for sensitive data
- Very specific: line 60
Imports: Always use @/ prefix, never relative imports
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
This project was generated from the Obytes React Native Template, a production-ready React Native starter with modern tooling and best practices.
What: Technology Stack
- Expo SDK 54 with React Native 0.81.5 - Managed React Native development
- TypeScript - Strict type safety throughout
- Expo Router 6 - File-based routing (like Next.js)
- TailwindCSS via Uniwind/Nativewind - Utility-first styling for React Native
- Zustand - Lightweight global state management
- React Query - Server state and data fetching
- TanStack Form + Zod - Type-safe form handling and validation
- MMKV - Encrypted local storage
- Jest + React Testing Library - Unit testing
What: Project Structure
src/
├── app/ # Expo Router file-based routes (add new routes here)
├── features/ # Feature modules - auth, feed, settings are EXAMPLES
├── components/ui/ # Pre-built UI components (button, input, modal, etc.)
├── lib/ # Pre-configured utilities (api, auth, i18n, storage)
├── translations/ # i18n files (en.json, ar.json - add more languages)
└── global.css # TailwindCSS configuration
Root Files:
├── env.ts # Environment config (CUSTOMIZE bundle IDs, API URLs)
├── app.config.ts # Expo configuration
└── README.md # Project-specific documentationHow: Development Workflow
Essential Commands:
pnpm start # Start dev server
pnpm ios/android # Run on platform
pnpm lint # ESLint check
pnpm type-check # TypeScript validation
pnpm test # Run Jest tests
pnpm check-all # All quality checksEnvironment-Specific:
pnpm start:preview # Preview environment
pnpm ios:production # Production iOS
pnpm build:production:ios # EAS production buildHow: Key Patterns
- Create features: New folder in
src/features/[your-feature]/with screens, components, API hooks - Add routes: Create files in
src/app/(file-based routing) - Forms: Use TanStack Form + Zod (see
src/features/auth/components/login-form.tsx) - Data fetching: Use React Query (see
src/features/feed/api.ts) - Global state: Use Zustand (see
src/features/auth/use-auth-store.tsx) - Styling: NativeWind/Tailwind classes (see
src/components/ui/button.tsx) - Storage: Use MMKV via
src/lib/storage.tsxfor sensitive data - Imports: Always use
@/prefix, never relative imports
How: Essential Rules
- ✅ DO use absolute imports:
@/components/ui/button - ✅ DO follow feature-based structure:
src/features/[name]/ - ✅ DO use TanStack Form for forms (not react-hook-form)
- ✅ DO use MMKV storage for sensitive data (not AsyncStorage)
- ✅ DO use EAS Build for production:
pnpm build:production:ios - ✅ DO prefix env vars with
EXPO_PUBLIC_*for app access - ❌ DO NOT modify
android/orios/directly (use Expo config plugins)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

