Dominik Herrmann

This AGENTS.md fixes the 𝘁𝗵𝗿𝗲𝗲 𝗺𝗼𝘀𝘁 𝗮𝗻𝗻𝗼𝘆𝗶𝗻𝗴 𝗵𝗮𝗯𝗶𝘁𝘀 of Codex and Claude Code: writing backward-compatible code for a project nobody uses yet, never deleting old code and docs it no longer needs, and adding a pile of tests just to change a button color. After using them every day for months, the lines I'd want in there from day one are the ones at the top: if the project has no real users yet, skip compatibility and migrations, and go straight to 𝘁𝗵𝗲 𝘀𝗶𝗺𝗽𝗹𝗲𝘀𝘁 𝗰𝗼𝗱𝗲 𝘁𝗵𝗮𝘁 𝘄𝗼𝗿𝗸𝘀. Then a four-step loop: docs first → tests → smallest implementation → clean up. Copy and paste it into your AGENTS.md 👇

A week of Claude Code sessions is too much to remember. Every weekend, have Opus 5.5 vibe-code a quick 𝘄𝗲𝗲𝗸𝗹𝘆 𝗰𝗮𝗹𝗲𝗻𝗱𝗮𝗿 like this from your local session logs. Then give it 𝗮 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁 𝘁𝗵𝗮𝘁 𝗼𝗻𝗹𝘆 𝗯𝘂𝗶𝗹𝗱𝘀 𝘄𝗲𝗲𝗸𝗹𝘆 𝗰𝗮𝗹𝗲𝗻𝗱𝗮𝗿𝘀: → Name it week-calendar, set its effort to medium, and preload a design skill → The first time, it asks which colors you like and whether to color by project or by task, and saves that to memory. After that, every calendar follows it → Call it when you want to look back on the week or write a weekly report. It regenerates the calendar and writes up a 3-line weekly report for you → The calendar shows four things: when you worked each day, what each session did, 𝘄𝗵𝗶𝗰𝗵 𝘀𝗲𝘀𝘀𝗶𝗼𝗻𝘀 𝘀𝘁𝗼𝗽𝗽𝗲𝗱 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗮 𝘀𝗶𝗻𝗴𝗹𝗲 𝗰𝗼𝗺𝗺𝗶𝘁, and how many hours each project took this week Send this prompt to Claude Code 👇 "Set up a subagent that only builds weekly calendars: 1. Create week-calendar in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). Give it Bash so it can run git log and the script that builds the calendar. It only writes files to ~/.calendar/ and its own memory. 2. The first time, it asks me what style I like: dark or light, one accent color, color by project or by task type, and whether the week starts on Monday or Sunday. It saves my answers to memory and follows them every time. 3. The calendar is one HTML file. The script writes the data straight into it, so it opens with a double-click. Use this week's session logs: Claude Code's are in ~/.claude/projects/ (skip the subagents folders), and if I use Codex, add ~/.codex/sessions/. Before writing the script, open one file to check the fields. Convert times to my local time zone, and use the cwd in each record to tell projects apart. One block per session; start a new block after any gap longer than 30 minutes. Clicking a block shows the project, start and end time, the model used, the session title (if there isn't one, sum up my first typed message in 3 to 5 words), my first typed message, and my commits and changed files in that repo during that time (skip folders that aren't git repos). Sessions that stopped without a single commit get a red outline and also go in a separate list. At the top, total this week's hours per project, counting parallel sessions only once. Keep everything local. 4. Add a rule to ~/.claude/CLAUDE.md: when I say "what did I do this week" or "write my weekly report", have week-calendar regenerate the calendar first, then write a 3-line weekly report from it: what I mainly got done this week, which project took the most time, and which no-commit sessions to pick up first next week. Show me the contents of the files you'll create or change, then explain the whole flow in words a 10-year-old could follow. Don't write anything until I confirm."