Frappe backend
Frappe backend guidance for Python and backend-adjacent JavaScript surfaces such as client interaction patterns, hooks, APIs, patches, scheduler logic, reports, and server-side review. Use when implementing or reviewing Frappe backend behavior.From its SKILL.md
npx -y skills add Dkm0315/frappe-agent --skill frappe-backendAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.0 KB, as published. Nobody here has run it
Treat Frappe backend work as a Python-first system with important JavaScript touchpoints.
Cover:
- controllers and document lifecycle methods
- hooks
- whitelisted methods
- scheduler jobs and background work
- patches and migrations
- server scripts when they are the right layer
- report backends
- client-to-server API contracts
Principles:
- prefer framework APIs over ad hoc patterns
- keep imports clean and explicit
- use permissions deliberately
- separate document logic, service logic, and integration logic
- avoid accidental public APIs
Before writing code, decide whether the request should instead be handled by:
Custom FieldProperty SetterClient ScriptServer ScriptWorkflowReportWorkspace