← ClaudeAtlas

context-hygienelisted

Knowledge about AI context file locations, staleness patterns, and maintenance rules across 10+ tool ecosystems. Loaded when working with or near context files.
knitli/toolshed · ★ 1 · Data & Documents · score 72
Install: claude install-skill knitli/toolshed
# Context Hygiene When working in this repository, be aware that AI context files (CLAUDE.md, AGENTS.md, Serena memories, Cursor rules, etc.) can become stale and contradictory. This skill helps you maintain context hygiene. ## Known context file locations The authoritative, plugin-wide list of known context files and locations lives at `${CLAUDE_PLUGIN_ROOT}/data/context-files.ini`. Read that file when you need exact paths, globs, or to check whether a particular file is a recognized context file. It is the single source of truth and is updated as new ecosystems are added. At a high level, the plugin recognizes these ecosystems: - **Agent memory files**: `CLAUDE.md` (Claude Code), `AGENTS.md` (universal), `GEMINI.md` (Gemini), `CRUSH.md` (Crush), `.cursorrules` / `.cursor/rules/*.mdc` (Cursor), `.windsurfrules` (Windsurf), `.continuerules` (Continue), `.clinerules` (Roo/Cline), `.aider.conf.yml` (Aider) - **Tool directories**: `.claude/`, `.gemini/`, `.codex/`, `.cursor/`, `.continue/`, `.roo/`, `.serena/`, `.specify/`, `.github/agents/`, `.github/skills/` - **Planning / output**: `claudedocs/`, `specs/`, `plans/`, `planning/`, `info/` - **Config**: `.mcp.json`, `.vscode/mcp.json`, `.vscode/settings.json` This overview is for quick orientation. Do not rely on it for exact-match scanning — use the INI. ## Rules for maintaining context hygiene ### When you modify code After making significant changes (renaming files, changing versions, restructuring modules, adding/rem