Where engineering-conventions is going

engineering-conventions started on 2026-10-30, when the standing rules for Marcel's repositories moved out of a private wiki into a public repository (the wiki's pages were retired the same day), so that every session and every contributor can read them. It is becoming the one place a new repository is set up from, and the plugin every Claude session loads.

This page says what is planned and why, inside the values, and what has shipped. Each step links its issue and the value it serves. Planned steps have no dates, only now, next or later; shipped steps carry the day they shipped.

The idea behind all of it

Write each rule down once, with its reason and its limit, where every person and every session can read it, and let each repository decide where it differs.

Now

Every repository points at the conventions#1V2

One line in each repository's CLAUDE.md, so a session without the plugin still finds them.

Details

Start with freundebuch, notefeed, questlog, mcp-login-oauth, gassi and passageway. Note where a CLAUDE.md repeats a convention (it can shrink) or contradicts one (the repository wins; decide whether the convention should change).

Next

Code style#2V1

Functions, naming, comments and tests, each confirmed by Marcel before it lands.

Later

Conventions from single repositories#3V4

Branch and commit naming, CI as the gate, tests through a quiet wrapper and others that live in one project's CLAUDE.md today.

30 Oct 2026

The conventions, public and as a plugin#4V5

Architecture, code, repository setup and stacks, moved from a private wiki; a skill to apply them and one to add to them.

Parked

• One package for the roadmap timeline: the hook and its CSS are copied into each repository today (Values and roadmap pages). A shared MkDocs plugin would keep them in step, once more than a handful of sites use them.
• A generated ADR menu: the Decisions section of a docs site is kept by hand (Documentation site); a plugin could build it from docs/adr/.

Decided against

• Homelab and personal conventions here: how Marcel's own servers, accounts and tools are set up stays in his private wiki, because this repository is public. See V3.

Keep it true

The timeline is rendered from docs/roadmap.yml; on GitHub, read that file. Finish a step in the pull request that finishes it: set status: done, replace when with a date, add the link to its pull request, and move it to the top of the shipped entries. Change the file in the pull request that changes the plan.