Once a codebase grows large enough you should create specialized markdown files (e.g. database_setup.md documenting table structure, RLS policies, mandatory/nullable fields, and SQL queries) that you tag whenever working on that area, acting as internal documentation that gives the model everything it needs.

normativepending

Speaker

David

Evidence Quote

anytime you're doing anything related to the database you can just tag this file... it's like Internal Documentation for each part

Source

I spent 400+ hours in Cursor, here’s what I learnedDavid Ondrej
Created: 6/18/2026, 2:32:09 PM

My Notes

Loading notes...