frappe-syntax-customapp

To scaffold a Frappe custom app correctly, you need the proper v14-v16 layout including pyproject.toml, __init__.py, hooks, modules.txt, and package directories. This ensures your app installs and updates without breaking bench workflows.

Correct pyproject.toml configuration for a Frappe custom app requires accurate package naming, __version__ exports, and Frappe dependency declarations. Properly defining these metadata fields prevents packaging failures during bench install and update operations.

Setting up patches and fixtures in a Frappe app involves registering modules and defining safe migration patterns in your hooks. This Skill guides you through app extension patterns for custom fields, property setters, and data migrations.

Yes, this Frappe scaffolding guidance works for extending an existing ERPNext installation. It covers app extension patterns for custom fields and property setters, ensuring your customizations remain stable and installable across bench-based development workflows.

Your Frappe custom app breaks during bench install or update due to missing structure, packaging metadata, module registration, or migration conventions. Validating your app structure against v14-v16 standards fixes these installable app bundle errors.

Yes, you need to register modules in modules.txt for a Frappe custom app. Proper module registration alongside correct hooks and pyproject.toml configuration is required to maintain stable, installable customizations across v14-v16 app structures.