add claude config#346
Conversation
|
| <version>3.4.0</version> | ||
| <configuration> | ||
| <!-- THE MAGIC LINE: Spotless will only format files changed relative to this branch --> | ||
| <ratchetFrom>origin/master</ratchetFrom> |
There was a problem hiding this comment.
why only this branch? won't this break the local development because there will be no formatter?
There was a problem hiding this comment.
It won't break formatting, it just limits which files get formatted. With this setup when spotless:apply is executed it will be triggered only for the files that are changed compared to master and the legacy files that were never formatted or updated will remain untouched.
| Application (MTA) specification. It serves as a foundational dependency for the | ||
| Cloud Foundry MultiApps Controller. | ||
|
|
||
| ## Security Boundary |
There was a problem hiding this comment.
does this security boundary note need to be doubled here in addition to in the rooot md file? Can it not only have a single source of truth in the root?
There was a problem hiding this comment.
I presume that we can keep both the root instructions along with the local instructions as well. For example if we have a multi agent development and when an AI agent is invoked inside multiapps/, there is no guarantee the root CLAUDE.md is in context — especially in sub-agent invocations, IDE integrations, or any session where the working directory is the sub-repo directly. If the root table isn't loaded, and the sub-repo has no boundary note, the AI has zero guardrails against leaking proprietary content.
| Before completing any task or committing code, you **MUST** run: | ||
|
|
||
| ```bash | ||
| mvn spotless:apply |
There was a problem hiding this comment.
this and the above mvn commands would probably be the same for all repos using maven - would it not shrink the context to have them in the root md file and keep the local files only for project specific things?
3 participants
No description provided.