... Each dir is it s own service/app. Works like a charm. Comment from Sai Prakash(@sylonzero): We're on the same backend and also, all Cursor users (though I throw in some Claude Code work from time to time). Our NX-based monorepo works extremely well for us: TypeScript-centric - so even MCP services etc can use the same domain logic, schema and other shared libs Rules, shared libs, build system, multiple apps, different outputs - very simple Tailwind-based style ... ... dependency graph. For those shipping SDKs: do you find that keeping the SDK code in the same monorepo helps the AI write better integration tests, or does it get confused by the different environments (e.g., std for SDK vs

... just released a quick tutorial showing how to create a profile on NXT. Your profile is the foundation of discovery on the platform. It helps the community understand who you are, what you re building, and why it matters. Early users currently get more visibility, and a complete profile makes that visibility meaningful. No marketplace. No noise. Just projects and people worth discovering. If you re building in Web3, this is where you start. Watch the video tutorial nxtdrop

... This tutorial explains how to submit and present a project on NXT in a clear and structured way. It covers every step of the submission process, including project title, description, categories, tags, media, FAQs, and key details that improve discovery. Built for creators and builders who want their Web3 projects to be understood, discoverable, and presented professionally. View full video Comment from Mad Lips 21(@madlips21): This tutorial is part of NXT

... Here is a tutorial on how to turn NXT into an app on your phone. Very easy to do! See you on the app. Watch Video ...

... together, but it saved me a ton of time. I m super curious how others are approaching this - especially solo builders trying to move fast. Would love to hear your experiences or trade notes. Comment from Shekhar K. Sharma(@nxame): @busmark_w_nika  That happened to my app during first few prompts. I instructed it not to change any files that may not be relevant and bump a package.json everytime it changed code, then list what files changes ... ... revision later it is still going strong and top production quality code. Comment from Shekhar K. Sharma(@nxame