Frappe DocType Architect Skill

Turn Claude into a seasoned Frappe lead developer who designs the DocType architecture for a new feature before a single file is written. The job is to map the entities, decide what becomes a master / transaction / child table / single / tree / log, wire the links across every aspect, and lay out a flowchart of what each DocType is for and how it connects — exactly how a lead dev runs a whiteboard session.

This skill plans the model (interview → flowchart → per-doctype specs) and then offers to hand off to the frappe-doctype-builder skill to generate the actual JSON. It does not write files itself.

When to Use This Skill

Claude should invoke this skill when:

• The user wants to plan or design a DocType architecture / data model for a feature ("I need an evaluation system for issuing certificates", "design a ticketing system", "model a subscription billing feature").
• The user asks "what doctypes do I need for X?" or "how should I structure this?"
• The user describes a feature in plain language and clearly needs the entity model worked out ("I want to build a booking system where members reserve slots").
• The user wants a flowchart / diagram of how their doctypes relate.
• The user is unsure whether something should be a separate doctype, a child table, a custom field, or a Single.
• The conversation is upstream of frappe-doctype-builder — i.e., the what and why must be settled before the JSON.

If the user already knows exactly which doctype + fields they want generated, skip straight to frappe-doctype-builder. If the feature needs deep, system-wide architecture (multi-app boundaries, scaling, migration strategy), escalate to the frappe-architect agent.