Stackness is where developers and vibe coders show the tools, workflows, and approaches they build with. Build a stack profile you share as one link, post your moves, follow people whose taste you trust, and watch tools rise and fall. Free and with an MCP server.
Hey everyone,
I'm very happy to share that I've launched a first version of the Stackness platform. It's a social platform where people can share how they build software and the tools and techniques they use. You can also see which tools and workflows are popular right now.
My main goal is to have a community that can share, discuss, and discover new things in the tech world.
I would really appreciate it if you could let me know whether it's relevant to you and what do you think about the platform in general :)
Report
You asked whether it's relevant. The thing that kills every stack profile site is staleness, because mine would be accurate for about three weeks and then sit there lying about a tool I dropped, and I'm not coming back to edit it. The MCP server is the most interesting thing here and it's the last four words of your description, since that's the one path where the profile updates itself instead of nagging me. I'd make reading a repo or a package file the default way a stack gets built and leave manual entry as the fallback.
Thanks a lot for the feedback, I really appreciate that. I'm totally agree that MCP server feature should be prominent, I'll probably move it higher in all descriptions :)
And I fully agree that having stack profile up-to-date is one of the main challenge, that's why there're multiple ways to automate that on Stackness. I also plan to publish skills on GitHub to make it even easier to plug in their setup.
Reading the repo or package file is a nice idea, although I'm worried that many people don't share that stuff publicly and scanning them would be complicated. Their AI tools on the other hand can do that and upload things themself :) I'll give it another thought to make it more convenient, thanks again for the feedback!
Stackness
You asked whether it's relevant. The thing that kills every stack profile site is staleness, because mine would be accurate for about three weeks and then sit there lying about a tool I dropped, and I'm not coming back to edit it. The MCP server is the most interesting thing here and it's the last four words of your description, since that's the one path where the profile updates itself instead of nagging me. I'd make reading a repo or a package file the default way a stack gets built and leave manual entry as the fallback.
Stackness
Hi @asadmalik901 !
Thanks a lot for the feedback, I really appreciate that. I'm totally agree that MCP server feature should be prominent, I'll probably move it higher in all descriptions :)
And I fully agree that having stack profile up-to-date is one of the main challenge, that's why there're multiple ways to automate that on Stackness. I also plan to publish skills on GitHub to make it even easier to plug in their setup.
Reading the repo or package file is a nice idea, although I'm worried that many people don't share that stuff publicly and scanning them would be complicated. Their AI tools on the other hand can do that and upload things themself :) I'll give it another thought to make it more convenient, thanks again for the feedback!