erpnext-impl-jinja

Organize ERPNext Jinja templating decisions into implementation workflows and decision trees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ERPNext/Jinja implementation decisions can be complex; this skill provides structured workflows, decision trees, and guidelines to determine how to implement print formats, email templates, portal pages, or custom Jinja methods.

Core Features & Use Cases

  • Decision trees guiding print formats, email templates, portal pages, and custom Jinja methods.
  • Implementation workflows from planning to testing, with best practices for context, styling, and compatibility (including V16 Chrome PDF).
  • Use Case: When starting a new ERPNext project, generate a complete Jinja-based template plan including data context, template type, and testing steps.

Quick Start

Describe your ERPNext Jinja task (print format, email template, portal page, or custom method), and I will output a tailored implementation plan.

Frequently Asked Questions about erpnext-impl-jinja

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

FAQPage Schema
How do I structure an ERPNext Jinja print format implementation from planning to testing?

ERPNext Jinja email templates are implemented using decision trees that determine context wiring, data access methods, and security considerations, ensuring dynamic content renders correctly within the ERPNext environment.

When should I use custom Jinja methods instead of standard ERPNext portal pages?

Custom Jinja methods are used over standard ERPNext portal pages when you need specific data access logic or context wiring that default portal page configurations cannot handle, guided by implementation decision trees.

Does ERPNext version 16 require specific considerations for Jinja printable formats?

Yes, ERPNext version 16 requires specific considerations for Jinja printable formats, particularly regarding Chrome PDF compatibility, which standardized implementation workflows address through tailored styling and testing guidelines.

What is the best way to wire data context for ERPNext Jinja templates?

The best way to wire data context for ERPNext Jinja templates is to follow structured decision trees that evaluate template type and data access requirements, ensuring secure and compatible context setup for printable formats and web content.

Why does my ERPNext Jinja print format fail to generate PDFs correctly in v16?

ERPNext Jinja print formats may fail to generate PDFs in v16 due to Chrome PDF compatibility issues, which implementation workflows address by applying specific styling best practices and testing steps for printable formats.