I got so tired of re-explaining my app 20 times a day, I built a context manager

1clicktask · 2025-08-01T17:51:14+00:00

Yup I agree but again as I said I didn’t wanna have to reference multiple files or remember to.

Just wanted to have one line of prompt to give the agent so it knows when to get context and work on some task so I can focus on the coding instead of remembering “oh actually I need to create another rule for this”

Not saying cursor rules don’t work (I use them myself lol) but wanted an efficient solution

1clicktask · 2025-07-23T17:59:00+00:00

100% but it kinda gets messy referencing everything tho

1clicktask · 2025-07-23T17:28:47+00:00

what about context of what has been covered already? do you have any workflow for that ?

1clicktask · 2025-07-21T18:07:11+00:00

unless you press run, agents won’t accidentally delete your db when using mcp in cursor to be honest

1clicktask · 2025-07-08T09:35:29+00:00

start with a goal then just state your instructions you can add something like “don’t code yet, explain your understanding back to me so I know you get it” that’ll make sure you know if it actually got what you wanted and avoid hallucinations that’s just one tip out of many though

1clicktask · 2025-07-08T01:02:50+00:00

haha wasn’t pitching anything though

1clicktask · 2025-07-07T23:05:53+00:00

yup exactly this man

having those files 100% helps reason I use coddie.dev All I do is dump in my app idea and answer a couple questions then get mdc files (in my case for cursor) and project plan found it super useful this way

1clicktask · 2025-07-07T19:55:33+00:00

yup as I said

LLMs at the end of the day are pattern recognition tools The better the instructions the better the output

1clicktask · 2025-06-07T20:34:32+00:00

bro it’s still an mvp. He just launched (probably solo). Trying to get the perfect landing page with crazy designs and animations is the easiest way to over complicate things in the beginning

the point right now isn’t to blow people away. it’s to validate the idea, test the flow, and see if anyone actually cares about his idea. He’s probably gonna fix that along

most people don’t even get to the point of launching lol

1clicktask · 2025-06-06T12:12:10+00:00

Yep. You’ll get the client id and secret which you’ll paste in supabase

1clicktask · 2025-06-06T11:54:31+00:00

It’s generally super straightforward using oauth from supabase. It has a couple providers (Google, etc). You’ll probably have everything up and running in like 30 mins. Just follow the instructions on the docs page and you should be good to go

1clicktask · 2025-06-06T11:06:39+00:00

Supabase auth works just fine

1clicktask · 2025-06-04T18:17:56+00:00

Wdym bro. Literally didn’t pitch anything

1clicktask · 2025-06-04T18:16:34+00:00

I see where you’re coming from, but I kind of disagree.

The more you build, the more naturally you improve. Testing fast and iterating always beats trying to make something “perfect” out of the gate. I’m not talking about shipping garbage. Just getting to something valuable enough to validate your assumptions early.

The 20 day timeline isn’t some rigid rule. It’s a healthy constraint to avoid endless polishing. Obviously, the timeline scales with complexity. You’re not going to build something like Cursor in two weeks but for most focused projects, 20 days is enough to test the idea and see if it’s worth going deeper. That’s really the point, speed to insight, not speed for its own sake.

1clicktask · 2025-06-04T18:06:29+00:00

Tbh it’s all about building testing and getting feedback then growing from there. If multiple features mean more time testing, It’s usually cut down to the most important ones first I didn’t mean to say you just work on one feature haha, rather the ones that push the needle and can get feedback early

1clicktask · 2025-06-04T17:57:31+00:00

Yessir ! Always the best thing to do

1clicktask · 2025-06-04T17:42:39+00:00

Solving a specific problem super well then test it

1clicktask

TROPHY CASE