yukta / build-logic
CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub
All modules apply these plugins via plugins { id("com.infenia.yukta.xxx-conventions") }.
In this repository21 other files it gives its agents.
- architecture/CLAUDE.mdCLAUDE.md
- boot/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
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
All modules apply these plugins via plugins { id("com.infenia.yukta.xxx-conventions") }.
≈ “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
Build Logic CLAUDE.md
Overview
The build-logic directory defines reusable convention plugins for the Yukta project.
Convention Plugins
- java-conventions: Java toolchain (25), Lombok, repositories, JUnit 5.
- quality-conventions: Spotless, Checkstyle, PMD, SpotBugs, OpenGrep, license headers.
- jacoco-conventions: Code coverage tracking.
- library-conventions:
java-library+ spring-conventions (used by every library module). - spring-conventions: Base conventions for Spring Boot modules.
- node-conventions: pnpm/Node.js toolchain wiring for frontend modules (e.g.
ui). - mutation-conventions: PIT mutation testing, applied only with
-Pmutation.
All modules apply these plugins via plugins { id("com.infenia.yukta.xxx-conventions") }.
Quality Configuration
- Checkstyle:
config/checkstyle/checkstyle.xml - PMD:
config/pmd/ruleset.xml - OpenGrep: runs in
checkonly if theopengrepCLI is installed, with the local rulesetconfig/opengrep/.semgrep.yml; any finding fails the build (--error) - License:
config/license/
Docs
../docs/contributing/modules/build-logic.mdx(module guide); open risks, bugs and review findings: GitHub issues labelledbuild(gh issue list -l build; risks also carryrisk); evolution path and quality lenses:../design/assessments/build-logic.md.
Imports
@.claude/rules/coding-standards.md @.claude/rules/git-workflow.md
Coverage policy
Defaults are LINE 100% / BRANCH 100% per class. Lower a class with coverageConfig { exception(pattern, reason, mapOf("BRANCH" to 0.7)) }; below 0.80 a reason is required. Stale patterns fail the build. A disabled gate task (Checkstyle, PMD, SpotBugs, Spotless, OpenGrep, Licensee, coverage) or one that ignores failures fails it too, unless listed in allowedDisabledQualityTasks (quality-conventions). The guards are tested in build-logic/src/test (TestKit; yk gradle :build-logic:test, also part of the root check). verifyCoverageData (part of check) fails a module that has classes but no test execution data (tests deleted, filtered or not run); call coverageConfig.noTests("reason") for a module that legitimately has none. Trivy is not part of check (CI runs it; yk gradle trivy on demand).
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.

