SkillsAdd

lubusin/frappe-skills

router

Route to the appropriate Frappe skill based on task type. Use as the entry point when working on Frappe projects to determine which specialized skill to apply.

First seen Aug 4, 2026

Installation

$ npx skills add lubusin/frappe-skills --skill router
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

expo-router Similar name
expo/skills

Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and d…

14.7K installs
clerk-react-router-patterns Similar name
clerk/skills

React Router v7/v8 patterns with Clerk — rootAuthLoader, getAuth in loaders, clerkMiddleware, p…

12.7K installs
nano-banana-pro-openrouter Similar name
github/awesome-copilot

Generate or edit images via OpenRouter with the Gemini 3 Pro Image model. Use for prompt-only i…

9.9K installs
wordpress-router Similar name
wordpress/agent-skills

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg bloc…

4.2K installs
dynamo-router-starter Similar name
nvidia/skills

Start or patch Dynamo router modes and run router endpoint smoke checks. Use for round-robin, K…

1.9K installs
sentry-react-router-framework-sdk Similar name
getsentry/sentry-for-ai

Full Sentry SDK setup for React Router Framework mode. Use when asked to "add Sentry to React R…

1.6K installs

Also in this package

Other skills from lubusin/frappe-skills · top by installs.

npx skills add lubusin/frappe-skills
frappe-app-development 304 frappe-frontend-development 294 frappe-doctype-development 254 frappe-manager 250 frappe-api-development 250 frappe-desk-customization 244 frappe-router 230 frappe-ui-patterns 226 frappe-testing 222 frappe-reports 212

Browse all from lubusin/frappe-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 57
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,058 B
  • docs SUMMARY.md 173 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 55 installs

SKILL.md

Frappe Router

Route to the appropriate Frappe skill based on your task.

When to use

  • First step when starting any Frappe-related work
  • To determine which specialized skill applies to your task

Procedure

0) Identify task type

Task Skill
Understand project structure, versions, apps → project-triage
Scaffold new app, hooks, architecture, background jobs → app-development
Create/modify DocTypes, fields, controllers → doctype-development
Build REST/RPC APIs, webhooks, integrations → api-development
Customize Desk UI, form scripts, list views, JS API → desk-customization
Build Vue 3 frontends with Frappe UI, portals → frontend-development
UI/UX patterns from CRM/Helpdesk/HRMS → ui-patterns
Create print formats, email templates, Jinja, PDFs → printing-templates
Build reports (Builder, Query, Script) → reports
Create public web forms for data collection → web-forms
Write or run tests → testing
Set up dev environment with Docker/FM → frappe-manager
Build CRM/Helpdesk/enterprise systems → enterprise-patterns

1) Run triage first (recommended)

Before deep work, run project-triage to understand:

  • Project type (bench/FM/standalone)
  • Frappe version
  • Installed apps
  • Available tooling

2) Combine skills as needed

Complex tasks may require multiple skills:

  • New app = app-development + doctype-development + api-development + testing
  • Feature with UI = doctype-development + desk-customization + api-development
  • Custom frontend = frontend-development + api-development
  • Document workflow = doctype-development + printing-templates + reports
  • Enterprise app = enterprise-patterns + doctype-development

Quick decision tree

Is this about understanding the project?
  → project-triage

Is this about creating a new app or app architecture?
  → app-development

Is this about data models or DocTypes?
  → doctype-development

Is this about APIs or external access?
  → api-development

Is this about Desk UI, form scripts, or client-side JS?
  → desk-customization

Is this about a Vue 3 frontend or portal?
  → frontend-development

Is this about UI/UX patterns or app design?
  → ui-patterns

Is this about print formats, PDFs, or Jinja templates?
  → printing-templates

Is this about reports or data analysis views?
  → reports

Is this about public web forms?
  → web-forms

Is this about testing?
  → testing

Is this about local dev environment?
  → frappe-manager

Is this a complex enterprise system?
  → enterprise-patterns

Guardrails

  • Always run triage first before making code changes to unknown projects
  • Check Frappe version before recommending features (API availability varies significantly between v13, v14, v15, v16)
  • Don't assume ERPNext - many projects use Frappe Framework without ERPNext
  • Verify site context - commands like bench migrate affect specific sites

Common Mistakes

Mistake Why It Fails Fix
Skipping project triage Applying wrong patterns for version Always run triage first
Using ERPNext-specific code in Frappe-only projects Module not found errors Check installed apps first
Wrong skill for task Incomplete implementation Match task type to skill carefully
Ignoring version differences Deprecated/missing APIs Check version compatibility in skill references
Working on wrong site Changes don't appear Always specify --site flag
Using vanilla JS/jQuery for frontends Ecosystem mismatch Use Frappe UI (Vue 3) via frontend-development
Custom app shell for CRUD apps Inconsistent UX Follow CRM/Helpdesk patterns via enterprise-patterns