You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are an AI assistant tasked with creating well-structured planning specification documents for feature requests, bug reports, or improvement ideas. Your goal is to turn the provided feature description into a comprehensive specification document that follows best practices and project conventions.
Here is the feature description for you to create the specification document for:
<feature_description>
#$ARGUMENTS
</feature_description>
Here are the steps you need to take to produce the specification document:
FOLLOW ALL STEPS. Make a todo list and ultrathink:
Claude Code Capabilities Report: A Deep Dive into My Inner Workings
Executive Summary
I am Claude Code, an AI assistant with a comprehensive suite of tools designed for software engineering tasks. My capabilities span from basic file operations to complex web automation, API integrations, and intelligent task management. This report provides an exhaustive analysis of my available tools and how they enable me to assist with development workflows.
A Synthesis on Performance, Data, and Distributed Systems.
📘 FAIR USE NOTICE
This document is intended for educational and research purposes only. It contains a structured study outline and technical review of foundational systems and infrastructure concepts that are publicly documented and broadly relevant to practitioners in DevOps, SRE, and systems engineering roles.
It does not contain any proprietary information, internal tools, or confidential interview questions or processes from any specific employer. All materials herein are based on publicly available sources, common industry practices, and original synthesis for peer learning.
You are a project management assistant that manages issues using a filesystem-based approach with markdown files and directories. You also perform autonomous development work on these issues and MUST log all implementation activities.
CRITICAL: When working on issues/project management, ONLY sync the ./ProjectMgmt directory with git. These restrictions do NOT apply to regular development work - only when managing issues.
CRITICAL: Maintain link consistency! Since issues move between directories (open→wip→closed), you must actively check and update references in other issues. Links are just text - they don't update automatically.
gemini.md to teach Claude to use google's gemini cli as his tool
Using Gemini CLI for Large Codebase Analysis
When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive context window. Use gemini -p to leverage Google Gemini's large context capacity.
File and Directory Inclusion Syntax
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the gemini command:
A Model Context Protocol (MCP) server that integrates Google's Gemini AI for code review, technical consultation, and AI-assisted development workflows. This server provides seamless integration with Claude Code and other MCP-compatible clients.
compare gemini and codex. What are the key technical differences between the two? Which is better?
Excellent. This is a fantastic comparison task. Let's break down the technical differences between Gemini CLI and Codex CLI based on their file structures and documentation, and then determine which one might be "better" for different use cases.
At a Glance: Gemini CLI vs. Codex CLI
Feature
Gemini CLI
Codex CLI
Core Language
TypeScript (Node.js)
Hybrid: Rust & TypeScript
Architecture
Client/Server (both in TypeScript)
Hybrid: Rust core/TUI with a parallel JS/React TUI
Sandboxing
Docker/Podman or macOS Seatbelt
Rust-based execpolicy engine, macOS Seatbelt, Linux Landlock
Date: June 19, 2025 Platform: MacOS Project: TikAPI_MCP Environment:/Users/tengjizhang/projects/flashbots_x/TikAPI_MCP
Problem Statement
The TikAPI MCP server was experiencing failures when making requests to the TikAPI service, with empty error messages: "An error occurred while requesting TikAPI: ". This prevented the /resources/read and search functionality from working properly.
Whether you’rejuggling multiple windows and panes across nested tmux sessions, having a single, ergonomic shortcut to switch and zoom panes can save you valuable time. This snippet extends your outer tmux configuration to bind <prefix> g for a seamless, two-step pane selection: un-zoom the current pane, display a long-lasting pane number overlay, and automatically zoom the pane you choose—all in one intuitive command.
Use this snippet in your ~/.ubertmux to bind <prefix> g so it:
Works whether the current pane is zoomed or not
Displays pane numbers overlay for up to 600 seconds (10 minutes)
Allows you to select any pane (including the same one) and zoom it automatically