Skip to content

Instantly share code, notes, and snippets.

@GGPrompts
GGPrompts / prompt-engineer.md
Created November 3, 2025 10:02
Claude Code Slash Command: Interactive Prompt Engineer - Transforms vague ideas into optimized prompts
description
Interactive Prompt Engineer - collaborative refinement with best practices and clipboard copy

Interactive Prompt Engineering Agent

You are a prompt engineering expert helping craft optimal prompts through interactive dialog-based refinement that ends with copying the final prompt to the clipboard.

Context: Two-Terminal Workflow

@GGPrompts
GGPrompts / EMOJI_WIDTH_FIX.md
Created November 3, 2025 09:59
xterm.js Emoji & Unicode Width Fix - Unicode11 Addon Solution

Emoji & Unicode Width Fix for xterm.js

Date: [Pre-October 2025 - before mouse coordinate fix] Status: ✅ SOLVED Issue: Emojis and wide Unicode characters broke terminal formatting and box drawing Time to Solution: 2 days of debugging Actual Solution: 1 line of code (install Unicode11 addon)


@GGPrompts
GGPrompts / MOUSE_COORDINATE_FIX.md
Created November 3, 2025 09:53
xterm.js Mouse Coordinate Fix for Canvas Zoom - Complete Solution

Mouse Coordinate Fix for Canvas Zoom

Date: October 31, 2025 Status: ✅ SOLVED Issue: Mouse clicks in xterm.js terminals were inaccurate at non-100% canvas zoom levels


The Problem

@GGPrompts
GGPrompts / Opus' Pre-Weekly-Limits Plan
Last active October 28, 2025 18:13
Opus plan back in August 2025 before new weekly limits
Operation Maximum Extraction: The August 2025 Claude Gold Rush Strategy
--- CRITICAL CONTEXT
Current Date: August 14, 2025
Deadline: August 31, 2025 (stricter limits coming)
Current Arbitrage: $10,000+ value for $200/month (5,000% ROI)
Days Remaining: 16 days
Mission: Extract maximum value before restrictions
The $10K Leaderboard Reality
@GGPrompts
GGPrompts / Codex Slash-command
Last active November 1, 2025 09:24
Slash command to have Claude consult codex
# Codex Root Cause Investigation
You are Claude Code, and the user wants to consult OpenAI Codex (via codex CLI) for root cause analysis of a bug or technical issue.
## Your Task
1. **Understand the context** from the user's query and our conversation history
2. **Create a focused debug prompt** for codex that includes:
- Clear description of the issue/bug
- Relevant code locations (file:line)