ruly: Instructions file for Claude Code

• Shared recipe definitions live in recipes.yml at the root of the rules repo (https://github.com/patrickclery/rules), using repo-relative paths. ~/.config/ruly/recipes.yml holds only remotes: and overrides: (per-machine additions). ~/.config/ruly/remotes/ is generated by ruly squash --sync — never edit it.
• Every time the slash commands are updated, make sure to update the slash command section of README.md
• When changing ruly CLI commands (squash, clean, analyze, mcp, etc.), always update README.md to reflect the changes
• NEVER edit CLAUDE.local.md — it is generated output from ruly squash and will be overwritten. Fix the source rules in ./rules/ instead.
• When I ask to change rules, don't change the rules in .claude/ always look in ./rules/
• When I ask to create a skill, add it to rules/{tag}/skills/{skill-name}.md (Ruly searches for skills in that structure)
• Skills in rules/ are regular .md files, NOT SKILL.md - Ruly converts them to SKILL.md format on squash
• Always use git mv to move/rename files instead of deleting and re-creating them (preserves git history)
• When deleting/moving/renaming files in rules/, always search for references to update:
  • requires: frontmatter in other rule files
  • Recipe files (recipes.yml in the rules repo, ~/.config/ruly/recipes.yml, .recipes.yml)
  • Section anchor links that may have changed
• When I say "commit" or "commit all", commit and push ALL modified files in BOTH repos (don't assume any changes are unrelated):
  1. The rules submodule (./rules) → https://github.com/patrickclery/rules
  2. The parent ruly repo → https://github.com/patrickclery/ruly (update submodule reference)
• Always use Mermaid for diagrams/flowcharts in rules (never graphviz/dot). Exception: Jira/Confluence don't support Mermaid, so use ASCII diagrams there instead.

Claude Code Instructions

Ruly Recipe and MCP Configuration Patterns

Import Ruly recipe configuration patterns and MCP server guidelines. @./.claude/ruly-recipes-mcp-patterns.md