RuoYi-Vue3-FastAPI Engineering Development Assistant

Problem

RuoYi-Vue3-FastAPI workspaces can mix business domains, CRUD features, and three delivery targets: backend, frontend, and app. When adding a meeting room entity, it is easy to place files in the wrong module, views, or pages directory, or to diverge table names, routes, menus, and permission IDs.

How It Works

• Separates modules from features: a module is a business domain such as meeting; a feature is a CRUD unit such as meetingRoom.
• Maps work to the three ends: module/{module}/, views/{module}/{entity}/, and pages/{module}/{entity}/, with backend, frontend, and app template references.
• Supports two flows: create a complete module, or add one feature to an existing module, covering routes, menus, dependencies, and permission IDs like {module}:{entity}:{action}.
• Applies naming constraints such as sys_{entity} table names, numeric menu IDs, and lowercase English module names to reduce drift.

Boundaries

The source paths are local Windows paths, so the actual repository layout should be checked first. It is suited to RuoYi-Vue3-FastAPI modular CRUD engineering; it does not replace business modeling, database review, or app platform rules.