How do I install the Frappe New App skill?

Run npx skillmds@latest add av-dev2/frappe-new-app 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 New App safe to use?

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

Which AI agents work with Frappe New App?

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 New App free to use?

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

Who published Frappe New App?

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

Frappe New App by av-dev2 — Agent Skill

Name: Frappe New App
Rating: 4.5 (4 reviews)
Author: av-dev2

File contents

New App Workflow

Follow these steps in order. Do not skip steps.

Checklist

- [ ] Step 1: Confirm bench root
- [ ] Step 2: Enable developer mode
- [ ] Step 3: Pick or create site
- [ ] Step 4: Create app
- [ ] Step 5: Install app on site
- [ ] Step 6: Build features
- [ ] Step 7: Migrate and verify

Step 1: Confirm bench root

ls apps/ sites/ Procfile

If it succeeds, bench is valid. Do not run anything else to verify.

Step 2: Enable developer mode

bench set-config -g developer_mode 1

Step 3: Pick or create site

See site-management.md for finding or creating a site.

Complete this step before proceeding. You need a working site first.

Step 4: Create app

The bench new-app command MUST use piped printf. No heredoc (<<EOF). No --no-input. No --no-git. No bare bench new-app <name> without pipe.

Ask user for: app name, title, description, publisher, email, license.

printf '<title>\n<description>\n<publisher>\n<email>\n<license>\nN\nN\nN\n' | bench new-app <app-name>

Example:

printf 'Expense Tracker\nTrack expenses\nJohn\njohn@example.com\nmit\nN\nN\nN\n' | bench new-app expense_tracker

Verify:

ls apps/<app-name>

Step 5: Install app on site

bench --site <site> install-app <app-name>
bench --site <site> list-apps  # verify

Step 6: Build features

Write DocTypes, controllers, hooks, permissions, UI directly in the app module directory created in step 4.

The app structure after bench new-app myapp:

apps/myapp/
  myapp/
    myapp/          ← module directory (same name as app)
      __init__.py
    hooks.py
    __init__.py
  setup.py

Load the relevant feature references from the main SKILL.md table as needed.

Step 7: Migrate and verify

bench --site <site> migrate

Rules:

Always pass --site <site> explicitly. Never run bare bench migrate.
After migration succeeds, do NOT query the database directly to verify schema changes. Frappe's migrate output is the source of truth.
If migrate fails with SyntaxError, fix the file first, then re-run.

Start bench in background if not already running:

bench start

Get URL:

bench --site <site> execute frappe.utils.get_url

---name: frappe-new-appdescription: Workflow for scaffolding a new Frappe app, bench setup, site creation, and installing the app.---# New App WorkflowFollow these steps in order. Do not skip steps.## Checklist```- [ ] Step 1: Confirm bench root- [ ] Step 2: Enable developer mode- [ ] Step 3: Pick or create site- [ ] Step 4: Create app- [ ] Step 5: Install app on site- [ ] Step 6: Build features- [ ] Step 7: Migrate and verify```## Step 1: Confirm bench root```bashls apps/ sites/ Procfile```If it succeeds, bench is valid. Do not run anything else to verify.## Step 2: Enable developer mode```bashbench set-config -g developer_mode 1```## Step 3: Pick or create siteSee [site-management.md](./site-management.md) for finding or creating a site.Complete this step before proceeding. You need a working site first.## Step 4: Create appThe `bench new-app` command MUST use piped `printf`. No heredoc (`<<EOF`). No `--no-input`. No `--no-git`. No bare `bench new-app <name>` without pipe.Ask user for: app name, title, description, publisher, email, license.```bashprintf '<title>\n<description>\n<publisher>\n<email>\n<license>\nN\nN\nN\n' | bench new-app <app-name>```Example:```bashprintf 'Expense Tracker\nTrack expenses\nJohn\njohn@example.com\nmit\nN\nN\nN\n' | bench new-app expense_tracker```Verify:```bashls apps/<app-name>```## Step 5: Install app on site```bashbench --site <site> install-app <app-name>bench --site <site> list-apps # verify```## Step 6: Build featuresWrite DocTypes, controllers, hooks, permissions, UI directly in the app module directory created in step 4.The app structure after `bench new-app myapp`:```apps/myapp/ myapp/ myapp/ ← module directory (same name as app) __init__.py hooks.py __init__.py setup.py```Load the relevant feature references from the main SKILL.md table as needed.## Step 7: Migrate and verify```bashbench --site <site> migrate```**Rules:**- Always pass `--site <site>` explicitly. Never run bare `bench migrate`.- After migration succeeds, do NOT query the database directly to verify schema changes. Frappe's migrate output is the source of truth.- If migrate fails with `SyntaxError`, fix the file first, then re-run.Start bench in background if not already running:```bashbench start```Get URL:```bashbench --site <site> execute frappe.utils.get_url```

Frequently asked questions

Frappe New App