Cursor rule

1---
2description:
3globs:
4alwaysApply: false
5---
6---
7name: Moodle Events and Callbacks
8---
9 
10# Moodle Events and Callbacks
11 
12## Purpose
13Ensure extensibility and modularity by using Moodle's event and callback systems.
14 
15## Instructions
16- Use Moodle's event API to trigger and observe events
17- Define custom events in `db/events.php`
18- Use `core\event` classes for core events
19- Register observers in `db/events.php`
20- Use callbacks for plugin extensibility (e.g., `myplugin_callback()`)
21- Document all custom events and callbacks
22- Avoid direct function calls between plugins; use events or callbacks
23 
24## Examples
25```php
26// File: ./db/events.php
27$observers = [
28    [
29        'eventname'   => '\core\event\user_loggedin',
30        'callback'    => 'local_myplugin_user_loggedin',
31    ],
32];
33 
34// File: ./lib.php
35function local_myplugin_user_loggedin($event) {
36    // Handle user login event
37}
38```
39 
40## Exceptions
41- Performance-critical code may use direct calls with justification
42