<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/brainstorm, 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-05-06T11:17:08+00:00</updated>
<entry>
<title>refactor(skills): convert 16 user-invoked skills to commands</title>
<updated>2026-05-06T11:17:08+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-06T11:17:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=aa6924591127970d3241ab6b1a50f4bab457da27'/>
<id>urn:sha1:aa6924591127970d3241ab6b1a50f4bab457da27</id>
<content type='text'>
I converted 16 user-invoked skills to commands. Skills cost ~150-300 tokens each per session for descriptions the model uses to auto-route. Commands cost nothing until you type the slash. These 16 are workflows I always trigger deliberately. The auto-routing wasn't earning its keep. This reclaims ~4-5k tokens per session.

Nine skills stayed where auto-routing genuinely helps: debug, root-cause-trace, five-whys, add-tests, frontend-design, humanizer, playwright-js, playwright-py, and pairwise-tests. Pairwise-tests stays a skill because its helper files don't fit a single-file command shape.

For arch-decide, I preserved the upstream MIT LICENSE alongside the command at .claude/commands/arch-decide.LICENSE so attribution stays intact.
</content>
</entry>
<entry>
<title>docs: split Linear vs PR structure; propagate content-scope rule to Tier 1 skills</title>
<updated>2026-04-25T00:11:41+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-04-25T00:11:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=e5b54c24afdd569765b215732884bd0a8f2758a9'/>
<id>urn:sha1:e5b54c24afdd569765b215732884bd0a8f2758a9</id>
<content type='text'>
Linear ticket bodies are now Problem + Fix only. PR descriptions keep
the four-section format (Problem, Fix, Why this fixes it, How it was
tested). Linear's GitHub integration handles the cross-link via the
PR body's Linear: line.

Cross-ref to the content-scope rule appended at the end of each Tier 1
skill that produces public artifacts: testing.md, arch-document,
arch-decide, arch-design, review-code, respond-to-review, brainstorm,
codify. Single-source the rule in commits.md, point at it from each
output-producing skill.
</content>
</entry>
<entry>
<title>chore: remove fix-issue skill, superseded by start-work</title>
<updated>2026-04-22T13:08:59+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-04-22T13:08:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=1fb4232671d30aa867e3e7b0c74d48a989e460c5'/>
<id>urn:sha1:1fb4232671d30aa867e3e7b0c74d48a989e460c5</id>
<content type='text'>
The fix-issue skill has been replaced by start-work, which covers the same ground (picking up a ticket with a known fix and carrying it through to handoff) with a seven-phase structure and three user-approval gates. Deleted fix-issue/SKILL.md and swept the references.

Updated:
- Makefile SKILLS list: remove fix-issue, add start-work so make install creates the right symlink.
- brainstorm/SKILL.md: implementation-path list points at start-work.
- debug/SKILL.md description: both "do NOT use for ticket-driven work" and "Companion to" references updated.
- review-code/SKILL.md description: "drafting implementation" redirect updated.

No change in meaning. Every old fix-issue context now names start-work.
</content>
</entry>
<entry>
<title>feat: clean-room synthesis — brainstorm, memorize, root-cause-trace, five-whys</title>
<updated>2026-04-19T19:40:34+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-04-19T19:40:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=89a3312b51baa3f74211c27414583b9add1b802f'/>
<id>urn:sha1:89a3312b51baa3f74211c27414583b9add1b802f</id>
<content type='text'>
Four new skills synthesized from patterns in NeoLabHQ/context-engineering-kit
(GPL-3.0). Clean-room approach: extracted rubrics from the originals
(triggers, phases, hard cases, footguns, novel patterns), then wrote from
scratch without referencing their prose. Ideas and methods aren't copyrightable;
wording is. These skills are independent works.

  brainstorm          Turn a vague idea into a validated design doc. Three
                      phases: one-question-at-a-time dialogue, six-approach
                      exploration (three conventional + three diverse tail
                      samples for anti-convergence), chunked design
                      presentation with per-chunk validation. Output:
                      docs/design/&lt;topic&gt;.md. Hands off to arch-decide /
                      arch-design / implementation.

  memorize            Curate session insights into project CLAUDE.md under a
                      dedicated "## Memorized Insights" section. Grow-and-
                      refine per ACE (arXiv:2510.04618): atomic, evidence-
                      backed, non-redundant bullets. Args: --dry-run, --max,
                      --target, --section, --source. Flags cross-project
                      patterns for promotion to ~/code/rulesets/claude-rules/.
                      Clearly delineates from auto-memory (private) and
                      formal rules (stable policy).

  root-cause-trace    Backward-walk technique for debugging. Observe symptom
                      → identify immediate cause → walk up the call chain →
                      find original trigger → fix at source + defense-in-
                      depth at each intermediate layer. Instrumentation
                      guidance (stack capture before the dangerous op, not
                      after; stderr not framework logger in tests); test-
                      pollution bisection. Companion to /debug — /debug is
                      broader; this is specifically the backward walk.

  five-whys           Iterative why-questioning from symptom to process/
                      decision root cause. Five is a convention, not a
                      quota — stop when a cause, if eliminated, would prevent
                      every symptom in the chain. Handles branching (multiple
                      contributing causes). Validates chains by walking back
                      from root to symptom. Refuses to terminate at "human
                      error" or "not enough budget" — those have deeper
                      whys. Companion to root-cause-trace (that's for code
                      execution; this is for process).

Makefile SKILLS extended. make install symlinks all four into
~/.claude/skills/ alongside existing skills. Lint clean.
</content>
</entry>
</feed>
