steipete

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

victorb

Guidelines to follow at all times:

• Always keep your changes limited to what explicitly mentioned
• Don't use any 3rd party libraries/framework/code unless explicitly requested
• Focus on simplicity both in terms of design/architecture and implementation
• Code has to be easy to reason about, and easy to extend/change in the future
• Validate that you understand the question correctly by re-iterating what's asked of you but with different words
• Double-check your work before committing, think outside the box and consider tradeoffs and pros/cons.
• Consider how maintainable your changes will be, always try to create as maintainable code as possible
• Take a step back if needed and retry if you can think of a better solution

reborg

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

• The link in the table of content jumps at the copy of the answer on this page.
• The link on the answer itself points back at the original post.

Table of Content

alirobe

### 
###
### UPDATE: For Win 11, I recommend using this tool in place of this script: 
### https://christitus.com/windows-tool/
### https://github.com/ChrisTitusTech/winutil
### https://www.youtube.com/watch?v=6UQZ5oQg8XA
### iwr -useb https://christitus.com/win | iex
###
### OR take a look at 
### https://github.com/HotCakeX/Harden-Windows-Security

dylanmcdiarmid

.vimrc
" Map leader to comma
let maplocalleader=","

" Toggle this for vim-sexp to not go into insert mode after wrapping something
let g:sexp_insert_after_wrap = 0
" Toggle this to disable automatically creating closing brackets and quotes
let g:sexp_enable_insert_mode_mappings = 1

Vocab

XVilka

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

ghoseb

;;
;; NS CHEATSHEET
;;
;; * :require makes functions available with a namespace prefix
;;  and optionally can refer functions to the current ns.
;;
;; * :import refers Java classes to the current namespace.
;;
;; * :refer-clojure affects availability of built-in (clojure.core)
;;   functions.