Anthropic CCA-F Questions & Answers

Other packages with the same extension remain uncovered. Tests under another package path remain invisible even though they end in the expected suffix. Tests use different package directories but all names end in .test.ts. Instead, use a matching file-type glob in frontmatter rather than one directory rule.

The test rule should activate from matching file paths. An absent manual command leaves an otherwise matching test file unprotected by style guidance. Tests use different package directories but all names end in .test.ts. Instead, use a matching file-type glob in frontmatter rather than one directory rule.

Production modules would receive test-only conventions. Every production TypeScript file would receive assertions and fixture guidance irrelevant to its behavior. Tests use different package directories but all names end in .test.ts. Instead, use a matching file-type glob in frontmatter rather than one directory rule.

A different extension still omits nested TypeScript paths. Changing only the extension does not add recursion into src/components/deep. Checking the rule against a real nested path confirms activation before developers rely on the requirement in a deep component. A rule applies to src/*.ts but does not cover src/components/deep/*.ts.

A declared path filter cannot cover files that do not match. The conditional loader evaluates paths mechanically, so deep files remain unmatched by the old pattern. Single-level path patterns do not necessarily match nested files; recursive globs are needed for deeper directories. Instead, use a recursive path glob and test it against a nested source path before relying on the rule.

Global activation removes the intended conditional scope. Making the rule unconditional reintroduces noise for unrelated source trees rather than fixing recursion. Single-level path patterns do not necessarily match nested files; recursive globs are needed for deeper directories. Instead, use a recursive path glob and test it against a nested source path before relying on the rule.

Keyword activation misses relevant files and can match unrelated tasks. Prompts can omit the keyword while touching sensitive handlers or mention it during unrelated analysis. Repository-wide Python filters impose payment rules on unrelated scripts and increase noise during otherwise legitimate changes.

This preserves the original overbroad activation. A repository-wide Python pattern continues to inject payment checks into tools and services. A rule intended for payment handlers loads for every .py file in the repository. Instead, narrow the paths field to the payment package. Repository-wide Python filters impose payment rules on unrelated scripts and increase noise during otherwise legitimate changes.

Team members would not share the sensitive rule. Private preferences do not impose consistent requirements on other engineers' payment modules. A rule intended for payment handlers loads for every .py file in the repository. Instead, narrow the paths field to the payment package.

A single developer's preferences do not govern the repository. User-memory settings are not committed and cannot be audited with the generated source. The same schema naming standard applies to generated clients in five modules. Instead, create one shared rule matching all client-generation paths.

Unrelated source code would receive generated-client conventions. The rule would influence handwritten code with no client-generation naming requirement. One shared matching rule can express a common naming contract over several generated-client directories. The same schema naming standard applies to generated clients in five modules.

Multiple copies drift as conventions change. Each copied file can become stale after a naming-policy change, producing divergent clients. The same schema naming standard applies to generated clients in five modules. Instead, create one shared rule matching all client-generation paths.

A global file makes the activation even broader. Moving the rule to root instructions widens the scope across the entire repository. A markdown-only style rule triggers during SQL migration edits. Instead, give documentation rules a markdown path filter. Markdown style conventions should activate for documentation files rather than executable SQL migration scripts.

Titles do not implement file-based conditional loading. The loader cannot infer Markdown-only applicability from a human-readable title. Markdown style conventions should activate for documentation files rather than executable SQL migration scripts. A markdown-only style rule triggers during SQL migration edits.

SQL migrations still receive the documentation style rule. Including SQL files still causes a prose formatting rule to affect migrations. Markdown style conventions should activate for documentation files rather than executable SQL migration scripts. Instead, give documentation rules a markdown path filter.

Body wording does not fix a false path match. Changing the prose has no effect until the frontmatter selects the actual modified path. Developers claim a rule is active although its pattern does not match the changed directory. Instead, check the frontmatter glob against the actual path.

Globalizing the rule hides the original pattern defect. Removing the filter silently activates a rule for files that never needed it. Developers claim a rule is active although its pattern does not match the changed directory. Instead, check the frontmatter glob against the actual path.

Globs operate on actual paths, not intuition. A superficially similar directory name may fail an exact or recursive glob pattern. Developers claim a rule is active although its pattern does not match the changed directory. Instead, check the frontmatter glob against the actual path.

Automatic activation outside iOS defeats the scoped requirement. Automatic global activation would consume context even if no iOS source is being examined. Conditional guidance prevents platform-specific requirements from occupying the context of unrelated backend tasks. An iOS-specific policy consumes tokens during backend API edits.

Backend tasks would still receive irrelevant rules. Server code would inherit mobile-platform constraints with no corresponding runtime relevance. Conditional guidance prevents platform-specific requirements from occupying the context of unrelated backend tasks. Instead, load it only when files in the iOS tree are used.

Extra tokens do not solve wrong policy activation. A larger prompt merely makes it possible to carry more irrelevant instructions. Conditional guidance prevents platform-specific requirements from occupying the context of unrelated backend tasks. An iOS-specific policy consumes tokens during backend API edits.

An important code-path convention becomes inconsistent. Human reminders alone are not reliable enough for a rule intended to cover every auth-path edit. Only auth middleware should require an explicit threat-model check. Instead, target authentication paths, not an arbitrary global keyword.

Unrelated documentation and UI changes do not need the auth check. Requiring threat modeling for every typo creates noise that discourages targeted security review. Only auth middleware should require an explicit threat-model check. Instead, target authentication paths, not an arbitrary global keyword.

Prompt words do not enforce actual auth-file coverage. An auth middleware edit may not mention security, so keyword activation misses the code boundary. Only auth middleware should require an explicit threat-model check. Instead, target authentication paths, not an arbitrary global keyword.

Explicit path filters are more dependable than guesses. Guessing a file type from a chat description is less accurate than matching the actual file path. User-private memory does not follow every teammate and a global rule unnecessarily constrains files outside the relevant family. Instead, use project path-scoped rules, not one developer's user memory.

Unrelated changes would receive unwanted style constraints. Blanket application burdens unrelated modules with style rules they cannot satisfy sensibly. A code style should apply to all people only when a matching file is edited. Instead, use project path-scoped rules, not one developer's user memory.

Other teammates would not inherit the same project rule. One person's local file does not bind the team to the same file-specific convention. A code style should apply to all people only when a matching file is edited. Instead, use project path-scoped rules, not one developer's user memory.

A filename does not declare conditional glob matching. A filename cannot express a set of directory globs as executable activation metadata. A paths list is placed in plain body text and never activates conditionally. Instead, put path filters in recognized YAML frontmatter.

Plain text has no effect on rule matching metadata. Text showing paths syntax as an example is not parsed as an active rule selector. A paths list is placed in plain body text and never activates conditionally. Instead, put path filters in recognized YAML frontmatter.

Headings cannot replace recognized rule frontmatter. Markdown headings can describe policy but do not supply recognized conditional-loading keys. Claude Code recognizes path-conditional rule metadata in YAML frontmatter rather than parsing arbitrary prose as activation configuration. Instead, put path filters in recognized YAML frontmatter.

The normal policy remains valid for other files. Ordinary files still need the baseline convention even if generated files use a documented exception. A general naming policy and a generated-code exception both match the same file. Instead, identify the overlapping glob scopes and specify an explicit narrow exception to the general rule. Identifying overlapping globs and documenting the exception prevents contradictory naming demands on the same generated artifact.

Other developers would still see the overlap. Teammates lacking that private override will still receive the conflicting common rules. A general naming policy and a generated-code exception both match the same file. Instead, identify the overlapping glob scopes and specify an explicit narrow exception to the general rule. Identifying overlapping globs and documenting the exception prevents contradictory naming demands on the same generated artifact.

Conflicting instructions leave generated output ambiguous. Two active incompatible rules will send contradictory instructions to the model for one artifact. Two matching rules can be simultaneously relevant, so their instructions must state how the narrower generated-code exception interacts with the general rule. A general naming policy and a generated-code exception both match the same file. Instead, identify the overlapping glob scopes and specify an explicit narrow exception to the general rule.