frappe-ops-app-lifecycle

Guide Frappe app lifecycle operations from scaffolding to marketplace publishing.

163|53|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-app-lifecycle-impertio-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-ops-app-lifecycle
Source: https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-app-lifecycle
Command: npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-app-lifecycle-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents broken Frappe app scaffolding, missing configuration, and failing builds/tests by guiding you through the full bench-driven app lifecycle with correct, production-safe steps.

Core Features & Use Cases

  • Scaffold and structure correctly: Produces a valid app directory layout and ensures setup.py/pyproject.toml and hooks.py essentials are in place before you build anything.
  • Run the right bench workflow: Covers migrate, build, run-tests, and restart in the correct order so schema changes and compiled assets stay consistent.
  • Install/update/publish safely: Provides best practices for dependency ordering, patch timing, production-mode configuration, and preparing an app for the Frappe Marketplace.
  • Use Case: When creating a brand-new custom ERPNext app and you need it to pass migrations, compile assets, run tests, and publish without hidden structural mistakes.

Quick Start

Use the frappe-ops-app-lifecycle skill to generate a safe, end-to-end command plan for scaffolding a new Frappe app, running migrate/build/tests, and preparing it for marketplace publishing.

Frequently Asked Questions about frappe-ops-app-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new Frappe app and structure it correctly?

To scaffold a Frappe app, use bench commands to generate the directory layout, ensuring setup.py or pyproject.toml and hooks.py files are configured before running builds or migrations to prevent structural failures.

What is the correct bench command sequence for Frappe migrations and asset builds?

The correct sequence for Frappe app updates is running migrate, build, run-tests, and restart in strict order so schema changes and compiled assets remain consistent across the bench environment.

How do I prepare a Frappe app for marketplace publishing?

Marketplace publishing requires following best practices for dependency ordering, patch timing, production-mode configuration, and passing tests to ensure the Frappe app is ready for release without hidden mistakes.

Do I need developer_mode disabled for production Frappe app deployment?

Production Frappe app deployment requires safe guardrails like disabling developer_mode, ensuring assets are compiled, and taking backups before executing bench migrations or app updates on client sites.

Why does my custom ERPNext app fail migrations after installing dependencies?

Custom ERPNext app migrations fail when setup.py or pyproject.toml and hooks.py structures are missing or incorrect, preventing deterministic operational outcomes during the bench-driven app lifecycle.