Greg Gamel ggamel

name	no-use-effect
description	Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.

No useEffect

Verification-Driven Development (VDD)

Methodology: Iterative Adversarial Refinement

Overview

Verification-Driven Development (VDD) is a high-integrity software engineering framework designed to eliminate "code slop" and logic gaps through a generative adversarial loop. Unlike traditional development cycles that rely on passive code reviews, VDD utilizes a specialized multi-model orchestration where a Builder AI and an Adversarial AI are placed in a high-friction feedback loop, mediated by a human developer and a granular tracking system.

I. The VDD Toolchain

Project Development Standards

Chainlink Issue Tracking (MANDATORY)

All development work MUST be tracked using chainlink. No exceptions.

Session Workflow

# Start every work session
chainlink session start

UV Cheat Sheet for macOS

Installation

Method 1: Official Installer (Recommended)

curl -LsSf https://astral.sh/uv/install.sh | sh

Method 2: Homebrew

<%* /*

/**
 * Obsidian Templater script to build a book from markdown files.
 * 
 * This script automates the process of generating a publish-ready book from a set of Obsidian markdown files.
 * It is designed to work on both Windows and Mac, and can be run from within Obsidian using the Templater plugin.
 * 
 * The script performs the following steps:
 *   1. Expands all Obsidian embeds and links, recursively flattening the book structure into two markdown files:

How I use 1Password to manage SSH keys for multiple GitHub accounts (including on WSL)

If you don't care about why or how this works, you can skip right down to Setup Steps

A little bit of background

These are the considerations I tried to satisfy while researching this solution:

I prefer not to generate new SSH keys for every machine/VM/environment where I use git or SSH. I end up with tons of keys per GitHub account or remote server, and I don't remember which is which.
I want to keep private keys secured somewhere that is not directly accessible on the filesystem. Also try to avoid copying private keys around at all costs.

TypingMind Extension - Export Chats

Exports chat history from the typingmind application.

Changelog

2025-03-23

cleaned up visual styling for the buttons to match the typingmind sidebar

	{
	"$schema": "https://gist.githubusercontent.com/LGUG2Z/78b3dd12a7b7069f1d1c60621fe50730/raw",
	"app_specific_configuration_path": "$HOME/komorebi-application-specific-configuration/applications.mac.json",
	"cross_monitor_move_behaviour": "Insert",
	"cross_boundary_behaviour": "Monitor",
	"default_workspace_padding": 15,
	"default_container_padding": 15,
	"resize_delta": 100,
	"floating_window_aspect_ratio": "Widescreen",
	"floating_layer_behaviour": "Float",

	#!/bin/bash

	# CHANGE THIS
	ACTUAL_EZA=/usr/local/bin/_eza

	display_time="modified"
	sort_time=""

	args=()
	while [ "$#" -gt 0 ]; do

	<!DOCTYPE html>
	<html lang="en">

	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>My Angular from Scratch</title>
	<style>
	.my-component {
	font-family: Arial, sans-serif;