How do I install the Frappe App Dev skill?

Run npx skillmds@latest add frappe/frappe-app-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Frappe App Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Frappe App Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Frappe App Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Frappe App Dev?

frappe (@frappe) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Frappe App Dev by frappe — Agent Skill

Name: Frappe App Dev
Rating: 4.666666666666667 (3 reviews)
Author: frappe

Frappe App Dev

Builds full-stack Frappe Framework applications end-to-end. Use this skill any time the user mentions: creating or modifying a DocType, writing a controller or lifecycle hook, adding a whitelisted API, setting up a new Frappe app or bench site, building a desk form or list view, creating portal pages, writing background jobs or scheduled tasks, managing permissions or roles, writing Frappe tests, or working with frappe.db / frappe.qb. Also applies when the user says things like "how do I hook into save", "add a field to a DocType", "create a REST endpoint in Frappe", "run bench migrate", or "install an app on a site" — even if they don't explicitly say "Frappe".

frappe de0f4e6 19 files · 50.1 KB Updated Sep 9, 2026

File contents

Frappe Full-Stack App Builder

Global Rules

Use bare bench. Not ./env/bin/bench. Not a full path.
Do not run which bench, bench --version, bench --help, or check frappe version. No discovery commands.
Do not delegate bench detection to a subagent. Run ls apps/ sites/ Procfile yourself.
Do not create DocType folders with mkdir. Frappe creates them via bench migrate.
Run bench start in a background process only.
Before running bench start, check if it's already running in an existing terminal. Do not start a second instance.
Always pass --site <site> explicitly to bench commands. Never run bare bench migrate.

Flow Selection

Determine which flow applies, then read ONLY the relevant file:

Creating a brand new app

Read new-app.md — covers bench setup, app scaffolding, site creation, and installation.

Working on an existing app

Read existing-app.md — covers finding the bench, locating the app, confirming site, and extending features.

Feature References

Load ONLY the references needed for the current task:

Topic	When to load	File
Site management	Finding/creating/managing sites	site-management.md
DocTypes	Creating/modifying DocTypes, fields, naming	doctypes.md
Controllers	Document lifecycle, server logic	controllers.md
Whitelisted APIs	REST endpoints, `@frappe.whitelist()`	api.md
Database & ORM	`frappe.db`, queries, raw SQL	database.md
Caching	Redis, `frappe.cache`	caching.md
Realtime	WebSocket, `publish_realtime`	realtime.md
Background jobs	`frappe.enqueue`, scheduled jobs	background-jobs.md
Hooks	`hooks.py` patterns	hooks.md
Permissions	Roles, DocType permissions, `has_permission`	permissions.md
Testing	Writing & running tests	testing.md
Frontend & UI	Desk UI, Vue SPA, portal pages	frontend.md (router → 3 sub-files)
Bench CLI	All bench commands reference	bench-operations.md

---name: frappe-app-devdescription: Builds full-stack Frappe Framework applications end-to-end. Use this skill any time the user mentions: creating or modifying a DocType, writing a controller or lifecycle hook, adding a whitelisted API, setting up a new Frappe app or bench site, building a desk form or list view, creating portal pages, writing background jobs or scheduled tasks, managing permissions or roles, writing Frappe tests, or working with frappe.db / frappe.qb. Also applies when the user says things like "how do I hook into save", "add a field to a DocType", "create a REST endpoint in Frappe", "run bench migrate", or "install an app on a site" — even if they don't explicitly say "Frappe".--- # Frappe Full-Stack App Builder ## Global Rules - Use bare `bench`. Not `./env/bin/bench`. Not a full path. - Do not run `which bench`, `bench --version`, `bench --help`, or check frappe version. No discovery commands. - Do not delegate bench detection to a subagent. Run `ls apps/ sites/ Procfile` yourself. - Do not create DocType folders with `mkdir`. Frappe creates them via `bench migrate`. - Run `bench start` in a background process only. - Before running `bench start`, check if it's already running in an existing terminal. Do not start a second instance. - Always pass `--site <site>` explicitly to bench commands. Never run bare `bench migrate`. ## Flow Selection Determine which flow applies, then read ONLY the relevant file: ### Creating a brand new app Read [new-app.md](./references/new-app.md) — covers bench setup, app scaffolding, site creation, and installation. ### Working on an existing app Read [existing-app.md](./references/existing-app.md) — covers finding the bench, locating the app, confirming site, and extending features. ## Feature References Load ONLY the references needed for the current task: | Topic | When to load | File | | ---------------- | -------------------------------------------- | ------------------------------------------------------- | | Site management | Finding/creating/managing sites | [site-management.md](./references/site-management.md) | | DocTypes | Creating/modifying DocTypes, fields, naming | [doctypes.md](./references/doctypes.md) | | Controllers | Document lifecycle, server logic | [controllers.md](./references/controllers.md) | | Whitelisted APIs | REST endpoints, `@frappe.whitelist()` | [api.md](./references/api.md) | | Database & ORM | `frappe.db`, queries, raw SQL | [database.md](./references/database.md) | | Caching | Redis, `frappe.cache` | [caching.md](./references/caching.md) | | Realtime | WebSocket, `publish_realtime` | [realtime.md](./references/realtime.md) | | Background jobs | `frappe.enqueue`, scheduled jobs | [background-jobs.md](./references/background-jobs.md) | | Hooks | `hooks.py` patterns | [hooks.md](./references/hooks.md) | | Permissions | Roles, DocType permissions, `has_permission` | [permissions.md](./references/permissions.md) | | Testing | Writing & running tests | [testing.md](./references/testing.md) | | Frontend & UI | Desk UI, Vue SPA, portal pages | [frontend.md](./references/frontend.md) (router → 3 sub-files) | | Bench CLI | All bench commands reference | [bench-operations.md](./references/bench-operations.md) |

Frequently asked questions