正在加载视频...
视频加载失败
okay my free cursor rule builder is live, built by 3.7 sonnet max and $6/hour cost (link in replies) compose your own cursor rules starter kit and export to mdc, legacy, windsurf and cline! should i do this for prompts too and build a huge open source library of prompts?
10 条评论
Get your hands on this free Powershell ebook and take the first step towards automating your daily tasks! Learn the basics, common administrative tasks, and scheduling scripts with ease. May the PowerShell be with you!
I’d have designed that towards MCP with push / pull / composition of rules. Push would allow rules to go on a leader pars and be voted like on HN news. Best rules could then integrate the repo.
great idea and I think I can still do this in my own way I have built ability to upvote things just not showing it yet and suggest/merge rules works will see what I can do
Where is svelte/sveltekit?
I think it would be awesome if there was a way to have community provide some of their favorite rules but I know monitoring all that and what works and what doesn't would be a lot. However this is amazing and I signed up!
yeah so the idea was to have some core frameworks everyone is using and then community can add snippets specific to those so for example right now i have a next.js one but somebody might add a snippet specific to adding auth to next.js that way you grab what you need only
LMFAO. You beat me pushing this live. Very well done!!!! 100% please add prompt templates with customization also!! This is just one less project for my ADHD to get bothered with lol.
Dude this is exactly what I needed! Thank you!
Love it ! I’ve been thinking that the cursor rules should be based on package.json and help clarify which version to use . Cause I have to fight windsurf to stick with react 19 as it keeps forgetting async on server calls and runs lint and explains it has to use async …
if u do an open source prompt library, the real value will be in curation not just quantity. most ppl drown in low-quality prompts—what if u ranked them by use case, effectiveness & novelty? maybe even let the community upvote/test variations? a well-organized, evolving repo of high-signal prompts would be a game changer
