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 is configuring MCP servers in Claude Code. You want to add a shared venue lookup server that all team members should have access to, and you personally want to add an experimental music playlist server that only you are testing. Which configuration approach correctly applies MCP server scopes?

• A. Add venue server to .mcp.json and playlist server to ~/.claude.json.
• B. Add venue server to ~/.claude.json and playlist server to .mcp.json
• C. Add both servers to your local ~/.claude.json
• D. Add both servers to the project-level .mcp.json file

Your send_notification tool calls third-party messaging APIs. When these services time out during delivery, you cannot determine whether the message was actually sent. Currently, the tool returns is_error: true with a generic "Notification failed" message for all timeouts. Production monitoring reveals agents automatically retry these failures, frequently causing users to receive duplicate notifications. How should you modify the error response?

• A. Return is_error: true with the original message content echoed back.
• B. Return is_error: true with a structured field retry_safe: true for timeouts, distinguishing them from permanent failures that should not be retried.
• C. Return is_error: true with a message communicating uncertainty: "Timeout - status unknown.
  Message may have been sent. Avoid retry."
• D. Return is_error: true with a message encouraging retry: "Delivery service temporarily unavailable.
  Please retry the notification."

What is the PRIMARY purpose of few-shot prompting?

• A. Increase model size.
• B. Encrypt prompts.
• C. Demonstrate desired output patterns.
• D. Reduce token costs.

During a billing dispute resolution, your agent successfully retrieves customer info via get_customer and order details via lookup_order, but when attempting to call process_refund, the tool returns a timeout error. The agent has enough information to explain the charges and verify refund eligibility, but cannot actually process the refund due to the backend failure. What approach best balances first-contact resolution with appropriate error handling?

• A. Confirm the refund will be processed and close the conversation, since the system has all necessary information to complete it automatically
• B. Explain the billing confirm refund eligibility, acknowledge the system issue preventing immediate processing, and offer escalation or retry later
• C. Implement automatic retries with exponential backoff for process_refund, keeping the conversation open until the refund is successfully processed
• D. Escalate immediately to a human agent since the refund action cannot be completed

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.
You've documented API error handling conventions in a CLAUDE.md file at your project root, specifying that endpoint handlers should use a custom ApiError class. After several sessions, you notice Claude Code sometimes follows these conventions and sometimes uses generic try/catch blocks with string messages. The inconsistency appears random across different coding sessions. What's the most efficient first diagnostic step?

• A. Search for conflicting instructions in ~/.claude/CLauDe.md or ~/.claude/rules/ that might override your project conventions.
• B. Create path-specific rules in .claude/rules/handlers.md with YAML frontmatter scoping the error handling instructions to your API handler files.
• C. Add a more detailed code examples to your CLAUDE.md showing the exact ApiError usage pattern for different endpoint types.
• D. Run /memory to check which memory files are loaded and verify your CLAUDE.md is included.