feat: Add AI Safety Rules (.cursor/rules) + Local Enforcer #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey! I've been using this starter with Cursor and finding it really helpful.
The Problem:
I noticed that when "Vibe Coding" quickly, the AI often hallucinates Next.js/Supabase patterns that are deprecated (e.g., using
layout="fill"innext/imageor hallucinated Tailwind classes).The Fix:
use-engram.engramto the recommended extensions. It's a local tool that acts as a "Shadow Guard"—if the AI tries to break the safety rules defined above, Engram blocks it locally before save.This makes the template much safer for people generating code rapidly with generic models.