router

Routes Frappe development tasks to the appropriate specialized skill based on task type.

62|23|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/lubusIN/frappe-skills --skill router-lubusin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: router
Source: https://github.com/lubusIN/frappe-skills/tree/main/router
Command: npx skills add https://github.com/lubusIN/frappe-skills --skill router-lubusin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on Frappe projects, it is hard to know which specialized skill applies to a given task, and choosing the wrong one leads to incomplete implementations, version-incompatible code, or ERPNext-specific patterns in Frappe-only projects. ## Core Features & Use Cases - Task-to-Skill Mapping: Matches task types (DocTypes, APIs, Desk UI, reports, testing, and more) to the correct specialized Frappe skill via a lookup table and decision tree. - Triage-First Workflow: Recommends running project triage before code changes to detect project type, Frappe version, installed apps, and tooling. - Skill Composition Guidance: Shows how to combine multiple skills for complex work, such as pairing doctype-development with api-development and desk-customization for a feature with UI. - Use Case: You are asked to add a public web form with a backend API to an existing Frappe site. The router directs you to web-forms plus api-development, after confirming the Frappe version through project-triage. ## Quick Start Ask the assistant to route your Frappe task, for example: "I need to build a Script Report on my Frappe v15 site, which skill should I use?"

Frequently Asked Questions about router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right skill for a Frappe development task?▼

Match your task type to the routing table: DocTypes go to doctype-development, APIs to api-development, Desk UI to desk-customization, and reports to reports. For complex work, combine multiple skills as the router suggests.

What should I do before making code changes to a Frappe project?▼

Run project-triage first to detect the project type, Frappe version, installed apps, and available tooling. This prevents applying patterns that are incompatible with your Frappe version or assuming ERPNext is installed.

Does Frappe skill routing depend on the framework version?▼

Yes, API availability varies significantly between Frappe v13, v14, v15, and v16. Always check the project version during triage before recommending features, since deprecated or missing APIs cause failures.

Can I combine multiple Frappe skills for one feature?▼

Yes, complex tasks often require several skills. A feature with UI typically combines doctype-development, desk-customization, and api-development, while a new app adds app-development and testing.

Why does Frappe code fail with module not found errors?▼

This usually happens when ERPNext-specific code is used in a Frappe-only project. Check installed apps during triage and avoid assuming ERPNext is present before importing its modules.