Alex Mabe melonamin

Claude Code with CLIProxyAPI on Linux and fish

This setup keeps two separate commands:

claude uses native Claude authentication and keeps Claude.ai connectors available.
claudex sends Claude Code requests through a local CLIProxyAPI instance and uses a Codex-backed model.

CLIProxyAPI listens only on 127.0.0.1 in this setup. Its client token is stored in a private configuration file and is read by the fish function at runtime.

Prerequisites

Mandatory Skill Activation Hook for Claude Code

Forces Claude to evaluate and activate relevant skills before implementation. By default, Claude Code often ignores available skills entirely and proceeds with generic responses instead of leveraging specialized skill knowledge.

Problem Solved

Claude Code frequently skips skill evaluation and jumps straight to implementation, missing out on specialized context and workflows that skills provide. This hook injects a system reminder on every prompt submission that enforces a three-step sequence: evaluate → activate → implement.

Files Required

Write ultra-precise prompts — state edge cases, implicit assumptions, and concrete examples; Claude can’t guess them.
Ask Claude to “ultrathink” when deeper multi-step reasoning is needed.
Use planning mode (Shift+Tab twice) or another model for high-level design before coding.
Delegate with the Task tool — spawn specialist sub-agents (design, research, etc.) to tackle parts in parallel.
Make Claude RTFM first — link docs or start a research Task so it learns the latest best practices before scaffolding.
Start new threads often — run /clear to reset context and cut drift when you switch topics.
Restart with --resume to branch without losing work.
Use claude --dangerously-skip-permissions" to avoid constant prompts, but 1) it's probably better run in a container 2) mind the limits, it will eat them fast
Dictate long prompts with voice-to-text; Claude copes well with messy transcripts.
Stage early, stage often — git add after each good turn to simplify rollbacks.

Keybase proof

I hereby claim:

I am melonamin on github.
I am melonamin (https://keybase.io/melonamin) on keybase.
I have a public key whose fingerprint is 0A39 2EAC 485F 8A9B 7446 75D9 F99F 0A92 2E8C 58EE

To claim this, I am signing this object:

	#!/usr/bin/env python3

	import sys
	import os
	import json
	import tomllib
	from pathlib import Path

	def normalize_color(color):
	"""Convert 0xRRGGBB or #RRGGBB to #RRGGBB format"""

	[package]
	name = "generate-datafusion-parquet"
	version = "0.1.0"
	edition = "2021"

	[dependencies]
	datafusion = "49"
	tokio = { version = "1", features = ["rt-multi-thread", "macros"] }

	import Foundation
	import Photos

	func requestPhotoLibraryAccess(completion: @escaping (Bool) -> Void) {
	PHPhotoLibrary.requestAuthorization { status in
	completion(status == .authorized)
	}
	}

	func fetchFavoritePhotos(startDate: Date) -> PHFetchResult<PHAsset> {

	#!/bin/bash

	# Required parameters:
	# @raycast.schemaVersion 1
	# @raycast.title FSNotes Create New Note
	# @raycast.mode silent

	# Optional parameters:
	# @raycast.icon ./images/fsnotes-icon.png
	# @raycast.packageName FSNotes

	git init --bare $HOME/.cfg
	alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'
	config config --local status.showUntrackedFiles no
	echo "alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'" >> $HOME/.bashrc

	- Haken
	- Flying Colors
	- John Petrucci
	- The Dear hunter
	- The Winery Dogs
	- Lunatica
	- Devin Townsend
	- Therion (Beloved Antichrist)
	- Toehider
	- Aurora