Master Frappe Framework and ERPNext full-stack development. Build, upgrade, and maintain production-ready Frappe custom apps using the 7-Layer Architecture combined with specialized AI agents for the FULL development lifecycle: development, testing, debugging, bug fixing, installation, remote operations, and performance optimization. ALWAYS trigger for: frappe app, frappe doctype, bench, erpnext, frappe hooks, frappe scheduler, frappe workflow, frappe report, frappe api, frappe controller, "create frappe app", "write doctype", "frappe custom app", "bench migrate", "upgrade frappe", "frappe engine", "frappe webhook", "frappe client script", "frappe server script", "frappe test", "improve frappe", "frappe backend", "frappe frontend", "frappe remote", "remote api", "frappe cloud", "REST API", "curl frappe", "install bench", "setup frappe", "create site", "production setup", "fix bug", "fix error", "solve frappe error", "frappe slow", "optimize query", "web form", "portal", "webform client script", "frappe performance", "frappe install", "bench setup", "frappe permission", "frappe fixture", "frappe workspace", "doc_events", "frappe i18n", "frappe report", "frappe translation", "bench new-app"
From cmnpx claudepluginhub tody-agent/codymaster --plugin cmThis skill uses the workspace's default tool permissions.
agents/doctype-architect.mdagents/erpnext-customizer.mdagents/frappe-backend.mdagents/frappe-custom-frontend.mdagents/frappe-debugger.mdagents/frappe-fixer.mdagents/frappe-frontend.mdagents/frappe-installer.mdagents/frappe-performance.mdagents/frappe-planner.mdagents/frappe-remote-ops.mdagents/github-workflow.mdcommands/frappe-app.mdcommands/frappe-backend.mdcommands/frappe-bench.mdcommands/frappe-debug.mdcommands/frappe-doctype-create.mdcommands/frappe-doctype-field.mdcommands/frappe-erpnext.mdcommands/frappe-fix.mdProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Implements distributed tracing with Jaeger/Tempo for microservices, including Kubernetes/Docker setup and OpenTelemetry instrumentation (Python/Flask). Use for debugging latency, dependencies, and request flows.
To provide a comprehensive lifecycle toolkit for Frappe/ERPNext development — from installation and setup, through development and testing, to debugging, bug fixing, remote operations, and performance optimization. Built on the strict 7-Layer Architecture (separating business logic from the Frappe ORM) with specialized AI Agents for each lifecycle stage.
┌─────────────────────────────────────────────────────────────────────┐
│ FRAPPE DEVELOPMENT LIFECYCLE │
│ │
│ 1. INSTALL → Setup bench, sites, apps [frappe-installer] │
│ 2. PLAN → Architecture, DocType design [frappe-planner] │
│ 3. BUILD → Backend, frontend, full-stack [backend/frontend]│
│ 4. TEST → Unit tests, integration tests [commands/test] │
│ 5. DEBUG → Log analysis, error investigation [frappe-debugger] │
│ 6. FIX → Structured bug fix loop [frappe-fixer] │
│ 7. OPTIMIZE → Performance tuning, caching [frappe-perf] │
│ 8. DEPLOY → Migrate, build, production setup [commands/bench] │
│ 9. OPERATE → Remote API, monitoring [frappe-remote] │
│ │
└─────────────────────────────────────────────────────────────────────┘
You are the orchestrator of the full Frappe development lifecycle. When handling a task, match it to the right lifecycle stage and invoke the appropriate agent.
Always reference the core architectural guidelines before implementing any feature:
See resources/7-layer-architecture.md for comprehensive code examples.
validate, on_submit, etc. No heavy business logic here.@frappe.whitelist endpoints using idempotent upsert patterns.after_install, after_migrate).window.myapp) and list views.agents/doctype-architect.md): Schema, relations, workflow states.agents/frappe-backend.md): Python APIs, controllers, and background jobs.agents/frappe-frontend.md): Client scripts, dialogs, custom formatters.agents/frappe-custom-frontend.md): Custom standalone frontend pages.agents/erpnext-customizer.md): Extending core ERPNext modules safely.agents/frappe-installer.md): Bench setup, site creation, production deployment.agents/frappe-planner.md): Feature planning and technical design.agents/frappe-debugger.md): Error analysis and log investigation.agents/frappe-fixer.md): Structured bug-fix loop (reproduce → diagnose → fix → verify).agents/frappe-performance.md): Query optimization, profiling, caching.agents/frappe-doctor.md): Environment health checks, user record repair, and zombie process cleanup.agents/frappe-remote-ops.md): REST API operations for remote/cloud sites.agents/github-workflow.md): Git operations and CI/CD.skills/doctype-patterns/SKILL.md – Best practices for custom fields, naming rules.skills/server-scripts/SKILL.md – Server-side Python patterns.skills/client-scripts/SKILL.md – JavaScript form/list configurations.skills/frappe-api/SKILL.md – Frappe Framework ORM and Python API usage.skills/bench-commands/SKILL.md – Bench CLI reference.skills/remote-operations/SKILL.md – REST API patterns for remote sites.skills/web-forms/SKILL.md – Web Form development patterns.resources/7-layer-architecture.md – Core architecture with code examples.resources/code-patterns-guide.md – Production code patterns (Layer 1-9 with real code, i18n, CI/CD, strict constraints).resources/bench_commands.md – Managing sites, building, caching.resources/common_pitfalls.md – Things to avoid.resources/scaffold_checklist.md – New app scaffolding.resources/upgrade_patterns.md – Version upgrade patterns.resources/rest-api-patterns.md – REST API curl patterns.resources/doctype-registry.md – DocType discovery and exploration.resources/installation-guide.md – Complete setup guide.resources/web-form-patterns.md – Web Form scripting.hooks.py, Client Scripts, or Custom Fields.fieldname (must be snake_case, e.g., violation_name) and DocType names (must be Title Case, e.g., Warehouse Violation). NEVER use Vietnamese or other non-ASCII characters in schema (name or fieldname). Use Frappe's Translation system or Field Label for localized display text. Non-ASCII names cause Frappe/MariaDB query builder & Insights SQL errors.engines/.frappe.log_error(), NEVER frappe.logger.redis-cli flushall, bench clear-cache, and verify core system users (Guest, Administrator) have enabled=1 and user_type='System User'.bench commands (like --force or drop) without explicit user consent.ignore_permissions=True.