Backend engineering conventions for team. Java/Kotlin servers. Project conventions in .claude/conventions/backend.md override these defaults.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Backend conventions, team default.
Project override: if `{repo}/.claude/conventions/backend.md` exists, overrides any rule here. See guides/conventions-override.md.
## Defaults
Illustrative defaults for JVM-leaning backend. Override per repo via `.claude/conventions/backend.md`.
Stack:
- Java or Kotlin (check pom.xml or build.gradle.kts)
- Spring Boot (current major) or Ktor for Kotlin services
- Build: Maven (mvn) or Gradle (gradlew)
- Deploy: JAR with embedded server
- Package prefix: match repo convention
Persistence:
- Custom JDBC AbstractRepository + SQL templates. Avoid JPA except where repo already uses it.
- Migrations via Flyway, naming `V{YYYYMMDD}__{description}.sql`.
Mapping:
- Orika 1.5.x. Avoid MapStruct unless repo already uses it.
Lombok:
- `@Data`, `@Builder`, `@RequiredArgsConstructor` OK.
- Avoid `@SneakyThrows`. Be explicit about checked exceptions.
Null handling:
- `Objects.equals()` for equality.
- `Boolean.TRUE.equals(...)` for nullable booleans.
- Guards and early returns. Avoid deep nesting.
Streams:
- Fluent: `.stream().filter(...).findAny().orElseThrow(...)`.
- Avoid stream-of-stream when guard would do.
Transactions:
…
The line at the top of this page pins the label git:20260519.492683a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2472 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
pierry/harness-kit · 4 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_erycrgusrknmefd2
GET https://markdownregistry.com/api/v1/resolve?ref=pierry/harness-kit/backend
GET https://markdownregistry.com/api/v1/blob/43db9a5cfd478b61778847300a609cfde61c9e226c18eef545dc814ec94a55dd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
pierry/harness-kit · .claude/agents/product-manager/skills/prd/SKILL.md · Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.
pierry/harness-kit · .claude/agents/product-manager/skills/prp/SKILL.md · Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/mobile/SKILL.md · Mobile engineering conventions for team. iOS and Android. Project conventions in .claude/conventions/mobile.md override…
pierry/harness-kit · .claude/agents/staff-software-engineer/skills/web/SKILL.md · Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override…
pierry/harness-kit · .claude/agents/system-architect/skills/design/SKILL.md · Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook…
pierry/harness-kit · .claude/agents/system-architect/skills/review/SKILL.md · Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and…
pierry/harness-kit · .claude/agents/system-architect/skills/search-engine/SKILL.md · Design a web-scale search engine (crawler, processing, indexing, query serving). Topic playbook from the System Design…
nerds-odd-e/doughnut · .agents/skills/backend/SKILL.md · Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work…
dojocodinglabs/code-sensei · skills/backend/SKILL.md · Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or…
tekkiiiii/the-agency · skills/backend/SKILL.md · Use when building or reviewing backend systems: APIs, database schemas, auth, file uploads, webhooks, microservices…
marvelcollin/agent-skills · skills/backend/SKILL.md · Build, review and load test backend services to an expert standard. When writing server code, applies hard rules B1 to…
wewpellex21/code-sensei · skills/backend/SKILL.md · Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or…
