The moment you connect Cuddler to a codebase, it begins reverse-engineering the standards your team already follows. We call the result the Rule Book: a living index of naming conventions, architectural patterns, dependency choices, and security guardrails. Next, Cuddler documents Recipe Books—step-by-step implementation notes learned from real commits.
Together, Rules and Recipes turn tribal knowledge into executable instructions. When a refactor lands in the backlog, Cuddler combines these playbooks with your current tree to propose changes that look and feel like your best pull requests.
Why Rule & Recipe Books matter
- New features inherit the same conventions you already approve in code reviews.
- Teams avoid regressions caused by inconsistent naming, file placement, or guardrail usage.
- Onboarding is faster because rules are surfaced in a readable playbook.
Make them work for you
- Ship the change once with your team.
- Approve the final code & tests.
- Let Cuddler propagate the pattern wherever it applies.
- Review and expand the Rule and Recipe Books as you iterate.
The payoff is simple: refactors land faster, onboarding gets easier, and production stays consistent.