frappe-syntax-hooks-events

What problem does it solve?

This Skill prevents fragile, production-breaking mistakes when implementing Frappe document lifecycle hooks via hooks.py doc_events, especially around incorrect event names and misunderstandings of execution order.

Core Features & Use Cases

• Accurate lifecycle event execution order: Guides you through the correct sequence for insert, save, submit, cancel, delete, rename, and update-after-submit flows.
• Correct doc_events registration patterns: Covers doc_events structure, wildcard handlers, multiple handlers per event, and the required handler function signature including method.
• Safer multi-app behavior: Clarifies extend vs override behavior across apps, including v16+ extend_doctype_class stacking and v14+ override_doctype_class pitfalls.
• Transaction-aware implementation rules: Highlights when handlers run relative to DB writes and when it’s safe to create linked documents or raise errors.

Quick Start

When wiring up hooks.py for Sales Invoice lifecycle logic, ask an AI to map your required behavior to the exact Frappe event (e.g., validate vs before_validate vs on_submit) and generate correct doc_events code that follows the documented ordering and handler signature.