- Tubelator AI
- >
- Videos
- >
- Science & Technology
- >
- How to Improve AI Output Quality in Coding Editors Using Cursor and Windsurf Settings
How to Improve AI Output Quality in Coding Editors Using Cursor and Windsurf Settings
Learn how to increase AI output quality in coding editors like VS Code using simple rules files with cursor and Windsurf settings. Discover the importance of providing concrete context for greater reliability and effectiveness in AI-assisted coding.
Install Tubelator On Chrome
Video Summary & Chapters
No chapters for this video generated yet.
Video Transcript
context is ke for AI here's what people
frequently forget AI can't magically
guess everything when building Real
World products you can't rely on AI to
just guess everything correctly the
secret is not about better prompts or
more powerful models it's about concrete
context today I'll show you how one
simple rules file can transform your AI
coding assistant into a much more
reliable development partner whether
you're using vs code cursor or WI or any
other coding editors that supports a
similar feature let's dive straight in
first of all these are context that get
included on all of your AI chats whether
it's your composer runs your chat your
wind Cascades your GitHub co-pilot edit
sessions as previously mentioned the
three major code editors all have a
similar feature here but just stored in
different files vs code keeps this
inside the GitHub Code Pilot
instructions cursor there's a cursor
rules files at the root of the room
repository and wind surf there's a do
wind surve rules that has just been
recently released let's create a new
chat when we take type anything short
hello how's it going this context gets
included directly as part of that prompt
automatically just as something obvious
let's say ho ho ho at the beginning of
the output every single time then we can
save the file and type this into cursor
chat how's it going you'll see it always
says ho ho ho there's a very easy way to
verify whether your rules file is
working correctly or not you'll notice
one key rule I've applied at the
beginning is this line every time you
choose to apply a rule explicitly state
the rule in the output you can
abbreviate the rule description to a
single word or phrase this is to make
sure that I can clearly see in the
output which rules has been followed
specifically for each one of the edit
sessions just so that I can easily
sanity check oh has it missed anything
