Garry Tan & Boris Cherny Claude Setupscoding

High-Velocity Multi-File Refactoring Command

Learn the exact terminal configurations, custom slash commands, and multi-file debugging tactics used by Y Combinator's Garry Tan and core Claude engineer Boris Cherny to build software at superhuman speed.

Length~30 words
Token Estimate~41 tokens
Recommended ToolGarry Tan & Boris Cherny Claude Setups
Published2026-08-28
Instagram Reel Breakdown
Watch on Instagram
High-Velocity Multi-File Refactoring Command Instagram Prompt Carousel
@thefutureguyy.ai
Click to load interactive Instagram player

Copy-Paste Prompt Template

Audit all files in the src/api directory. Standardize error responses to use our AppError class, ensure all async functions have proper try/catch blocks with logging, and update corresponding integration tests.

How to Run This Prompt

  1. 1Review the workflow habits of top Silicon Valley developers.
  2. 2Configure auto-approvals for read-only commands in Claude Code.
  3. 3Leverage multi-file refactoring passes to eliminate repetitive chores.

Official Tool for this Prompt

Explore all tools

More Prompts from Recent Reels

All Prompts
TerminalBench Frontier Code Architect
Prompt Carousel

TerminalBench Frontier Code Architect

OpenAI introduces the GPT-5.6 three-tier model family: Sol for frontier coding and reasoning (scoring 91.9% on TerminalBench), Terra as the balanced daily driver, and Luna for ultra-fast, cost-effective high-volume tasks.

Act as a principal software engineer. Analyze the following full-stack architecture for performance bottlenecks, concurrency race conditions, and memory leaks. Provide refactored code with strict TypeScript types, unit tests, and asymptotic complexity analysis.
Context Session State Compressor
Prompt Carousel

Context Session State Compressor

You don't hit Claude limits because you send too many questions—you hit them because every message re-sends the entire preceding conversation history. Learn prompt caching, sub-threading, and context reset tactics.

Summarize our entire ongoing technical session into a concise 150-word state summary. List: Current Goal, Confirmed Architecture Decisions, Unresolved Bugs, and Next Immediate Action. Drop all intermediate logs.