| 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. |
| { | |
| "$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", |
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.
<%* /*
/**
* 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:Just some tips I gathered over time. All in one easily reachable place so I can share it wherever I want.
Some of it is just for me to copy and paste from :)
| #!/usr/bin/env bash | |
| # CHANGE THIS | |
| ACTUAL_EZA=/usr/local/bin/_eza | |
| args=() | |
| globs=() | |
| while [ "$#" -gt 0 ]; do | |
| arg="$1" | |
| shift |
If you don't care about why or how this works, you can skip right down to Setup Steps
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.
The goal of this Article is to teach you how to find out what takes how much space on your HAOS system.
At the end you should have an interactive way to explore your storage similar to this.

To check the recorder database size/stats I recommend the DBStats app/container.