CCA-F: Claude Certified Architect — Foundations

You are integrating Claude Code into your Continuous Integration/Continuous Deployment (CI/CD) pipeline. The system performs automated code reviews, generates test cases, and provides feedback on pull requests. You need to design prompts that give actionable feedback and minimize false positives.

The automated review repeatedly flags patterns that your team intentionally uses—force-unwrapping optionals in test files, using large coordinator classes that follow your established architecture, and importing internally maintained modules marked as deprecated in the public SDK. Developers dismiss approximately 30% of all findings as project-specific false positives.

Which approach prevents the model from producing these findings in the first place by providing the project’s conventions as persistent context on every review?