<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/.ai/workflows/page-me.org, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-07-02T09:58:03+00:00</updated>
<entry>
<title>fix(page): pages are info-level, not alarm-red</title>
<updated>2026-07-02T09:58:03+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-02T09:58:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=a6b534ff6c8c998d940fc3bd201f236c182c8bb3'/>
<id>urn:sha1:a6b534ff6c8c998d940fc3bd201f236c182c8bb3</id>
<content type='text'>
Craig's verdict on the all-red page styling: it reads like the system is about to crash. page-me and the work-the-backlog end-of-set page now use notify info --persist, still persistent and audible, never crash-scary. status-check's success and fail notifications keep their types, since a job outcome isn't a page.

The commit also carries the two loop-filed task records and the archive sweep counterpart from earlier tonight.
</content>
</entry>
<entry>
<title>chore(ai): initialize project notes and Claude tooling surfaces</title>
<updated>2026-05-07T02:59:52+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-07T02:59:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=d81b23ad6b6e437dfe3c338a00a4be39bc555146'/>
<id>urn:sha1:d81b23ad6b6e437dfe3c338a00a4be39bc555146</id>
<content type='text'>
Replace the seed notes.org with project-specific context (layout, install modes, task tracker location, recent inflection point). Bring in the synced template surfaces (protocols, workflows, scripts, references, retrospectives, someday-maybe) as tracked content for this content/documentation project.
</content>
</entry>
</feed>
