Explore the .claude directory changedclaude-directory
Nearest release: v2.1.293, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 7 Oct 2026 18:41 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 7 Oct 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+5added
Lines−5removed
From line
160
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits42to this page, all time
The whole hunk
from line 160, old and new numbered
/
from line 160
160160 icon: 'folder',
161161 color: '#9B7BC4',
162162 oneLiner: 'Topic-scoped instructions, optionally gated by file paths',
163 when: <>Rules without <C>paths:</C> load at session start. Rules with <C>paths:</C> load when a matching file enters context</>,
163 when: <>Rules without <C>paths:</C> load at session start. Rules with <C>paths:</C> load when Claude reads, writes, or edits a matching file</>,
164164 description: [<>Project instructions split into topic files that can load conditionally based on file paths. A rule without <C>paths:</C> frontmatter loads at session start like CLAUDE.md; a rule with <C>paths:</C> loads only when Claude reads, writes, or edits a matching file.</>, <>Like CLAUDE.md, rules are guidance Claude reads, not configuration Claude Code enforces. For guaranteed behavior use <A href="/docs/en/hooks">hooks</A> or <A href="/docs/en/permissions">permissions</A>.</>],
165165 tips: [<>Use <C>paths:</C> frontmatter with globs to scope rules to directories or file types</>, <>Subdirectories work: <C>.claude/rules/frontend/react.md</C> is discovered automatically</>, 'When CLAUDE.md approaches 200 lines, start splitting into rules'],
166166 docsLink: '/en/memory#organize-rules-with-claude/rules/',
from line 172
172172 color: '#9B7BC4',
173173 badge: 'committed',
174174 oneLiner: 'Test conventions scoped to test files',
175 when: <>Loaded when Claude reads a file matching the <C>paths:</C> globs below</>,
175 when: <>Loaded when Claude reads, writes, or edits a file matching the <C>paths:</C> globs below</>,
176176 description: <>An example rule that only loads when Claude is working on test files. The <C>paths:</C> globs in the frontmatter define which files trigger it; here, anything ending in .test.ts or .test.tsx. For other files, this rule is not loaded into context.</>,
177177 example: `---
178178paths:
from line 193
193193 color: '#9B7BC4',
194194 badge: 'committed',
195195 oneLiner: 'API conventions scoped to backend code',
196 when: <>Loaded when Claude reads a file matching the <C>paths:</C> glob below</>,
197 description: <>A second example showing a rule scoped to backend code. The <C>paths:</C> glob matches files under src/api/, so these conventions load only when Claude is editing API routes.</>,
196 when: <>Loaded when Claude reads, writes, or edits a file matching the <C>paths:</C> glob below</>,
197 description: <>A second example showing a rule scoped to backend code. The <C>paths:</C> glob matches files under src/api/, so these conventions load only when Claude is working on API routes.</>,
198198 example: `---
199199paths:
200200 - "src/api/**/*.ts"
from line 601
601601 icon: 'folder',
602602 color: '#9B7BC4',
603603 oneLiner: 'User-level rules that apply to every project',
604 when: <>Rules without <C>paths:</C> load at session start. Rules with <C>paths:</C> load when a matching file enters context</>,
604 when: <>Rules without <C>paths:</C> load at session start. Rules with <C>paths:</C> load when Claude reads, writes, or edits a matching file</>,
605605 description: 'Same as project .claude/rules/ but applies everywhere. Use this for conventions you want across all your work, like personal code style or commit message format.',
606606 docsLink: '/en/memory#organize-rules-with-claude/rules/',
607607 children: []
No line in this hunk matches that.