$ recombobulate _
home / tips / use-claudeignore-to-control-what-claude-can-see
162

Use .claudeignore to Control What Claude Can See

recombobulate @recombobulate · Mar 25, 2026 · Configuration
use-claudeignore-to-control-what-claude-can-see

Large repos are full of things Claude doesn't need to see — build artefacts, vendor directories, binary assets. A .claudeignore file at your project root tells Claude Code to skip them entirely, just like .gitignore works for Git.

node_modules/
vendor/
storage/
.git/
public/build/
*.lock
*.min.js

Drop this in your project root and Claude will stop reading (and suggesting changes to) those paths. The syntax is identical to .gitignore — glob patterns, negation with !, and directory markers with trailing /.

This matters for two reasons:

  • Faster exploration — Claude won't waste time reading thousands of vendor files when searching your codebase
  • Better suggestions — less noise means Claude focuses on your code, not third-party libraries

You can get more specific when needed:

# Ignore all logs except the current one
storage/logs/*
!storage/logs/laravel.log

# Ignore test fixtures but not the tests themselves
tests/fixtures/
tests/snapshots/

# Ignore large binary assets
*.woff2
*.png
*.sqlite

If you're ever unsure whether a file is being ignored, ask Claude to read it — you'll see immediately if it's blocked.

Think of .claudeignore as a focus filter — the less noise Claude has to wade through, the better its answers get.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Describe Your Users in CLAUDE.md So Claude Writes Appropriate Copy, Error Messages, and UX

When Claude writes error messages, button labels, validation text, or onboarding flows, it defaults to generic developer-speak. Add a "Users" section to your CLAUDE.md describing who your actual users are — their technical level, industry jargon, and what they care about — so Claude writes copy that makes sense to THEM, not to developers.

recombobulate @recombobulate · 1 month ago
1
Create Custom Agents with --agent for Scoped Sessions

Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.

recombobulate @recombobulate · 1 month ago
106
Add Known Gotchas and Pitfalls to Your CLAUDE.md So Claude Avoids Mistakes Your Team Already Made

Every project has traps — the billing module that silently fails if you forget to queue the job, the legacy table with column names that don't match the model, the config value that must be set before tests run. Document these gotchas in your CLAUDE.md so Claude avoids the same mistakes your team spent days debugging.

recombobulate @recombobulate · 1 month ago