You are integrating Claude into an application written in Python. The Claude SDK provides a Python client that wraps the underlying REST API.
How would you integrate the SDK?

• A. Use a different LLM provider's SDK and translate the responses into Claude's API shape so the application can switch providers in the future.
• B. Skip the SDK and embed Claude calls in shell commands invoked from Python, so that the application runs the calls outside the main Python process.
• C. Call the REST API directly with raw HTTP requests so the application avoids the SDK's abstraction between the application code and the API.
• D. Use the Claude Python SDK and let it handle authentication, retries, and response parsing through its standard documented patterns for Python integrations.

Your team's Claude agent has accumulated several customizations that bypass the SDK's defaults, including custom history management, retry logic, and error handling. A new team member has proposed reverting all the customizations to maintain the codebase more easily. The tech lead disagrees and says each customization was added for a reason.
How would you advise the team?

• A. Revert all customizations to the SDK's defaults to standardize the codebase.
• B. Migrate the agent off the SDK and rebuild it with a custom loop.
• C. Keep all customizations, trusting that the tech lead's original reasoning is still valid.
• D. Decide on each customization individually based on its original reason and the SDK's current capabilities.

You are configuring Claude Code for a new project. The team needs to set permissions, default model selections, and environment-specific behavior at the project level so the configuration is consistent across all developers working on the repository.
The Claude Code mechanism you would use is...

• A. Environment variables that each developer sets on their own machine when working with Claude Code on the project.
• B. A system prompt embedded in every Claude Code conversation by each developer at the start of every session in the project.
• C. A shared spreadsheet that lists configuration values for team members to reference and update by hand as the project evolves.
• D. The settings.json file, scoped at the project level so the configuration applies consistently across developers and persists with the repository.

You are designing a Claude application that will require structured JSON output for downstream processing.
The output schema is well-defined, and downstream systems will reject malformed JSON.

• A. Define a clear schema, structure the prompt to request output in that schema, and validate Claude's output against the schema before passing it downstream.
• B. Define a clear schema and structure the prompt to request output in that schema, with downstream systems handling any validation needed.
• C. Structure the prompt to request output in a schema that is described in plain English, with downstream systems parsing whatever shape Claude produces.
• D. Avoid structured output and use free-form text everywhere instead, on the grounds that free-form text is more flexible and handles edge cases better than structured schemas.

The Claude application your team built has grown over six months, and the prompt-handling code has accumulated duplication and tangled control flow. The functionality is working, but new features are getting harder to add.
How would you address this?

• A. Plan a refactoring pass to consolidate duplicated logic, separate concerns, and simplify control flow before adding new features.
• B. Refactor the prompt-handling code in small increments as part of each new feature ticket, treating the cleanup as a side effect of feature work.
• C. Move all the prompt-handling code into a single large function to reduce the number of files developers have to navigate when reading the code.
• D. Continue adding features and plan a refactoring pass after the next two release cycles when the team has more bandwidth for internal work.