agentleFS
lubusINlubusIN/frappe-skills/router/SKILL.md

router

Skill68 starsChanged 9 days agoMITView on GitHub

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.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research and setup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before deep work, run project-triage to understand:

    line 37
  2. Very specific:

    Document workflow = doctype-development + printing-templates + reports

    line 49
  3. Distinctive:

    Always run triage first: before making code changes to unknown projects

    line 97
  4. Distinctive:

    Check Frappe version: before recommending features (API availability varies significantly between v13, v14, v15, v16)

    line 98

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

TaskSkill
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

MistakeWhy It FailsFix
Skipping project triageApplying wrong patterns for versionAlways run triage first
Using ERPNext-specific code in Frappe-only projectsModule not found errorsCheck installed apps first
Wrong skill for taskIncomplete implementationMatch task type to skill carefully
Ignoring version differencesDeprecated/missing APIsCheck version compatibility in skill references
Working on wrong siteChanges don't appearAlways specify --site flag
Using vanilla JS/jQuery for frontendsEcosystem mismatchUse Frappe UI (Vue 3) via frontend-development
Custom app shell for CRUD appsInconsistent UXFollow CRM/Helpdesk patterns via enterprise-patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.