1/ I kept wishing my coding agent already knew what a "CRM" or "dashboard" should contain the way Lovable and Replit do, without my code leaving my machine soI built Buildable: that product knowledge as a local plugin for Claude Code, Codex & Cursor. Just hit v1.0. 2/ The goal isn't "describe an app, get a finished product." It's to stop the agent starting from scratch when you say "build me a CRM."/buildable-plan "build me a CRM" → picks the archetype target (web/mobile) → hands over a build-verified starter → loads only the refs it needs (~10% of the brain) 3/ Instead of reinventing UI every time, it composes reusable micro-blocks, filterable table, detail panel, form, empty state.Persistence and auth are planned behind swappable local seams. No hosted lock-in. Nothing is uploaded. 4/ Then it reviews the result, build, responsive layout, accessibility, design tokens, local-first guardrails and gives you an honest "what's left to ship" list (data's mocked, no deploy). It never auto-adds a backend. 5/ Next.js TS Tailwind on web, Expo NativeWind on mobile. 15 app types generate runnable code today; the rest get a full spec plan. Zero deps, MIT, CI builds every starter.

1/ I kept wishing my coding agent already knew what a "CRM" or "dashboard" should contain the way Lovable and Replit do, without my code leaving my machine soI built Buildable: that product knowledge as a local plugin for Claude Code, Codex & Cursor. Just hit v1.0. 2/ The goal isn't "describe an app, get a finished product." It's to stop the agent starting from scratch when you say "build me a CRM."/buildable-plan "build me a CRM" → picks the archetype target (web/mobile) → hands over a build-verified starter → loads only the refs it needs (~10% of the brain) 3/ Instead of reinventing UI every time, it composes reusable micro-blocks, filterable table, detail panel, form, empty state.Persistence and auth are planned behind swappable local seams. No hosted lock-in. Nothing is uploaded. 4/ Then it reviews the result, build, responsive layout, accessibility, design tokens, local-first guardrails and gives you an honest "what's left to ship" list (data's mocked, no deploy). It never auto-adds a backend. 5/ Next.js TS Tailwind on web, Expo NativeWind on mobile. 15 app types generate runnable code today; the rest get a full spec plan. Zero deps, MIT, CI builds every starter

1/ I kept wishing my coding agent already knew what a "CRM" or "dashboard" should contain the way Lovable and Replit do, without my code leaving my machine soI built Buildable: that product knowledge as a local plugin for Claude Code, Codex & Cursor. Just hit v1.0. 2/ The goal isn't "describe an app, get a finished product." It's to stop the agent starting from scratch when you say "build me a CRM."/buildable-plan "build me a CRM" → picks the archetype target (web/mobile) → hands over a build-verified starter → loads only the refs it needs (~10% of the brain) 3/ Instead of reinventing UI every time, it composes reusable micro-blocks, filterable table, detail panel, form, empty state.Persistence and auth are planned behind swappable local seams. No hosted lock-in. Nothing is uploaded. 4/ Then it reviews the result, build, responsive layout, accessibility, design tokens, local-first guardrails and gives you an honest "what's left to ship" list (data's mocked, no deploy). It never auto-adds a backend. 5/ Next.js TS Tailwind on web, Expo NativeWind on mobile. 15 app types generate runnable code today; the rest get a full spec plan. Zero deps, MIT, CI builds every starter. ⭐ github.com/suntay44/buildabl…

1/ I kept wishing my coding agent already knew what a "CRM" or "dashboard" should contain the way Lovable and Replit do, without my code leaving my machine.So I built Buildable: that product knowledge as a local plugin for Claude Code, Codex & Cursor. Just hit v1.0. 🧵 2/ The goal isn't "describe an app, get a finished product." It's to stop the agent starting from scratch when you say "build me a CRM."/buildable-plan "build me a CRM" → picks the archetype target (web/mobile) → hands over a build-verified starter → loads only the refs it needs (~10% of the brain) 3/ Instead of reinventing UI every time, it composes reusable micro-blocks, filterable table, detail panel, form, empty state.Persistence and auth are planned behind swappable local seams. No hosted lock-in. Nothing is uploaded. 4/ Then it reviews the result, build, responsive layout, accessibility, design tokens, local-first guardrails and gives you an honest "what's left to ship" list (data's mocked, no deploy). It never auto-adds a backend. 5/ Next.js TS Tailwind on web, Expo NativeWind on mobile. 15 app types generate runnable code today; the rest get a full spec plan. Zero deps, MIT, CI builds every starter. ⭐ github.com/suntay44/buildabl…

A few weeks ago, I started building the Vitasync mobile app. I completed the authentication screens and integrated them with the live API. My major challenge was setting up NativeWind (Tailwind CSS for React Native) with Expo Router.

Expo, nativewind, convex

Turned the Home screen wireframe into actual UI, and other screens are also under progress, tried to setup Nativewind (A tool like Tailwind for React native) but it's not working for some reason now decided to start coding UI with default stylesheet of React native.

Did anyone managed to install nativewind v4 while using expo sdk 55 or 56? I have been struggling with this for last 2 days. Only classes used during build work. @expo @nativewindcss

React native! react wali feel ata hai plus nativewind just like tailwind

#LSPPDay02 Today I: - Set up Tailwind CSS in React Native using NativeWind - Configured everything manually - Learned how NativeWind integrates with React Native @lftechnology #60DaysOfLearning2026 #LearningWithLeapfrog

Minha tech stack como founder em 2026 - vercel pra frontend - railway pra backend e db - onlyfans pra renda passiva - js/ts pra front/mobile/backend - tailwind / nativewind pra styles - Claude e cursor pra AI

React Native UI Libraries Hero UI: heroui.com/en/docs/native/ge… Gluestack: gluestack.io/ React Native Reusables (ShadcnUI inspired): reactnativereusables.com/ React Native Paper (Material Design inspired): reactnativepaper.com/ Tamagui: tamagui.dev/ Nativewind UI: nativewindui.com/component/a…

How do you handle NativeWind styling issues in React Native, especially when they interfere with navigation layouts or navigation blocks?

Great to hear! I was actually inspired by your work on create-expo-stack when building Better T Stack 😁 And yeah, I’m definitely still interested. Would love to try NativeWind v5 once it moves to latest.

Noted, I committed to releasing v5 by AppJS, I’m still working to do so. Now that @mark__lawlor is back, major feature improvements will also follow. If you’re still interested, I’ll lyk once I move Nativewind v5 to latest. Regardless, your feedback is super useful, especially for something like better t stack. I really like the idea given my work on rn.new.

Stable v5 release I had Nativewind support before, but removed it because tailwind v3 was causing weird issues in monorepos with tailwind v4

Good question. We already see it in the weekly downloads: 210k for Uniwind and 150k for Unistyles. Unistyles is 2.5 years old, and Uniwind is 9 months old. I think most developers prefer Tailwind. There are also 1M weekly downloads on the NativeWind side.

Day 1 of #100DaysOfCode Updated my portfolio with new experience React Native for my new full-time role, built a small practice app using Expo Go, and explored NativeWind for styling Currently stuck on NativeWind setup issues 😅 Anyone with experience in this and can help me?

Day 1 It took me more than a day to set up Android simulator and react native/expo project, I hit almost every common beginner React Native/Expo issue at once. - Expo SDK version mismatch - Gradle build errors - Android emulator issues - Metro bundler problems - NativeWind setup issues - Babel config issues - Clerk auth setup - .env variables not loading - Expo Router confusion - TypeScript path alias errors - Package dependency conflicts - Android permissions/config - Cache/node_modules corruption - “Works on web but not on mobile” - React Native navigation/provider confusion React Native is genuinely way harder to set up initially than normal React