# Frappe Existing App

> Existing App Workflow

- Skill: `av-dev2/frappe-existing-app` (Agent Skill)
- Install (CLI): `npx skillmds@latest add av-dev2/frappe-existing-app`
- Raw SKILL.md: https://api.skillmd.com/api/skills/av-dev2/frappe-existing-app/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: av-dev2 (https://skillmd.com/u/av-dev2)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/av-dev2/frappe-existing-app

---


# Existing App Workflow

Use this flow when the user wants to extend, modify, or fix an app that already exists.

## Checklist
```
- [ ] Step 1: Find and confirm bench root
- [ ] Step 2: Locate the app
- [ ] Step 3: Confirm site and app installation
- [ ] Step 4: Enable developer mode
- [ ] Step 5: Build / modify features
- [ ] Step 6: Migrate and verify
```

## Step 1: Find and confirm bench root

The bench root is typically the parent of the workspace directory, or the workspace itself. Look for `apps/`, `sites/`, and `Procfile`.

```bash
ls apps/ sites/ Procfile
```

If the workspace is inside the app (e.g. user opened `apps/myapp/`), go up:
```bash
ls ../../apps/ ../../sites/ ../../Procfile
```

## Step 2: Locate the app

```bash
ls apps/
```

Find the app directory. Read its module structure:
```bash
ls apps/<app-name>/<app-name>/
```

Each subdirectory under the module is a Frappe module (contains DocTypes, etc.):
```bash
ls apps/<app-name>/<app-name>/<module-name>/
```

Do NOT create a second app. Do NOT run `bench new-app`.

## Step 3: Confirm site and app installation

See [site-management.md](./site-management.md) for finding the right site for this app.

Verify the app is installed:
```bash
bench --site <site> list-apps
```

If not installed:
```bash
bench --site <site> install-app <app-name>
```

## Step 4: Enable developer mode

```bash
bench set-config -g developer_mode 1
```

## Step 5: Build / modify features

Read the app's existing code to understand patterns before making changes. Load only the relevant feature references from the main SKILL.md table.

Key files to read first:
- `apps/<app>/setup.cfg` or `pyproject.toml` — app metadata
- `apps/<app>/<app>/hooks.py` — existing hooks
- `apps/<app>/<app>/<module>/` — existing DocTypes and modules

## Step 6: Migrate and verify

```bash
bench --site <site> migrate
```

Same rules as new app — see [new-app.md](./new-app.md#step-7-migrate-and-verify) for migrate rules.