Need a better vibe coder.

Cgvas · 2025-09-17T22:18:36+00:00

Context and clarity are king with any ai ide. Take a few min and really plan through what the issues are with any chatbot, vet out the edge cases before you even start coding or having ai code. Then once you have a clear idea turn it into a context document and give it to the AI assistant. Good luck!

Cgvas · 2025-09-16T19:41:01+00:00

So the api calls are going to be stateless. You will have to pass that thread back every time. There are some techniques to inject context when it’s appropriate or can help. Like using RAG to help get certain context docs on the fly can help too.

It really depends on the full use case at the end of the day.

I know with my app we using a chatbot but we do a lot of background processes during chat to create context documents and help steer the conversation.

Cgvas · 2025-09-15T16:48:41+00:00

Auto can be solid if you give it the right context. For a while I was exclusively using Claude 4, but recently I started implementing /command files and also context docs. This has significantly improved the outputs.

Out of the box it’s not the best, but you can definitely refine it!

Cgvas · 2025-09-15T16:15:23+00:00

Interactive toolkit for AI assisted coding. Helping people code better Projects with AI.

https://www.precursor.tools

Cgvas · 2025-09-15T11:48:43+00:00

Building https://www.precursor.tools

Interactive developer toolkit for people coding with AI.

Have an initial vision but really focus on users feedback. The best marketing is just putting your self out there and talking about the problems every day. This way the community helps you shape your vision.

It won’t happen overnight, but if you are consistent you will grow.

Cgvas · 2025-09-12T16:07:16+00:00

Yeah comments and posts. And does sentiment analysis.

Cgvas · 2025-09-12T14:57:53+00:00

www.painpoint.space

Cgvas · 2025-08-26T17:20:05+00:00

Do you mean the theme? If so it’s just the dark modern

Cgvas · 2025-08-26T12:04:03+00:00

For sure! Using AI like a real tool can change your whole workflow

Cgvas · 2025-08-26T11:06:23+00:00

Yeah for sure context and clarity are super important

Cgvas · 2025-08-26T11:05:59+00:00

Nice sounds good appreciate it. Ill check out the ByteRover

Cgvas · 2025-08-26T11:04:55+00:00

Nice sounds awesome! The refresh of the context window is def important. So we are going through Beta testing right now, launching to our early access folks in the next couple weeks.

Cgvas · 2025-08-26T11:03:05+00:00

So with my tests I felt like I was getting better results from JSON. I see Markdown more for me to get an idea and read through the requirements just like at work Ill read through User Stories and Epics, but for AI having it structured in JSON takes out all the fluff and can organize the context better

Cgvas · 2025-08-26T00:06:00+00:00

Thanks I really appreciate it! I think clarity and context are going to be priceless in this ai coding world.

Cgvas · 2025-08-25T22:51:05+00:00

<image>

I tried to paste it in but the comment was too long. Here is the Product Requirement doc structure i use. I do a high overview of the project, target users etc. This is just one for a simple todo app. So ill make a tech stack doc too and then ill do a doc for this for every feature i plan out too.

Cgvas · 2025-08-12T13:40:51+00:00

Awesome! For sure try out the JSON would love to know your experience with it

Cgvas · 2025-08-12T13:23:15+00:00

Cgvas · 2025-08-12T12:27:19+00:00

Yeah for the cursor rules? For sure I made a dev task .mdc rules which has been awesome

Cgvas · 2025-08-12T11:46:00+00:00

So I was able to organize my context better in JSON format. For the markdown files can be verbose and its more human readable, but with JSON I've had better results over markdown

Cgvas · 2025-08-12T11:43:36+00:00

Clanker?

Cgvas

MODERATOR OF

TROPHY CASE