Impertio-Studio/Frappe_Claude_Skill_Package

Controller Errors helps debug and prevent Frappe Document Controller failures across naming, validation, save, submit, cancel, and permission hooks. Use it to trace lifecycle-phase errors in v14/v15/v16 and fix recursion, missing super() calls, and submit configuration issues.

Frappe API Errors explains common REST and webhook failure modes in Frappe and ERPNext, including 401, 403, 404, 417, 429, 500, CSRF, CORS, and upload issues. Use it when debugging API calls, authentication, or response handling.

Frappe Agent Architect designs multi-app Frappe and ERPNext architectures, including when to split apps, how to set dependencies, and how to structure cross-app hooks and overrides. Use it before coding to avoid monolithic app sprawl and circular dependencies.

Frappe Agent Migrator plans Frappe and ERPNext major-version upgrades, scans custom code for breaking API changes, and suggests fixes for migration errors. Use it when moving between versions or diagnosing failures after an update.

Frappe Cache & Locking covers Redis caching, cache invalidation, and distributed locking in Frappe. Use it to avoid stale data, repeated slow queries, and race conditions when data changes.

Frappe Client Script Errors helps debug and prevent common Frappe client script failures like TypeError, frappe.call issues, async mistakes, child table access errors, CSRF problems, and save-time validation mistakes. Use it when a script breaks, a field does not update, or a call fails in v14 to v16.

Frappe Client Scripts gives step-by-step patterns for building client-side form behavior in Frappe and ERPNext, including field visibility, filters, buttons, validation, calculations, and server calls. Use it when implementing or debugging form logic that runs in the browser.

Frappe Code Interpreter turns vague ERPNext and Frappe development requests into concrete technical specifications. It identifies the trigger, mechanism, and required frappe-* skills when the request is unclear or has multiple implementation paths.

Frappe Code Validator reviews Frappe and ERPNext code against best practices, version patterns, and deployment checks. It is used before deployment or when debugging code, scripts, hooks, or bench setup.

Frappe Core API covers REST, RPC, webhook, and authentication patterns for ERPNext/Frappe integrations. Use it to connect external systems, call server methods, handle 401s, and work with rate limits.

Frappe Core Files covers file uploads, attachments, private/public access, and S3 storage in Frappe. Use it to save, read, attach, or serve files without broken links or permission mistakes.

Frappe Core Utils helps you use frappe.utils for dates, numbers, strings, validation, and file paths in Frappe v14-v16. It is useful when you need timezone-aware, locale-aware helpers instead of Python stdlib shortcuts.

Frappe Database Errors helps diagnose and fix common Frappe and ERPNext database exceptions such as duplicate entries, validation errors, deadlocks, and connection issues. Use it when handling `frappe.db.sql()`, `get_value()`, or save-time failures.

Frappe Database Operations helps you read, write, and query ERPNext/Frappe data with the right API, from `frappe.get_doc` and `frappe.db.get_list` to query builder and SQL. Use it when building database logic, caching values, or avoiding permission and transaction mistakes.

Frappe Debugger helps diagnose Frappe and ERPNext errors by classifying tracebacks, checking logs, and inspecting live state in bench console. Use it for Python, JavaScript, database, permission, scheduler, and build issues.

Frappe Document Controllers explains how to implement DocType logic in a custom Frappe app, including validation, lifecycle hooks, autoname, submittable workflows, controller overrides, child table controllers, and flags.

Frappe Hooks Error Diagnosis helps debug hooks.py failures in Frappe and ERPNext, including wrong dict structure, circular imports, path errors, scheduler issues, and broken overrides. Use it when a hook does not fire or an import, SQL, or fixture error appears.

Frappe Logging shows how to use frappe.logger() and frappe.log_error() for file logs, Error Log entries, request logging, Sentry, and production monitoring in Frappe v14-v16. It helps avoid print() in production, swapped log_error arguments, and logging sensitive data.

Frappe Notifications covers email, system alerts, assignments, auto repeats, and ToDo creation in Frappe. Use it when configuring document-triggered notifications or programmatic messaging without misconfigured delivery or templates.

Frappe Permission Errors helps debug PermissionError, has_permission hooks, User Permission filtering, perm_level access, sharing, guest access, and list-view restrictions in Frappe/ERPNext. Use it when document or API access is blocked by permissions.

Frappe Permissions explains how to implement Frappe and ERPNext access control using roles, user permissions, perm levels, masking, and permission hooks. Use it when checking who can see, edit, or restrict documents and fields.

Frappe Search explains how to implement link field autocomplete, global search, website search, and custom FTS in Frappe v14-v16. Use it when search results are missing, autocomplete is not working, or you need to tune indexing and permissions.

Frappe Server Script Errors helps debug and prevent common Frappe Server Script failures such as ImportError, restricted builtins, sandbox violations, wrong script type, permission issues, and missing API responses.

Frappe Translation helps implement i18n in Frappe v14-v16 apps using _(), __(), _lt(), CSV/PO files, and bench extraction commands. Use it when adding translated strings or fixing text that does not extract correctly.

Frappe Workflow Engine manages Frappe document lifecycles with workflow states, transitions, role permissions, and action conditions. Use it to create or troubleshoot approval flows, stuck documents, and workflow permission errors.