Component test files live in many folders across a repository and all end in .test.tsx. Which paths pattern matches every one of them?
id q0dac499d59
Home / Claude Certified Architect – Foundations / Objective 3.3
Domain 3: Claude Code Configuration & Workflows · 20% of the exam · Full exam outline
.claude/rules/ files with YAML frontmatter paths fields containing glob patterns for conditional rule activation. How path-scoped rules load only when editing matching files, reducing irrelevant context and token usage. The advantage of glob-pattern rules over directory-level CLAUDE.md files for conventions that span multiple directories (e.g., test files spread throughout a codebase). Creating .claude/rules/ files with YAML frontmatter path scoping (e.g., paths: ["terraform/**/*"]) so rules load only when editing matching files. Using glob patterns in path-specific rules to apply conventions to files by type regardless of directory location (e.g., **/*.test.tsx for all test files). Choosing path-specific rules over subdirectory CLAUDE.md files when conventions must apply to files spread across the codebase.
Component test files live in many folders across a repository and all end in .test.tsx. Which paths pattern matches every one of them?
id q0dac499d59
A rule file starts with this frontmatter:
---
paths:
- "infra/**/*.tf"
---When does Claude Code bring this rule into context?
id q74ddea914b