Claude Code skills, rules, and language bundles https://git.cjennings.net/rulesets/atom?h=main 2026-07-29T05:49:43+00:00 2026-07-29T05:49:43+00:00 Craig Jennings c@cjennings.net 2026-07-29T05:49:43+00:00 urn:sha1:5999f88dd6e66794a9a0898ba643247de023ac2d protocols.org pointed at references/calendar-reference.org, which the template rsync never copies. The link was dead in every consuming project. It now points at the four calendar workflows, which do sync. They already carry the tool names, both account ids, and the gcalcli fallback. The reference file itself is gone. Nothing linked it any more. It existed as two copies that sync-check doesn't gate, and all three credential paths in it had been dead since the OAuth keys moved into the encrypted MCP bundle. protocols.org now names mcp/README.org as the authority instead, in prose rather than a link, so it can't go dead downstream the same way. I dropped one fact with it on purpose: that the Google Cloud app runs in production mode so tokens don't expire weekly. It's checkable in the console and it was the last live line in the file. The same defect class turned up at seven more sites in four synced workflows, all reaching outside .ai/ with ../../. I filed those rather than fixing them here. scripts/lint.sh already has a check built for exactly this and misses them because it only matches markdown link syntax. 2026-07-09T19:02:39+00:00 Craig Jennings c@cjennings.net 2026-07-09T19:02:39+00:00 urn:sha1:6def7c4d63f499aba10fe93c7bb2c7e206a7d7f5 Every org document an agent writes carried `#+AUTHOR: Craig Jennings & Claude`. No template stamps that line. Agents copy it from a neighboring file, so one stray header propagates through everything generated afterward. My own repos tolerate the co-author line. Employers whose policy is that work product carries employee names alone do not. An `#+AUTHOR:` line survives conversion into docx, a wiki page, or a PDF that reaches a customer. I rewrote the header to `Craig Jennings` across the workflows, templates, specs, and design docs. The rule now lives in commits.md, so the next generated document starts correct rather than inheriting the mistake. Archived session logs keep their original headers as a record of what happened. The two Codex-authored design docs keep their byline, because Codex wrote them and relabeling would be a false attribution rather than the removal of one. 2026-05-15T21:56:39+00:00 Craig Jennings c@cjennings.net 2026-05-15T21:56:39+00:00 urn:sha1:c1d4e3c4a42abd01bc7ef83b1d6ae036ee32ef1d