Your AI Tooling Needs Maintenance Too

The .claude/ directory drifts just like production code. Here's how a dedicated folder manager agent keeps your AI tooling configuration clean and working.

Terrance MacGregorTerrance MacGregor
March 26, 2026
2 min read
grok-image-f830215f-7a57-4be6-a44c-2d25d6001b37.png

Your AI Tooling Needs Maintenance Too

The Problem

The `.claude/` directory starts clean. Then you add an agent, rename it mid-project, and forget to update the reference. You add a settings file for local overrides, then another one that partially conflicts with the first. You have agent files that reference Bash tools you removed three sprints ago. The config that was supposed to stay local got checked in.

Nobody audits it because it's "just config." It's not production code. It doesn't ship. It doesn't have tests. So it drifts — slowly, invisibly — until something stops working and you spend an hour figuring out why an agent isn't running.

What We Learned

AI tooling infrastructure drifts just like production code. The `.claude/` directory is the nervous system of your AI-assisted workflow — it controls which agents are available, which tools they can use, how permissions are configured, and how the whole system hangs together.

Neglect it and it slows you down in ways that are hard to diagnose. Clean it up and everything works the way you designed it.

What You Can Do About It

The claude-folder-manager audits the entire `.claude/` directory. It fixes typos in agent file names. It merges conflicting settings files. It removes stale agent entries that reference tools that no longer exist. It checks that every agent in the directory is syntactically valid and that the tools it requests are actually available.

It also reports gaps: workflows that don't have agents, skills that should be commands, features of Claude Code the team hasn't adopted yet. The audit report gives you a clear picture of what's working, what's broken, and what's missing.

Why It Matters

A `.claude/` directory where every file has a purpose, every agent works, and the tooling configuration reflects the actual state of the project. Maintenance takes minutes, not hours.

And when something breaks — which happens less often after a good audit — you know exactly where to look.


At Periscoped, we treat our AI tooling with the same care we give our production systems — because the tools you build with shape the products you build.

Enjoyed this? Explore more on claudeaiai agentproductivity or get in touch.