yukta / architecture
CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub
Test-only module with the ArchUnit rules for the Apache modules. Reference: docs/contributing/architecture.mdx.
In this repository21 other files it gives its agents.
- boot/CLAUDE.mdCLAUDE.md
- build-logic/CLAUDE.mdCLAUDE.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- core/CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- messaging/CLAUDE.mdCLAUDE.md
- plugin-api/CLAUDE.mdCLAUDE.md
- plugins/CLAUDE.mdCLAUDE.md
- plus/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ide-index-mcpSkill
- pickupSkill
- playwrightSkill
- testsSkill
- ticketSkill
- yuktaSkill
- yukta-supervisorSkill
- yukta-workflowsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Test-only module with the ArchUnit rules for the Apache modules.
- Very specific: line 5
Run: yk gradle :architecture:test (the Plus modules: yk gradle :plus:plus-architecture:test).
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture Module CLAUDE.md
Test-only module with the ArchUnit rules for the Apache modules. Reference: docs/contributing/architecture.mdx.
- Run:
yk gradle :architecture:test(the Plus modules:yk gradle :plus:plus-architecture:test). - Layout:
src/testFixturesholds whatplus-architecturereuses (Modules,Scopes,HygieneRules,ReactiveRules,DeprecationRules,StructureRules);src/testholds the module-specific rule holders (ModuleRules,CoreRules,WebRules), one runner per scope (*ArchitectureTest), the self-tests (RuleSelfTest,ModuleLocationTest) and the guards (ModuleCoverageTest,NoEscapeHatchesTest). - Layers are found by the directory a class was built in (
Modules), not by package: modules share packages. - The module depends on every Java module. A new module in
settings.gradle.ktsmust be added tobuild.gradle.kts(ModuleCoverageTestfails otherwise); it must not depend on:plus*(only boot andplus/**may). - Policy: violations are fixed. No freezing, no
@ArchIgnore, no weakening a rule to make a build pass. Exemptions (blocking calls, deprecated API, plugin edges) are short maps with a reason; adding one needs a maintainer's review. - Core's package layout is
src/test/resources/core-packages.puml; change it together with the code and explain why. - PMD/Checkstyle apply here too: package-private members carry
/* default */, repeated literals are constants, rule holder classes arefinalwith a private constructor.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

