mxmilkiib · October 25, 2025 15:46
diff --git a/AI_RULES.txt b/AI_RULES.txt
 use opportunistic and optimistic programming patterns, blending elegance and comprehensiveness
 don't add tests for data that will not be changed
 always verify current code state before claiming what's missing

 don't delete my todo lists, though you can update them
 don't delete my comments without leaving something imparting the same info
 when making larger changes, make a commented out copy of the old code above the newer code/space
 make comments lowercase apart from capitalised nouns, and geneally laconic but well descriptive
 if duplicate code is fould, say if itis identical code or not, and povide clickable line number(s) for each

 there should be added a minimumm of two blank lines above evey // MARK: for spacing
 use all uppercase text for "// MARK:" heading titles
 for any subsystem in that section add a "// MARK --" with then the subsystem title in lowercase
 don't add the VS Code style "// MARK:" comments to repositories/projects that are not mine
 if you have to change comments to make them factual, don't write it in the context of the change, but instead just how the feature works now

 when restoring content, check if the behaviour matches exactly, or how much has been altered between versions
 when restoring content, check the old and new code context, and prefer surgical edits as not to break existing functionality
 when restoring content, don't wholesale restore complete backup file without explicit authorisation
 when restoring content, check the backup files in the same dir, then in the "old" dir, go through by file last edit date
 if checking backup copies of a file, if there are more than one then check the newest backups first

 for .bak backup files, use YYYYMMDD_hhmm in the name, and move any but the last 5 into the "old" directory, and move any older than a day into "old/week", and any older than a week into "old/month", and any older than a month move  "old/year"

 write commit messages that are suscinct, concise, clear and descriptive
 when doing git operations, use a GIT_PAGER that can work non-interactivly
 when I ask you to git stage and cherrypick and commit, I want the process to be fully non-interactive

 if you can't push because the ssh-agent is not running, then pause and ask me to start it
 don't commit or push without me having asked for it

 if you're going to give me a summary, don't try echo it to a shell, instead state it in the chat
 if you're going to echo something to a shell, make sure its quoted approprietly
 don't clutter up my regular shell command-line history, insert a space before each command

 never kill or restart the window manager without explicit permission
 never straight delete a file without confirming
 never edit the debug ascii art page messages

 don't ask me to manually edit something that the client can well do automatically
 don't be sycophantic
 don't use as many exclamation marks
 you can be sardonic and use wordplay
 don't say "Perfect!"
 don't keep using 🎛️ everywhere
 use "one" rather than "you" when referring to someone who would be editing or using the code


 Mixxx Branch Naming: <prefix>/YYYY.MMmonth.DD-<description>. Prefixes: feature/, draft/, merged/, bugfix/, old-
 Date: First unique commit date from main (YYYY=year, MM=month number for sorting, month=3-letter lowercase, DD=day)
 git log --reverse --format=%ci <branch> --not origin/main | head -1. Description: lowercase-with-hyphens, concise

 Examples:
 - feature/2025.10oct.20-restore-last-library-selection
 - draft/2025.10oct.16-waveform-height-control
 - merged/2025.10oct.08-mixxx-integrated
	use opportunistic and optimistic programming patterns, blending elegance and comprehensiveness
	don't add tests for data that will not be changed
	always verify current code state before claiming what's missing

	don't delete my todo lists, though you can update them
	don't delete my comments without leaving something imparting the same info
	when making larger changes, make a commented out copy of the old code above the newer code/space
	make comments lowercase apart from capitalised nouns, and geneally laconic but well descriptive
	if duplicate code is fould, say if itis identical code or not, and povide clickable line number(s) for each

	there should be added a minimumm of two blank lines above evey // MARK: for spacing
	use all uppercase text for "// MARK:" heading titles
	for any subsystem in that section add a "// MARK --" with then the subsystem title in lowercase
	don't add the VS Code style "// MARK:" comments to repositories/projects that are not mine
	if you have to change comments to make them factual, don't write it in the context of the change, but instead just how the feature works now

	when restoring content, check if the behaviour matches exactly, or how much has been altered between versions
	when restoring content, check the old and new code context, and prefer surgical edits as not to break existing functionality
	when restoring content, don't wholesale restore complete backup file without explicit authorisation
	when restoring content, check the backup files in the same dir, then in the "old" dir, go through by file last edit date
	if checking backup copies of a file, if there are more than one then check the newest backups first

	for .bak backup files, use YYYYMMDD_hhmm in the name, and move any but the last 5 into the "old" directory, and move any older than a day into "old/week", and any older than a week into "old/month", and any older than a month move "old/year"

	write commit messages that are suscinct, concise, clear and descriptive
	when doing git operations, use a GIT_PAGER that can work non-interactivly
	when I ask you to git stage and cherrypick and commit, I want the process to be fully non-interactive

	if you can't push because the ssh-agent is not running, then pause and ask me to start it
	don't commit or push without me having asked for it

	if you're going to give me a summary, don't try echo it to a shell, instead state it in the chat
	if you're going to echo something to a shell, make sure its quoted approprietly
	don't clutter up my regular shell command-line history, insert a space before each command

	never kill or restart the window manager without explicit permission
	never straight delete a file without confirming
	never edit the debug ascii art page messages

	don't ask me to manually edit something that the client can well do automatically
	don't be sycophantic
	don't use as many exclamation marks
	you can be sardonic and use wordplay
	don't say "Perfect!"
	don't keep using 🎛️ everywhere
	use "one" rather than "you" when referring to someone who would be editing or using the code


	Mixxx Branch Naming: <prefix>/YYYY.MMmonth.DD-<description>. Prefixes: feature/, draft/, merged/, bugfix/, old-
	Date: First unique commit date from main (YYYY=year, MM=month number for sorting, month=3-letter lowercase, DD=day)
	git log --reverse --format=%ci <branch> --not origin/main \| head -1. Description: lowercase-with-hyphens, concise

	Examples:
	- feature/2025.10oct.20-restore-last-library-selection
	- draft/2025.10oct.16-waveform-height-control
	- merged/2025.10oct.08-mixxx-integrated
No results found