An enterprise wants Claude responses to remain professional across every interaction. Where should tone instructions primarily reside?

• A. API key description
• B. User prompt only
• C. Retrieved documents
• D. System prompt

You are using Claude Code to accelerate software development. Your team uses it for code generation, refactoring, debugging, and documentation. You need to integrate it into your development workflow with custom slash commands, CLAUDE.md configurations, and understand when to use plan mode vs direct execution.
Your team has three requirements for Claude Code's behavior in your project
1. Claude must never modify files in the db/migrations/ directory
2. Claude should prefer your custom logging module over console.log
3. All TypeScript files must be auto-formatted with Prettier after
every edit
All three are currently written as instructions in your project's CLAUDE.md. During a complex refactoring session, a developer discovers that Claude edited a migration file, violating requirement #1. How should you restructure these requirements across Claude Code's configuration mechanisms?

• A. Rewrite all three requirements in CLAUDE.md using stronger directive language and add few- shot examples that demonstrate Claude refusing to edit migration files and running Prettier after edits.
• B. Configure hooks for all three: a PreToolUse hook script that blocks Edit calls targeting db/migrations/,a PreToolUse hook script that adds logging convention context before edits, and a PostToolUse hook that runs Prettier after TypeScript edits.
• C. Add Edit(./db/migrations/**) to permissions.deny in the project settings, keep the logging preference in CLAUDE.md, and add a PostToolUse hook on the Edit tool that runs Prettier on changed TypeScript files.
• D. Move all three requirements into .claude/rules/ as path-scoped rules: one targeting db/migrations/** that forbids editing those files, and others targeting **/*.ts for the logging convention and formatting instruction.

Your infrastructure-as-code repository includes Terraform modules (/terraform/), Kubernetes manifests (/kubernetes/), and CI/CD pipeline scripts (/pipelines/). Each requires different conventions, but your single root CLAUDE.md has grown to 500+ lines. When developers work on Kubernetes files, Terraform-specific rules load into context unnecessarily, consuming tokens.
What is the best approach to reorganize so only relevant guidance loads when editing specific file types?

• A. Keep the root CLAUDE.md and use @path/to/import syntax to modularly include tool-specific guidance files from separate documents.
• B. Split content into subdirectory CLAUDE.md files (/terraform/CLAUDE.md,
  /kubernetes/CLAUDE.md), so Claude loads directory-specific guidance.
• C. Create files in .claude/rules/ with YAML frontmatter path-scoping (e.g., paths: ["terraform/**/*"]), loading rules only when editing matching files.
• D. Restructure the root CLAUDE.md into clearly labeled sections with headers (e.g, "## Terraform Conventions"), improving organization and readability.

Compliance requires that refunds exceeding $500 must automatically escalate to a human agent
- this rule cannot be left to model discretion. Despite clear system prompt instructions, production logs show the agent occasionally processes high-value refunds directly (3% failure rate). How should you achieve guaranteed compliance?

• A. Implement a hook to intercept tool calls; when the refund process amount exceeds $500, block it and invoke human escalation.
• B. Add few-shot examples to the prompt showing correct escalation behavior at various refund amounts ($400, $500, $600).
• C. Modify the refund tool to return an error with message "Amount exceeds policy limit - please escalate" when threshold is exceeded.
• D. Strengthen the system prompt with emphatic language: "CRITICAL POLICY: Refunds over $500 MUST trigger human escalation. NEVER process these directly."