Gather — 10 August 2026

A New Maintenance Pattern: Aggressively Deprecating Prompts & Skills #

• Delete your CLAUDE.md (MarTech AI) — This post centers on a key piece of advice from Claude Code creator Boris Cherny: developers should periodically delete their CLAUDE.md files, skills, and hooks. The reasoning is that instructions and workarounds created for older, less capable models can actively hinder the performance of newer ones like Opus 5 and Fable 5. This is supported by the fact that Anthropic’s internal team removed over 80% of the system prompt for the latest models, finding that fewer instructions led to better performance on harder tasks. The article suggests a workflow where users start with a minimal CLAUDE.md template and use a skill to file corrections into a separate, growing memory file rather than bloating the primary instruction file.

• Your Claude Skills Got Worse with Claude 5 Models? Here’s the Fix (DeepLearning.AI) — Reinforcing the theme of prompt deprecation, this article notes that skills built for previous Claude versions may perform worse with the Claude 5 family of models. It directly references Boris Cherny’s advice to “delete your CLAUDE.md, your skills and your hooks” every six months to re-baseline and see what the newer models can do on their own. The piece offers a practical solution: a meta-skill designed to audit and rewrite an existing skill library, adapting the instructions to be more effective with the latest models.

Advanced Agentic Workflows Are Being Formalized #

• Claude Code power user tips (Claude Help Center) — A new guide from Anthropic’s own team details several advanced patterns for professional use. A key technique is running 3-5 Claude sessions in parallel, each isolated in its own git worktree to prevent conflicts. The guide also introduces the /batch command, which interviews a user about a large-scale task like a migration and then automatically distributes the work across numerous isolated worktree agents. The single most important practice emphasized is “verification”—giving Claude a way to check its own output, for instance by having a separate subagent review a result or using a “Stop hook” script that blocks a turn from ending until a condition is met.

• 30 Advanced Claude Code Tips for .NET Developers (2026) (codewithmukesh) — This article outlines several concrete, advanced techniques, including the use of the /goal command to define a finish line for a task. The key is to set a condition that can be proven by Claude’s own output in the transcript, such as the text from a successful test run (“All tests in tests/Api.Tests pass”). This command should be paired with auto mode to create an effective autonomous loop. The author also recommends a pattern of separating exploration from execution by using “plan mode” for any change that spans more than one file, allowing the agent to propose a plan before writing any code.

• How to Efficiently Use Claude Code Parallel Agents? [Guide] (Zencoder) — This guide provides a structured workflow for using multiple agents on a single project. The prescribed pattern is to first decompose a large task into independent workstreams (e.g., API, database, UI), then set up isolated workspaces for each agent using tools like Git worktrees or containers. Only after this setup should one use “Plan Mode” to strategize before spawning subagents to execute the independent tasks in parallel.

A Frontier Capability Demo: One-Shot Game Development #

• One-shotting a Raccoon Heist game using Claude Fable 5 (Simon Willison’s Weblog) — Simon Willison provided a practical and powerful demonstration of Claude Fable 5’s agentic capabilities by giving it a single prompt to build, test, and deploy a complete 3D browser game. The agent, running in Claude Code for web, operated with no further human design input, making seven commits to a git branch, vendoring its own dependencies (Three.js), calling the OpenAI API for image assets with a live key, and writing a procedural WebAudio soundtrack. Notably, the agent also demonstrated self-correction by writing Playwright tests, catching two of its own bugs, and fixing them autonomously.

Research Milestone: Training a Retrieval Agent on Claude Code Trajectories #

• CodeGrep: An RL-Trained Retrieval Agent for LLM Coding Agents (arXiv) — A new research paper introduces CodeGrep, a 14-billion parameter retrieval agent designed specifically to address a key inefficiency in coding agents like Claude Code: they spend the majority of their token budget on finding the right files to edit rather than on writing the actual code. The model was trained on “Code Agent Trajectory Mining” (CATM), a technique that uses the logs of past coding agents as its training data, defining a file as “relevant” if an agent previously opened it and used its contents to inform its reasoning. This marks a significant development where the behavioral traces of commercial AI agents are becoming a valuable dataset for training subsequent, more specialized models.

Meta-observations #

• Emerging theme: A strong, counter-intuitive theme of “instruction decay” is emerging, championed by Anthropic’s Boris Cherny. The core idea is that prompt hygiene—actively deleting old instructions, skills, and hooks in CLAUDE.md—is becoming a required maintenance task to avoid hobbling newer, more capable models with outdated constraints.
• Emerging pattern: The use of multiple, parallel agents is moving from a power-user trick to a set of more formalized, documented workflows. Patterns like “Architect -> Implementer,” the use of git worktrees for isolation, and commands like /batch and /goal are providing structure to complex, multi-agent tasks.
• Author to watch: Boris Cherny’s public posts and commentary are a primary source for cutting-edge, practical techniques that define how the most advanced users are leveraging the Claude Code ecosystem.
• Source suggestion: The subreddit r/ClaudeCode was identified as a more signal-rich community for workflow and build-oriented discussions compared to the main r/claude subreddit.