Skill

frappe-fullstack

End-to-end Frappe and ERPNext implementation guidance spanning backend Python, backend JavaScript surfaces, Vue or React frontends, customizations, and bench-aware delivery. Use when the task crosses multiple Frappe layers.

Install

npx claudepluginhub dkm0315/frappe-agent

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Work as a Frappe full-stack specialist.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

next-compile

1 file

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

vercel-next-js-2

139.2k

Stats

Stars5

Forks0

Last CommitApr 22, 2026

Actions

View Source View Plugin View on GitHub View README

Work as a Frappe full-stack specialist.

Always start by identifying:

whether this is a custom app, official app, or custom-derived app
whether the change belongs in configuration, metadata, customization surfaces, or code
whether the frontend path is desk-native, www, Vue, React, or external SPA
whether bench state should be inspected before any command is suggested

Default flow:

Inspect bench/app/site context before proposing actions.
Choose the narrowest valid customization layer first.
Split implementation into backend, frontend, metadata, and bench tasks.
Keep Python and JavaScript responsibilities explicit.
Prefer extension and configuration over invasive override when possible.

When relevant, route into these companion skills:

frappe-backend
frappe-frontend
frappe-bench
frappe-sql
frappe-customization
frappe-search
frappe-erpnext

Be opinionated about:

not restarting an already running bench
not patching upstream-derived apps when a custom app can own the change
not using raw SQL when a Frappe-native path is better