Sleeyax sleeyax

name	cook
description	Code in an Opus session, using Fable subagent to plan and Codex to write code and finally Fable subagent review for every task.
user-invokable	true

Implement all tasks given to you. Use a Fable high subagent to write a plan.md for each task. Require my approval for all plans before beginning implementation. Then write all code by calling out to codex exec for each task using codex --yolo exec -c model="gpt-5.5" -c model_reasoning_effort="high" < plan.md (allow cmd to run for up to 20 minutes), then review code (using a subagent with Fable high) and smoke testing new features (usage a subagent with Opus medium) by running pnpm dev and doing real requests, before committing and pushing, then moving onto next task. Remember that every subagent or codex session is completely independent and must be given the full context it needs to complete its work.

Drizzle ORM PostgreSQL Best Practices Guide (2025)

Latest Drizzle ORM features and optimal schema patterns

Major 2025 Update: PostgreSQL now recommends identity columns over serial types. Drizzle has fully embraced this change.

import { pgTable, integer, text, timestamp, varchar } from 'drizzle-orm/pg-core';

Preparations

Install Virtual Machine Manager - probably in your repo with the name virt-manager
Install any other requirements for virtualization on your distro
Ensure any Virtualization options is enabled in Bios.
Get a windows11 iso download here
Get virtio drivers iso download here

Setup

Edit -> Preferences -> Enable XML editing
Create the VM but before Finish - check Customize conf before install
@Overview

Using `@react-pdf/renderer` v3.0.1 with React 18

Introduction

When I tried to use the @react-pdf/renderer package (version 3.0.1) with a React 18 app, two problems arose. In this article, I'll describe those problems and tell you how I solved them.

Update: Here's a video demonstration of the problems and solution described in this article: https://youtu.be/YZP5r7Uy_bU

Problem 1: Dependency Conflict

Go development environment on Windows with MSYS2

Normally, it is sufficient to grab the Go MSI installer from the website in order to set up the toolchain. However, some packages that provide Go wrappers for C libraries rely on cgo tool, which in turn, needs the GCC toolchain in order to build the glue code. Also, 3rd-party dependencies are usually hosted on services like GitHub, thus Git is also needed. This mini-guide illustrates how to setup a convenient development environment on Windows using MSYS2.

	'use client';

	/*
	This file is adapted from next-themes to work with tanstack start.
	next-themes can be found at https://github.com/pacocoursey/next-themes under the MIT license.
	*/

	import * as React from 'react';

	interface ValueObject {

	// Types for the result object with discriminated union
	type Success<T> = {
	data: T;
	error: null;
	};

	type Failure<E> = {
	data: null;
	error: E;
	};

	version: '3.4'

	services:
	mail:
	image: inbucket/inbucket:latest

	environment:
	NODE_ENV: production
	ports:
	- 9000:9000

	{
	"PX1": "no_script",
	"PX2": "js_bootstrap",
	"PX3": "domready",
	"PX4": "fingerprint",
	"PX6": "nav_timing",
	"PX7": "incognito",
	"PX8": "score_session",
	"PX9": "score_impression",
	"PX10": "ui_interaction",

	package transform

	import (
	"reflect"
	"strings"
	"time"
	)

	const (
	tagName = "firestore"