rulesets - Claude Code skills, rules, and language bundles

	Commit message (Collapse)	Author	Age	Files	Lines
*	docs: keep chat output plain text to avoid reverse-video	Craig Jennings	2026-05-25	1	-11/+15
\| \| \| \| \| \|	Craig's terminal renders Markdown bold and inline-code spans as reverse video, which is hard to read. I added a rule to interaction.md: in conversational output, write command names, paths, and key chords as plain text, and lean on headers, dashes, parentheses, and quotes for structure. It governs chat output only, not the Markdown source of the rule and spec files he reads in an editor. I also made the keybinding-display example plain text so the convention shows the format the way it should appear in chat, with a pointer to the new rule.
*	docs: add the keybinding-display convention	Craig Jennings	2026-05-25	1	-0/+38
	I added a rule for how to present a keymap's bindings when asked to show them. The format is a bulleted list grouped by prefix level: a General header at the top that lists the sub-prefixes leading into each category, then one section per category. Every bullet carries the full chord, the bound command, and the which-key label, so the written view matches what which-key shows on screen.