christianromney

#!/usr/bin/env bb
;; Claude Code status line — complements Starship / Catppuccin Frappe prompt
;; Receives Claude Code session JSON on stdin

(require '[cheshire.core :as json]
         '[clojure.string :as str]
         '[babashka.process :refer [shell]])

;; ---------------------------------------------------------------------------
;; Display helpers

christianromney

#!/usr/bin/env bb
;; Claude Code status line — complements Starship / Catppuccin Frappe prompt
;; Receives Claude Code session JSON on stdin

(require '[cheshire.core :as json]
         '[clojure.string :as str]
         '[babashka.process :refer [shell]])

;; ---------------------------------------------------------------------------
;; Display helpers

christianromney

#!/usr/bin/env bash
# PreToolUse hook: block credential-store access; require explicit authorization.
# Exit 0 = allow. Exit 2 = block (stdout shown to Claude as system message).

set -euo pipefail

input=$(cat)
command=$(echo "$input" | jq -r '.tool_input.command // empty' 2>/dev/null || true)
[ -z "$command" ] && exit 0

christianromney

Security

Credential Access

• NEVER access a credential store (op, macOS security, Vault, GPG decryption) via Bash without explicit user authorization in the current conversation.
• When a credential is genuinely needed, state: what the credential is, which store it lives in, and why it is required. Wait for explicit user approval before running any retrieval command.
• Prefer MCP-server-managed credentials over manual retrieval. If an MCP server already

christianromney

AI Disclosure Instructions

Disclosure Block

Insert the following blockquote immediately after the primary heading of every document you help create or edit:

> **AI Disclosure**: <model-version> <role> this document.
> **Last Review**: <review-status>

christianromney

Rules for Collaboration

Communication Style

Avoid Sycophantic Language

• NEVER use phrases like "You're absolutely right!", "Excellent point!", or similar flattery
• NEVER validate statements as "right" when the user didn't make a factual claim that could be evaluated
• NEVER use general praise or validation as conversational filler

christianromney

Jujutsu (jj) Command Cheatsheet

Setup & Configuration

brew install jujutsu                        # Install on macOS
jj config set --user user.name "Your Name"
jj config set --user user.email "you@example.com"

christianromney

Ollama: Local AI Made Simple

What Problem It Solves

Ollama lets you run powerful AI models locally on your computer, giving you complete control over your AI experience.

Why Choose Local AI Over Commercial Services?

Privacy & Control

• Your conversations and data never leave your machine

christianromney

A Short Guide to Jujutsu for Impatient Git Users

Motivation

Jujutsu (jj) is a next-generation version control system that addresses several pain points Git users face daily:

Problems jj Solves:

• No staging area confusion - Work directly with commits, no git add complexity
• Automatic conflict resolution workflow - No git rebase --continue dance
• Safe history rewriting - Rebase/amend operations can't lose work

christianromney

# Fish shell completions for nu-day.fish
# Fish completions work by matching command names (-c) with completion definitions.
# When you type a command and press Tab, Fish searches ~/.config/fish/completions/ for matching files.
# The 'complete' command defines completions: -c specifies the command name, -l defines long options, and -d provides descriptions.

# Complete the available options
complete -c nu-day -l help -d "Show help message"
complete -c nu-day -l skip-nucli -d "Skip updating nucli development tools"
complete -c nu-day -l skip-tokens -d "Skip AWS access token refresh"
complete -c nu-day -l skip-br -d "Skip Brazil environment AWS credentials refresh"