Dkm0315/frappe-agent / skills/frappe-fullstack
frappe-fullstack
VerifiedEnd-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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
SKILL.md
View on GitHub---
name: frappe-fullstack
description: 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.
---
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:
1. Inspect bench/app/site context before proposing actions.
2. Choose the narrowest valid customization layer first.
3. Split implementation into backend, frontend, metadata, and bench tasks.
4. Keep Python and JavaScript responsibilities explicit.
5. 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-doctype-design`
- `frappe-search`
- `frappe-erpnext`
- `frappe-crm`
- `frappe-helpdesk`
- `frappe-lms`
- `frappe-gameplan`
- `frappe-drive`
- `frappe-hrms`
- `frappe-insights`
- `frappe-builder`
- `frappe-payments`
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |