Discover gists

ZI-main.md
- The main Zotero Integration template
runImport.md
- Template that enables updating literature notes at the click of a button, and much more.
Meta bind button template
- Template for in-note button that executes runImport.md

Chat GPT "DAN" (and other "Jailbreaks")

The Autonomous Agent Prompting Framework

This repository contains a disciplined, evidence-first prompting framework designed to elevate an Agentic AI from a simple command executor to an Autonomous Principal Engineer.

The philosophy is simple: Autonomy through discipline. Trust through verification.

This framework is not just a collection of prompts; it is a complete operational system for managing AI agents. It enforces a rigorous workflow of reconnaissance, planning, safe execution, and self-improvement, ensuring every action the agent takes is deliberate, verifiable, and aligned with senior engineering best practices.

I also have Claude Code prompting for your reference: https://gist.github.com/aashari/1c38e8c7766b5ba81c3a0d4d124a2f58

Writing the "Related Work" Section of a Paper/thesis

By: Chamin Morikawa (https://www.linkedin.com/pulse/writing-related-work-section-paperthesis-chamin-morikawa/)

For most students, writing about what they did on their own is not hard. But writing about others' work - which is what you have to do in the "State of the Art" or "Related Work" section - is quite hard for them. Here are a few guidelines to make this task a bit easier.

The Basics

Let's lay down our assumptions before continuing. I assume that you want to write a "Related Work" section for a research paper or a thesis that describes your approach to solve some problem. Let's also assume that there are other publications that attempt to solve the same problem, but the solutions in them are not perfect. Finally, let's assume that your approach has some difference when compared to those by others, and some improvement (faster, more accurate, easier to afford, etc.).

Introduction

In CS2, when a player is sliding/surfing against some geometry, it's possible that they lose all their momentum/velocity. This is usually called wallbug/rampbug. While the name was inherited from Source 1 games (such as CS:GO, CS:S, TF2,...), rampbugs in CS2 behave much differently from its predecessor. In contrast to source 1 games, it's also possible have the velocity redirected to another direction instead of losing all momentum.

This bug doesn't seem to be common in all source 2 games (HL:A for instance, does not have this bug), and was orignially not present in the very early versions of CS2 Limited Test. Rampbugs become more and more frequent over time, with the Call to Arms update effectively doubling the frequency of these bugs, which is a significant problem for custom gamemodes heavily depending on geometry collision (eg. surf).

Keep in mind that while the player collision hitbox is a box, the images shown below will represent the player as a dot instead for simplicity.

Observati

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

Minecraft Version	Server Jar Download URL	Client Jar Download URL
25w46a	https://piston-data.mojang.com/v1/objects/e61a72ec98fae895ef3e80b05269ae343c42fc0b/server.jar	https://piston-data.mojang.com/v1/objects/b26ec81736baeeb35b4585110ef3b5bf1178c3cf/client.jar
25w45a	https://piston-data.mojang.com/v1/objects/4c0fe96ca002d7049226a740194c8d7114bd5059/server.jar	https://piston-data.mojang.com/v1/objects/d9e25f7e65c41e8fa8c69a9f11a6d5132860af64/client.jar
25w44a	https://piston-data.mojang.com/v1/objects/1ade1ebd6affbfed6dbfb2ce8864cf19efed07ba/server.jar	https://piston-data.mojang.com/v1/o

	#!/usr/bin/env bash
	me=$(basename "$0")
	export me

	function usage(){
	cat >&2 <<ENDOFHELP
	Usage: $me [-r\|--relative] [-c\|--children] [-t\|--tosec] [-h\|--help] TARGET [DESTINATION]

	$me examines rom media files in TARGET and subdirectories
	and for each set of filenames that only differs from a order

	$('#continueButton').click()
	var keeps = $("#pageContainer").parentsUntil('body').toArray().concat($("#pageContainer").children().toArray())
	var divs = $("div:not(#pageContainer)").toArray()
	divs.filter(x => keeps.indexOf(x) < 0).forEach(x => x.remove())
	window.print()

	# Create a new worktree and branch from within current git directory.
	ga() {
	if [[ -z "$1" ]]; then
	echo "Usage: ga [branch name]"
	exit 1
	fi

	local branch="$1"
	local base="$(basename "$PWD")"
	local path="../${base}--${branch}"