frappe-doctype

Generate Frappe v15 DocType scaffolds with controllers, services, repositories, and tests.

15|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/sergio-bershadsky/ai --skill frappe-doctype
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-doctype
Source: https://github.com/sergio-bershadsky/ai/tree/main/plugins/frappe-dev/skills/frappe-doctype
Command: npx skills add https://github.com/sergio-bershadsky/ai --skill frappe-doctype

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a production-ready Frappe v15 DocType scaffold with a controller, service layer, repository, and tests that enforce a clean, multi-layer architecture.

Core Features & Use Cases

  • Generates a full DocType skeleton including JSON schema, Python controller, service, repository, and tests.
  • Enforces v15 type annotations and lifecycle hooks templates (before_validate, before_save, on_submit, on_cancel, etc.).
  • Supports Standard, Submittable, Child Table, and Single DocTypes for modular development workflows.

Quick Start

Provide the DocType name and optional module to generate a complete multi-layer DocType scaffold.

Frequently Asked Questions about frappe-doctype

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

FAQPage Schema
How do I scaffold a Frappe v15 DocType with a service layer and repository?

Scaffold a Frappe v15 DocType by generating a multi-layer architecture skeleton that includes a Python controller, service layer, repository, and tests alongside the JSON schema.

What lifecycle hooks are needed for a submittable Frappe DocType?

Submittable Frappe DocTypes require lifecycle hook templates for before_validate, before_save, on_submit, and on_cancel to manage state transitions and enforce business logic.

Does this Frappe DocType generator support child tables and single types?

This generator supports Standard, Submittable, Child Table, and Single DocTypes, applying mandatory field definitions and naming conventions across all modular development workflows.

How do I enforce TYPE_CHECKING annotations and test coverage in Frappe?

Enforce TYPE_CHECKING annotations and comprehensive test coverage by generating a DocType scaffold that applies separation of concerns and index-aware data access across the service and repository layers.

What's the best way to structure a production-ready Frappe DocType architecture?

Structure a production-ready Frappe DocType using a clean, multi-layer architecture that separates controllers, services, and repositories to ensure maintainability and index-aware data access.