Claude Code skills, rules, and language bundles https://git.cjennings.net/rulesets/atom?h=main 2026-07-09T19:02:39+00:00 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-31T03:13:37+00:00 Craig Jennings c@cjennings.net 2026-05-31T03:13:37+00:00 urn:sha1:ddcde66a768758844a5be705de6a89e68697fa1a An org-drill session asked to send a follow-up email first claimed it couldn't, then hand-built MIME through msmtp, because nothing told it cmail send exists. I added a "Sending Email" subsection to protocols.org (read every session): cmail (c@cjennings.net) is the default for personal mail, dmail for work, and cmail-action send is the tool, with one-liner examples for body-file, attachments, Cc/Bcc, and threaded replies. I also rewrote send-email.org Step 4, replacing the inline-Python heredoc that taught the hard way with the cmail-action send call. 2026-05-15T21:56:39+00:00 Craig Jennings c@cjennings.net 2026-05-15T21:56:39+00:00 urn:sha1:c1d4e3c4a42abd01bc7ef83b1d6ae036ee32ef1d