rulesets - Claude Code skills, rules, and language bundles

	Commit message (Collapse)	Author	Age	Files	Lines
*	docs(cross-project): prefer inbox-send for handoff drops	Craig Jennings	2026-05-15	1	-0/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The cross-project boundary rule already prescribes dropping a handoff file in the target project's inbox/ when option 1 ("do it from here") is chosen. The change adds a paragraph pointing at the new inbox-send script as the preferred tool for the drop. The script handles project discovery, source-project provenance in the filename, slug derivation, and timestamping in one call, replacing the hand-constructed filenames and guessed project paths the rule used to require. Filename convention is unchanged (YYYY-MM-DD-HHMM-from-<source>-<slug>.<ext>); the script just generates it instead of me typing it out. Fallback to Write/Edit is documented for cases where the script isn't installed (e.g. a freshly-cloned project before the first startup-rsync).
*	feat(rules): cross-project boundary rule + cj-comments preflight	Craig Jennings	2026-05-13	1	-0/+50
	New `claude-rules/cross-project.md` codifies the per-project `.ai/` scope boundary. Stop-and-ask when a request targets another project's files, inline numbered options, handoff-file convention when the user opts to do it from here. `/respond-to-cj-comments` gains a section-0 preflight (boundary check before reading the target file) and a section-7 handoff step (writes the carry-forward file in the target project's `inbox/` when the boundary crossing was approved).