frappe-syntax-doctypes

Design and validate Frappe DocType schemas with correct field types and naming rules.

Updated May 31, 2026
One-click install
npx skills add https://github.com/anonymousminati/Res-POS --skill frappe-syntax-doctypes-anonymousminati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-syntax-doctypes
Source: https://github.com/anonymousminati/Res-POS/tree/main/.claude/skills/syntax/frappe-syntax-doctypes
Command: npx skills add https://github.com/anonymousminati/Res-POS --skill frappe-syntax-doctypes-anonymousminati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design and modify Frappe DocType schemas without breaking field definitions, naming conventions, child-table links, or tree structures. It reduces schema errors that cause invalid JSON, bad database models, and confusing form behavior.

Core Features & Use Cases

  • DocType JSON design: Define standard, submittable, single, virtual, and child DocTypes correctly.
  • Fieldtype and property guidance: Choose the right field types, validation flags, filters, and layout fields for each use case.
  • Naming and hierarchy rules: Set autoname patterns, naming rules, tree metadata, and parent-child relationships safely.
  • Customization support: Plan custom fields, property setters, data masking, and generated type stubs with Frappe-compatible patterns.
  • Use Case: Use this Skill when building a new business document, fixing a broken child table, or auditing a DocType before deployment.

Quick Start

Ask the skill to review your Frappe DocType JSON and recommend the correct field types, naming rule, and structure.

Frequently Asked Questions about frappe-syntax-doctypes

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

FAQPage Schema
How do I design a valid Frappe DocType JSON schema?

Design Frappe DocType schemas by applying correct field types, naming rules, and document structure to prevent invalid JSON and bad database models. This ensures standard, submittable, single, virtual, and child DocTypes function correctly.

What is the correct way to set up autoname patterns and naming rules in Frappe?

Autoname patterns and naming rules in Frappe define unique document identification safely. Setting these metadata properties correctly during DocType creation prevents naming conflicts and confusing form behavior.

How do I configure parent-child relationships and child tables in a Frappe DocType?

Configure parent-child relationships in Frappe by applying specific linkage rules and the istable metadata property. Defining child DocTypes correctly ensures relational data maps properly without breaking document structure.

Can I use Frappe DocType customization for tree structures and single settings?

Frappe DocType customization supports single settings and tree structures using issingle and is_tree metadata. Applying these flags correctly generates valid hierarchical documents and application-wide configuration models.

Why does my Frappe DocType form behave incorrectly after adding custom fields?

Frappe DocType forms behave incorrectly when custom fields or property setters violate Frappe-specific JSON constraints. Auditing field definitions, validation flags, and layout fields helps fix broken child tables and confusing form behavior.