frappe-syntax-doctypes

Define DocType JSON schemas with fieldtypes, naming rules, and relationships.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when creating or modifying DocType JSON definitions, choosing fieldtypes, configuring naming rules, adding child tables, or setting up tree structures. Prevents invalid DocType configurations from wrong fieldtype choices, broken naming rules, and misconfigured child table links. Covers DocType JSON schema, all fieldtypes and their properties, autoname/naming_rule patterns, child table (Table fieldtype), tree DocTypes, virtual DocTypes, Single DocTypes.

Core Features & Use Cases

  • DocType JSON design guidelines
  • Naming rules and auto-naming patterns
  • Tree and virtual DocType guidance
  • Child table design and validation

Quick Start

Open a DocType JSON and apply the canonical fieldtype, naming_rule, and tree-structure guidance to ensure a correct, production-ready schema.

Frequently Asked Questions about frappe-syntax-doctypes

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

FAQPage Schema
How do I configure naming rules and auto-naming patterns in a Frappe DocType JSON?

To configure naming rules in a Frappe DocType, apply the autoname property and naming_rule patterns within the JSON schema to define auto-naming conventions, ensuring unique identifiers and preventing broken record names.

What are the best practices for designing child tables in Frappe?

Best practices for designing Frappe child tables involve using the Table fieldtype and validating link configurations to ensure proper data modeling relationships. This prevents misconfigured child table links and maintains schema integrity within the parent DocType.

How does a tree structure DocType work in Frappe?

A tree structure DocType in Frappe works by configuring specific tree hierarchy properties within the JSON schema, allowing nested data modeling. This guides correct parent-child relationships and prevents invalid structural configurations in hierarchical data.

When should I use virtual DocTypes instead of standard DocTypes in Frappe?

Use virtual DocTypes in Frappe instead of standard DocTypes when you need specific schema designs without underlying database tables. They require awareness of field definitions and anti-patterns to ensure correct schema design and data modeling without physical storage.

How do I choose the correct fieldtypes and indexing for a Frappe DocType?

Choosing correct Frappe DocType fieldtypes and indexing requires applying canonical JSON design guidelines to match data requirements. This prevents invalid configurations from wrong fieldtype choices and ensures production-ready, optimized schema performance.