erpnext-syntax-jinja

Provide deterministic Jinja templating guidance for ERPNext Print Formats, Email Templates, and Portal Pages.

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-syntax-jinja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erpnext-syntax-jinja
Source: https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package/tree/main/skills/source/syntax/erpnext-syntax-jinja
Command: npx skills add https://github.com/OpenAEC-Foundation/ERPNext_Anthropic_Claude_Development_Skill_Package --skill erpnext-syntax-jinja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ERPNext template authors often struggle with inconsistent Jinja usage across Print Formats, Email Templates, and Portal Pages, leading to production errors and hard-to-maintain code.

Core Features & Use Cases

  • Deterministic Jinja behavior across ERPNext/Frappe versions (v14/v15/v16)
  • Context-aware templating guidance for Print Formats, Email Templates, and Portal Pages
  • Guidelines for translations, formatting, and safe rendering

Quick Start

Load and apply ERPNext Jinja templates using the examples to format print formats, emails, and portal pages.

Frequently Asked Questions about erpnext-syntax-jinja

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

FAQPage Schema
How do I write deterministic Jinja templates for ERPNext Print Formats?

Use this Skill to apply deterministic Jinja syntax rules for ERPNext Print Formats, Email Templates, and Portal Pages. It provides consistent guidance on context objects, formatting methods, and safe rendering across Frappe v14 through v16.

Why does my ERPNext Jinja email template render inconsistently across Frappe versions?

ERPNext Jinja template inconsistencies across Frappe v14-v16 happen when context objects and formatting methods are misapplied. Applying deterministic templating guidelines ensures consistent rendering and prevents production errors.

Does this Jinja templating guidance apply to Frappe v16 portal pages?

Yes, this Jinja templating guidance applies to Frappe v16 portal pages. It covers context-aware templating, safe rendering rules, and frontmatter compliance for ERPNext v14 through v16 environments.

What are the safe rendering rules for Jinja in ERPNext Email Templates?

Safe rendering rules for Jinja in ERPNext Email Templates involve enforcing translation, formatting, and frontmatter compliance. Following these templating best practices prevents hard-to-maintain code and production errors.

What's the best way to avoid Jinja templating inconsistencies in ERPNext?

The best way to avoid Jinja templating inconsistencies in ERPNext is to use deterministic guidance for context objects and custom hooks. This enforces functional requirements and safe usage across Print Formats and Portal Pages.