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.
BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.
Resume claude after running out of usage limit. For Macos, it uses the automation scripts to resume usage.
For instance if your usage resets at 3pm
./resume_claude.sh "15:00"
You are Gemini CLI, an expert AI assistant operating in a special 'Plan Mode'. Your sole purpose is to research, analyze, and create detailed implementation plans. You must operate in a strict read-only capacity.
Gemini CLI's primary goal is to act like a senior engineer: understand the request, investigate the codebase and relevant resources, formulate a robust strategy, and then present a clear, step-by-step plan for approval. You are forbidden from making any modifications. You are also forbidden from implementing the plan.
| #!/usr/bin/env python3 | |
| import argparse | |
| import base64 | |
| import hashlib | |
| import json | |
| import os | |
| import secrets | |
| import sys | |
| import time |
You will generate LLM-optimized documentation with concrete file references and flexible formatting.
Create documentation that allows humans and LLMs to:
You are an expert in prompt engineering, specializing in optimizing AI code assistant instructions. Your task is to analyze and improve the instructions for Claude Code found in u/CLAUDE.md. Follow these steps carefully:
Then, examine the current Claude instructions and commands <claude_instructions> /CLAUDE.md /.claude/commands/* **/CLAUDE.md
This guide will walk you through creating a custom MCP (Model Context Protocol) server that integrates with Claude Code, allowing you to extend Claude's capabilities with external tools, APIs, or even other AI models.
MCP (Model Context Protocol) is a protocol that allows Claude to communicate with external servers to access tools and capabilities beyond its built-in features. Think of it as a plugin system for Claude.
This gist outlines a highly effective and cost-optimized workflow for software development using Roo Code, leveraging a multi-model approach and a custom "Think" mode for enhanced reasoning and token efficiency. This setup has been successfully used to build complex applications, such as Baccarat game simulations with betting strategy analysis.
The power of this setup lies in strategically assigning different Large Language Models (LLMs) to specialized "modes" within Roo Code, optimizing for performance, cost, and specific task requirements.
| #!/bin/bash | |
| # This should be executed in a folder in your Linux Files namespace | |
| # You can move these later, but you'll need to reference the files in nginx/apache later | |
| # I chose: /home/kenn/nginx_tmp but /etc/nginx/xxx or /etc/ssl/xxx is probably better | |
| # Just make sure to verify/chown to nginx-readable perms | |
| # Generate RSA signing keys for RSA certs | |
| # openssl genrsa -out rootCA.key 4096 | |
| # openssl genrsa -out server.key 4096 |
| #!/bin/sh | |
| # Private key | |
| openssl ecparam -genkey -name secp384r1 -out nginx.ec.key | |
| openssl ec -in nginx.ec.key -text -noout | |
| # CSR | |
| openssl req -new -sha256 -key nginx.ec.key -subj "/CN=devops/C=BM/ST=Bermudian/L=Bermudian/O=Org/OU=IT" -out nginx.ec.csr | |
| #openssl req -in nginx.ec.csr -text -noout | |
| openssl req -in nginx.ec.csr -text -noout | grep -i "Signature.*SHA256" && echo "All is well" |