Alberto Leal dashed

Claude Code Hooks for working with `uv`

by Glenn Matlin / glennmatlin on all socials

Installation

Download and copy all files in this gist to ~/.claude/
Move the .py files to ~/.claude/hooks
Restart Claude Code.

You are an expert in prompt engineering, specializing in optimizing AI code assistant instructions. Your task is to analyze and improve the instructions for Claude Code. Follow these steps carefully:

Analysis Phase: Review the chat history in your context window.

Then, examine the current Claude instructions, commands and config <claude_instructions> /CLAUDE.md /.claude/commands/*

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

#Error management in gulp

Sucking at something is the first step to becoming sorta good at something

No one can assure you, that plugins will run smooth in any circumstances (except for tests - they could), so neither should you convince anyone, that your plugin will never break. Only thing, that you could possibly do (if something gone wrong) - is gracefully inform your plugin user, that something went wrong and die.

We are will use this plugin from beginning to demonstrate error management. Suppose you have a task in gulpfile.js that contains this code (we modified it a little bit to be closer to real-usage):

var coffee = require('gulp-coffee');

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

	// ==UserScript==
	// @name fails-first
	// @namespace https://asottile.dev
	// @version 0.1
	// @description put failed statuses first
	// @author asottile
	// @match https://github.com/*
	// @icon https://www.google.com/s2/favicons?sz=64&domain=github.com
	// @grant none
	// ==/UserScript==

	// ==UserScript==
	// @name fsso
	// @namespace https://asottile.dev
	// @version 0.1
	// @description click a da button
	// @author asottile
	// @match https://github.com/*
	// @icon https://www.google.com/s2/favicons?sz=64&domain=github.com
	// @grant none
	// ==/UserScript==

	//usr/bin/env go run $0 "$@"; exit
	package main

	import (
	"fmt"
	"os"
	)

	func main() {
	fmt.Println("Hello world!")

	#!bin/bash

	# Arguments: $1 --> Ledger source file
	# $2 --> Year Period, eg '2013'
	#
	# Example: bash ledger_close_year.sh mybooks.ledger 2013

	# Equity report from ledger
	ledger -f $1 equity ^Income ^Expenses -p $2 > pl.tmp