erpnextlisted

# ERPNext / Frappe — core knowledge skill This skill gives an agent the *core* knowledge needed to operate a running ERPNext instance correctly: the data model (what DocTypes exist and how they relate), how to talk to the system (bench CLI + the API), and a module-by-module map of the business domain. It is **knowledge**, not a workflow runbook — for opinionated back-office procedures (bookkeeping, AR/AP, audit reconciliation) see the companion `shicheng-agents/claude-skills` repo, which builds *on top of* the facts here. > **Targets Frappe/ERPNext v14–v16.** Where versions diverge (e.g. subcontracting was > reworked in v15, HR/CRM split into separate apps), the references call it out. > This is distilled from the official docs at <https://docs.frappe.io/erpnext/> and > <https://docs.frappe.io/framework/>. Verify against the live instance — see > "Introspect the live system" below — because every site can be customized. ## The one mental model: everything is a DocType Frappe is a **metadata-driven, full-stack web framework** (Python + a Vue/JS desk UI). ERPNext is a large set of apps built on it. The single most important idea: > **Every "thing" in the system — a Sales Invoice, a Customer, even configuration like > "Stock Settings" — is a `DocType`. A DocType is a model definition; each record is a > `Document` (`doc`). Most DocTypes are backed by a SQL table named `tab<DocType>`** (so > `Sales Invoice` → `tabSales Invoice`). If you understand DocTypes, fieldtypes, the