While this looks professional its clear that the creators have no business background. There is no Privacy Policy, no Terms & Conditions, and who is to say that entered ideas are not saved, used for training or commercialized.
While the creator thinks following is funny on the Contact page I typically respond whenever I want :D its not making a professional impression at all.
What the main page doesnt say is that this is just for JS/TS based development. so overall its wasting visitors time.
Also its a bit unclear why the author pretends to be Cursor <meta name="creator" content="Cursor AI">@danperks
Xo don’t be discouraged. And it appears you aren’t.
I love how u h effort folks re putting towed undertaking filing agentic computing into workflows where we just couldn’t do it with hymns who consume physical resource such as food and love
Anyway, Al effort in this direction are great.
I’ve been working on my thing, Renjis thing, Garotm thing…
I liked to say thank you and well done. Its community projects like that that will grow and help Cursor massively in the long run. So Thank you for your time and will look to use it!
What do you think about having a cursor-rules builder wizard that can be set up step by step? That way, you can consider every detail yourself instead of just copying someone else’s rules.
When I bark at my bots I usually lead in with stern directive:
you are an expert in writing succinct technical documentation and detailed specifications.
Lemme see how this turns out:
(I’ve pointed it at folder @RULES which is the GH clone of @Garotm’s
=====
"Give me a mobile_first webapp that allows my to upload from camera, mic both audio, pics/vids and choose gallery endpoint from my .accounts for imgur, gdrive, github and add a link and description to my personal gallery in app. Make it have sharable links, and a comment section that uses the same commenting input UX as forum.cursor.com such that links to files, pics, other content expand / preview in thread.
Based on this, give me a full spec, plan and detailed project .cursorrules for build, structure, succinctness and context preservation. Create a .ps1 wrapper for all yolo’d commands and save all in /scripts project folder. Create .ps1 setup which sets dirs, .cursurrules, .sql schema file for the backend, use .env for db, account creds. Dry run all dependencies and paths, fail elegantly, maintain detailed development_diary both json and .rmd, headers with versioning, and run a backup operation every time you update development_diary all documentation in .rmd. /log dir appropriately
Always check if exist, if not make - both sql and .ps1
Update workspace file, and refer to @rules for additional reference based on your proposed stack and design.
. Think, clarify propose, confirm, exectute show chain of thought.
@.env @peexi.code-workspace"
Still had issues with it being aligned with the intent… it began down the predictable agentic pitfalls.
I just made a bunch of fixes, I am also going through all of the static files and changing how that is done in my non-forked version of this. Thanks for the feedback, though I really appreciate it. !!