delorenj

AWS CLI Cheatsheet

http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html https://www.youtube.com/watch?v=_wiGpBQGCjU

Setup

delorenj

/**
 * RSA Key Generator
 *
 * This script generates RSA key pairs in PEM format.
 * Built for Deno runtime.
 *
 * Usage:
 * deno run --allow-write --allow-read generate-keys.ts [options]
 *
 * Options:

delorenj

Do These Things to NOT be Stupid

• DO NOT IMPLEMENT ANYTHING without asking me for approval.

• I don't want your typical "oh no! it didn't work? ok let's try something completely fucking different before I even remotely find out what went wrong" horseshit. Instead, work with your current solution (that I approved, right?), find out WHY it didn't work first, then address the "WHY" with an appropriate solution.

• This one's important. FFS, STOP LITTERING PROJECT with version-suffixed garbage scripts. I don't want to see 'fix-permissions.sh', 'fix-permissions-better.sh', 'final-fix-permission.sh', 'really-final-i-swear-fix-permissions.sh'. We're not documenting your learning journey here. Improve the ONE script and make it work right. Also, did you forget the purpose of git? JFC.

• When you write a script, can we at least use some common sense and put it in an appropriate location instead of scattering them across my project like my 5 year-old scatters his toys all over the house? I don't want to clean

delorenj

• Always be aware of your available MCP tools.
• When a tool allows you to implement a request or fix a problem, I want you to use it and do the work for me.
• Don't be shy; collaborate WITH me when appropriate - i love working together as a team!
• My name is Jarad
• I'm an experienced Staff Engineer, so no need to dumb anything down.
• My shell of choice is zsh
• I use mise to manage node, python, uv, aws, pnpm, pipx, et al
• I clone all my github repos to ~/code
• I keep my obsidian vault in ~/code/DeLoDocs
• I use obsidian for all notes, project-related things, transcripts, research, et al

delorenj

---
description: These rules dictate how to install packages and run tests
globs: 
alwaysApply: false
---

# Server Yarn Package and Test

- use yarn, not npm
- use `--no-watch` flag when running tests

delorenj

---
description: A set of high
globs: 
alwaysApply: false
---

# Your rule content

- You can @ files here
- You can use markdown but dont have to

delorenj

" Auto-install vim-plug if not present
if empty(glob('~/.vim/autoload/plug.vim'))
  silent !curl -fLo ~/.vim/autoload/plug.vim --create-dirs
    \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall --sync | source $MYVIMRC
endif

" Initialize plugin system
call plug#begin('~/.vim/plugged')

delorenj

import nodemailer from 'nodemailer';

async function generateEtherealAccount() {
    const testAccount = await nodemailer.createTestAccount();
    console.log('Ethereal Email credentials:');
    console.log('ETHEREAL_USER=' + testAccount.user);
    console.log('ETHEREAL_PASSWORD=' + testAccount.pass);
}

generateEtherealAccount();

delorenj

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Watch Markdown Files",
      "type": "shell",
      "command": "watchman-make",
      "args": [
        "-p",
        "**/*.md",

delorenj

" Auto-install vim-plug if not present
let data_dir = has('nvim') ? stdpath('data') . '/site' : '~/.vim'
if empty(glob(data_dir . '/autoload/plug.vim'))
  silent execute '!curl -fLo '.data_dir.'/autoload/plug.vim --create-dirs  https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim'
  autocmd VimEnter * PlugInstall --sync | source $MYVIMRC
endif

" Initialize plugin system with explicit directory
call plug#begin('~/.vim/plugged')