Launching today
Stackness
Show your stack! The social home for your dev tools
57 followers
Show your stack! The social home for your dev tools
57 followers
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.
Stackness
Hedy AI
Can you update your stack whenever you switch tools and does the shared link update automatically?
Stackness
@kate_sleeman Yes sure, you can update your stack any time with new tools, it will get recorded to your history feed and shared link will lead to your updated published stack page.
Serand
I like the social side of this. Seeing what tools other developers actually use can be more useful than reading endless tool list.
Stackness
@anthony_adams_ yep, that would be amazing! And hopefully soon the social aspect of Stackness will work better once there're more users sharing their stack and discussing it, thanks for your feedback!
TrackerJam
The idea of following people based on their tool choices is interesting. Sometimes you find better tools through somenes workflow than through a search.
Stackness
@maklyen_may yes indeed, and you can see what the people you follow added to their stack via https://stackness.dev/updates page. thanks for the feedback!
Will there be a way to compare two people’s stacks and quickly see which tools they have in common?
Stackness
@zeeshan_aslam2 great idea! I was developing something similar but I haven't finished yet. My idea was to do a comparison tool between two tools based on user's stacks. But I like your idea too, it could be some kind of "compare" button which allows you to pick users and see what's in common. Thanks for suggestion! I think I'll implement it very soon
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!
Premarket Bell
The one link stack profile is a really handy idea. It would be nice to share your whole setup without having to list every tool separately.
Stackness
@daniel_henry4 thanks a lot! initial setup is quite annoying because I had to reflect and analyse what I'm actually using haha but then that gave me idea of the onboarding wizard and also "stack builder" feature which basically allows you to select a bunch of tools by clicking (similar to Spotify), so it might help. And then there's always AI which can scan the projects and extract the tools