frappe-errors-clientscripts
byimpertio-studio· 58 skills
Use when debugging or preventing errors in Frappe Client Scripts. Prevents TypeError, frappe.call failures, async/await mistakes, cur_frm vs frm confusion, field not found, child table access errors, timing issues, CSRF token errors, and permission denied on frappe.call. Covers error diagnosis flowchart and debug tools for v14/v15/v16. Keywords: client script error, TypeError, frappe.call, async await,, Cannot read properties of undefined, TypeError, browser console error, script not running, form not updating. cur_frm, field not found, child table, CSRF, permission denied.
How to install frappe-errors-clientscripts?
impertio-studio/frappe_claude_skill_package/frappe-errors-clientscripts
$npx -y skills add impertio-studio/frappe_claude_skill_package --skill frappe-errors-clientscriptsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/impertio-studio/frappe_claude_skill_package" --skill "impertio-studio/frappe_claude_skill_package/frappe-errors-clientscripts"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/impertio-studio/frappe_claude_skill_package" that are relevant to the current task. Run `npx skills add "https://github.com/impertio-studio/frappe_claude_skill_package"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.Jul 2026
- appinsights-instrumentationGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references.Jul 2026
- diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Jul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work.Jul 2026
- golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single…Jul 2026
