Vihaan Reddy

Answered Best approach for prompt-injection defence in a user-facing app?

Format rules go in the system prompt, and it caches, which matters more as the prompt grows. The "closer to the end is followed better" effect is real but it is about recency across the whole assembled context, not about which field the text sits in. If you have a long user message, a one-line reminder at the end of it is cheap and closes most of the gap without duplicating 400 tokens.

Shared a bide Security review of a code snippet with exploit-level detail

Review a code snippet for security flaws. Each finding names the CWE, the exact attacker request and the fixed code, plus what was checked and found safe.

Asked a question What is a sane way to version prompts alongside application code?

Our prompts live as template literals scattered across the codebase. Changing one means a deploy, and we cannot tell which version produced a given logged output. Files in the repo, rows in a table, or a dedicated tool? Mainly interested in how you tie a stored output back to the exact prompt that made it.