aaronedev

-- =============================================================================
-- lightline to lualine theme converter
-- Author: shadman
-- License: MIT License
-- =============================================================================

-- Instructions

-- 1. Source this file in neovim with lightline installed
-- 2. execute :lua light2lualine_theme_converter('theme_name')

aaronedev

CLAUDE.md - Universal Development Principles

This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.

Required Tools and Research Methods

1. Mandatory MCP Tool Usage

BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.

aaronedev

1. Go to about:config, enable these flags:
   • toolkit.legacyUserProfileCustomizations.stylesheets
   • layout.css.color-mix.enabled
2. Go to about:support, look for profile folder.
3. Add the CSS below to chrome/userChrome.css inside the profile folder.

aaronedev

#!/usr/bin/env bash
set -e

declare -i last_called=0
declare -i throttle_by=4

@throttle() {
	local -i now=$(date +%s)
	if (($now - $last_called > $throttle_by)); then
		# delay execution

aaronedev

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

aaronedev

local M = {}

-- Cache for module state
local state = {
  buf = nil,
  win = nil,
  ns = nil,
  width = 34,
  uses_mousemoveevent = vim.o.mousemoveevent,
}

aaronedev

{
  "vim.showMarksInGutter": false,
  "vim.foldfix": true,
  "vim.surround": true,
  "vim.easymotion": true,
  "vim.easymotionKeys": "asdghklqwertyuiopzxcvbnmfj",
  "vim.leader": "<space>",
  "vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": [":", "w", "<CR>"],

aaronedev

Semantic Branch Names

See how a minor change to your branch name style can make you a better programmer.

Format: <type>/#<issueNumber>-<alias>

Example