Generate DocType Controller

Scaffold class-based Frappe DocType controllers with lifecycle hooks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ATXINVOX/frappe-microservices-poc --skill generate-doctype-controller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Generate DocType Controller
Source: https://github.com/ATXINVOX/frappe-microservices-poc/tree/main/.cursor/skills/generate-controller
Command: npx skills add https://github.com/ATXINVOX/frappe-microservices-poc --skill generate-doctype-controller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating DocType controllers by hand can lead to inconsistent lifecycle methods and boilerplate. This Skill automates scaffolding of class-based controllers with standard hooks (validate, before_insert, after_insert, before_update, after_update, before_delete), ensuring a uniform architecture across DocTypes.

Core Features & Use Cases

  • Scaffold class-based controllers with the full set of lifecycle hooks to enforce business rules and data integrity.
  • Enforce consistent file structure, naming conventions, and reusable method skeletons for rapid development.
  • Provide ready-to-use patterns that align with frappe_microservice-lib patterns, reducing onboarding time for new projects.
  • Use Case: Create a new DocType controller across multiple services with a single command, then customize business logic as needed.

Quick Start

Run this skill to scaffold a new DocType controller and register it in your Frappe service.

Frequently Asked Questions about Generate DocType Controller

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

FAQPage Schema
How do I generate a Frappe DocType controller with standard lifecycle hooks?

Yes, scaffolding Frappe controllers enforces consistent file structures and standard lifecycle methods across DocTypes. This approach eliminates boilerplate, ensures uniform architecture, and reduces onboarding time for new frappe_microservice-lib projects.

What lifecycle methods are included when scaffolding a DocType controller in Frappe?

Scaffolding a DocType controller includes the full set of Frappe lifecycle methods: validate, before_insert, after_insert, before_update, after_update, and before_delete. These hooks are generated as ready-to-use skeletons to enforce business rules and data integrity.

Can I use this scaffolding tool for a Frappe-based microservice architecture?

To create a new DocType controller in Frappe, run this skill to scaffold the class-based controller and register it in your service. You then customize the generated lifecycle hook skeletons with your specific business logic as needed.

Why do I need to auto-generate Frappe controllers instead of writing them manually?

You need to auto-generate Frappe controllers because manual creation leads to inconsistent lifecycle methods and boilerplate code. Automated scaffolding enforces a uniform architecture with reusable patterns, standardizing development and accelerating rapid project setup.