The wait is over! Here’s my written tutorial and video guide to get you started vibe coding your way into the future.
Ditto by Soapbox's avatar Ditto by Soapbox
MKStack is the fastest way to start building a #Nostr app with #AI that immediately works, connects to real relays, and follows the protocol standards — all in one shot. @Derek Ross teamed up with Soapbox to put together this step-by-step tutorial of how to get started #vibecoding with MKStack. https://soapbox.pub/blog/mkstack-tutorial/
View quoted note →

Replies (47)

i do not believe it looks at community NIPs, but i could be wrong. i say this without certainty, only because i don't recall seeing it looking at them when i scrolled through what it was doing with MCP. if it's not, i would copy and paste entire NIPs or create a document CUSTOM_NIP.md and put it in the project directory.
I'll say *yes* only because I've seen Dork read other MD files that it's created as part of a change. They were all named NIP.md or FEATURE_NAME.md. Dork will read the whole directory to understand the project.
Smaller context windows. Implement one feature and then then control-c, exit, relaunch stacks agent, start fresh. It burns money, but not as much money as contracting work out to a junior developer. It will get cheaper in the future.
Cool. I used it for a day after seeing your first video and it got a lot done but I burned $100. I also had no idea what I was doing. I took the code it gave me and started using Claude Code and Cursor to finish it since it's much much cheaper. I'll have to try it again but Claude is working great for my current project.
i will say that as you build more, it gets cheaper per application becuase you learn how to prompt and build better. my first application was very expensive.
n's avatar
n 6 months ago
(・∀・)イイネ!!
Cool, what have you made so far? I’ve messed around with it off and on. Used cursor, Replit but got kind of stuck with a few ideas. Learning GitHub and figuring out how to go back to a previous version is something I’m need help in understanding still
My first was 5050pods.com using MKStacks and then adding to it with a combination of Claude Code and Cursor. Still needs more live testing so its on the back burner. Currently I'm working on @chadf_boostbot that was made with Claude Code and Cursor. I like Claude for building and Cursor is nice for trying to make the code work if Claude gets stuck.
Love this! Mastering a new skill is the ultimate vibe, feels like upgrading your own personal software. I'll be studying this while daydreaming about the ultimate hardware upgrade: finding the perfect yacht for sale https://www.yachttrading.com/. Cheers to building the future!
That would be a good idea as a test case. I haven't heard anyone doing that yet, but since Cursor works fine you'd just need to add the Void (I'm not familiar) rules file and MCP config.
Void is actually Free Software Cursor (Notice how I spelled Free Software, as I don't just use either FOSS or FLOSS because it's neutral). It should work similarly to Cursor, but Void is under Apache 2 if I'm not mistaken.
This is great. My problem seems to be an outdated version of node js, but I just upgraded. Time to start vibe coding. Thanks dude.
I'm riding the struggle bus big time to get started with this, encountering some errors and unsure how to navigate the API part. I'm a complete developer noob but have an idea I want to develop 😔
what errors are you getting? do you mean errors with your application? or errors with stacks and mkstack itself? if it's errors with your application you can copy and paste them into Dork and have him work on them. though i will say that Dork only accepts one line and if you want to copy and paste a very long error, you're going to need to remove all new line breaks.
I'm making some progress. Needing Git wasn't in the tutorial, but I got that sorted. I got the API setup with some credits, got the app coded, but it's not loading for me in the browser. Stuck with the "Welcome to your blank app" screen. Working with Dork and Chatpgpt to hopefully figure this out...
i have seen this happen before. your application is built, but the main index page wasn't updated. try something like "now that the application is built, i'd like to access it from the index page" and see if that fixes it.
Ok, thanks! I'm deep in the troubleshooting, aided by the AIs, and am close to giving up. At least for now. Chatgpt told me it wasn't a problem the errors "Error starting MCP js-dev: spawn npx ENOENT" and "Error starting MCP nostr: spawn npx ENOENT" when starting the starts address. But the AI tells me it is, which makes sense?