erpnext-impl-clientscripts

Define and implement deterministic ERPNext client-script workflows for UI behavior.

163|53|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package --skill erpnext-impl-clientscripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erpnext-impl-clientscripts
Source: https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package/tree/main/skills/source/impl/erpnext-impl-clientscripts
Command: npx skills add https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package --skill erpnext-impl-clientscripts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deterministic client-script workflows help ERPNext teams implement reliable client-side UI behavior, reducing production issues caused by ad-hoc scripting.

Core Features & Use Cases

  • Guidance on when to run logic on the client vs the server to preserve data integrity and UX.
  • Implementation workflows for common UI tasks: field visibility, validation, cascading filters, and dynamic form interactions.
  • Real-world patterns and examples to accelerate development and ensure consistency across forms and child tables.

Quick Start

Identify a ERPNext form scenario and follow the decision tree to implement the appropriate client-script workflow.

Frequently Asked Questions about erpnext-impl-clientscripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement deterministic ERPNext client scripts for reliable form UI behavior?

Deterministic ERPNext client scripts define reliable client-side UI workflows for field visibility, validation, cascading queries, and dynamic form interactions, replacing ad-hoc scripting to reduce production issues.

When should I run ERPNext form logic on the client vs the server?

Run logic on the client for UI tasks like field visibility and dynamic form interactions, but allocate logic to the server when data integrity is required, using decision trees to guide the split.

How do I add validation and cascading filters to ERPNext child tables using JavaScript?

Implement validation and cascading filters in ERPNext child tables using JavaScript client-script coding patterns, which provide real-world examples for dynamic form interactions and consistent behavior.

What's the best way to handle errors in Frappe client scripts during dynamic form interactions?

Handle errors in Frappe client scripts during dynamic form interactions by applying deterministic coding patterns, which ensure consistent field visibility and validation behavior across forms and child tables.

Can I use client scripts to manage field visibility and dynamic form interactions across ERPNext forms?

Yes, ERPNext client scripts manage field visibility and dynamic form interactions across forms and child tables using deterministic workflows, ensuring reliable client-side UI behavior and consistency.