Migrate from ai-rulesmith
Use this when a project still has AI_RULES.json and/or .rulesmith/.
- Note the profile name (or rule lists) in
AI_RULES.json. - Pick the closest recipe under
examples/(see Recipes). task apply RECIPE=<name> TARGET=/path/to/projector copy the recipeconfig.tomlby hand.- Rewrite every
[[includes]]to the git library URL with a pinnedref. - Move the old preamble into
.ai-rulez/context/(or a root rule). - Project-specific vars (license, Python version): put them in local context or override rules under
.ai-rulez/rules/. - Run
ai-rulez validateandai-rulez generate. - Decide whether generated outputs are committed or gitignored (
gitignore = truein config). - Delete
AI_RULES.jsonand.rulesmith/once generation looks right. - Optional: keep ai-rulez MCP enabled and use
enablement-guidefor later toggles.
Mapping cheat sheet
Section titled “Mapping cheat sheet”| rulesmith idea | ai-rulez idea |
|---|---|
| Hardcoded rule slug list | builtins + module [[includes]] |
| Profile JSON | Recipe directory under examples/ |
| Steps workflow | workflow-standard or workflow-strict module (skills, agents, commands) |
Global ~/.config/rulesmith or vendor | Git include ref pin |
task build (rulesmith) | ai-rulez generate / task build here |
This library
Section titled “This library”This repository already dogfoods ai-rulez (.ai-rulez/ + modules/). No other local
AI_RULES.json consumers were found at migration time; apply the playbook when you hit one.