I just created https://t.co/xSpOBHQaCb, a tool to generate a TSConfig file for your new TypeScript project based on a few user inputs⚙️
It's inspired by @mattpocockuk's TSConfig Cheat Sheet.
Check it out!
@RhysSullivan This is a very real concern. I was building a vibe coded app recently and the auth middleware for the server endpoints generated from Claude didn’t even validate the JWT. It just decoded the sub from the payload if verification failed lol. I was shocked
We have the options of .cursor rules folder, CLAUDE dot md, and now GEMINI dot md files. I feel like there needs to be a standard across all of them otherwise we're going to have 10 md files all containing the same thing
We have the options of .cursor rules folder, CLAUDE dot md, and now GEMINI dot md files. I feel like there needs to be a standard across all of them otherwise we're going to have 10 md files all containing the same thing
Proper tests and CI are critical for this kind of workflow, even in the early stages of a project/POC. These are your indicators that the LLM didn’t completely screw up the task
This workflow is insane. Setup Claude app to your GitHub repo, create issues with desired changes, and have Claude understand the problem and open a PR.
I don’t even have to have my editor open, I could do this on my phone, and have multiple instances running at the same time
all of the context/changes requested are persisted in the ticket details. Makes it easier to track and reference later. The skill of being able to articulate what you want in natural language has never been more useful
@mitsuhiko Curious how this works with conflicting changes since these are running in parallel. Do you specify that in your markdown file with instructions? Do you also isolate changes to different branches or have all agents committing to the same branch?
@anothercohen Same here. Trialed it several years ago and there hasn’t been much changes since trying it again a week ago. I’ve gone back to the Apple Watch and started using the Bezel app. It’s great
@adamwathan Really love Supabase but I found you start worrying more about security than building due to a number of things. For me it was things like row level security policies, having your whole db schema public by default in the rest/gql endpoints, stuff like that