erp-structural-implementation

Name: erp-structural-implementation
Availability: InStock
Author: pphat

Scaffold ERP modules end-to-end in Laravel and Nuxt projects.

Updated May 15, 2026

Search Tags:#architecture #frontend #multi-tenant #backend #scaffolding #erp

Ready to run

npx skills add https://github.com/pphatdev/erp-prompt --skill erp-structural-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: erp-structural-implementation
Source: https://github.com/pphatdev/erp-prompt/tree/main/rules/structure
Command: npx skills add https://github.com/pphatdev/erp-prompt --skill erp-structural-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a new ERP module end-to-end, ensuring backend and frontend adhere to the project's conventions and tenancy model.

Core Features & Use Cases

Canonical recipe for adding domain modules with consistent structure, namespaces, and permissions.
End-to-end scaffolding covering migrations, models, services, controllers, policies, resources, routes, frontend pages, and sidebar entries.
Quick-start example: used to onboard new domain areas quickly without drift.

Quick Start

Follow this canonical recipe to scaffold a new ERP module end-to-end in both backend and frontend, matching existing project conventions.

Frequently Asked Questions about erp-structural-implementation

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

FAQPage Schema

How do I scaffold an ERP module end-to-end in a multi-tenant Laravel and Nuxt project?▼

Scaffolding an ERP module end-to-end automates backend models, controllers, services, policies, routes, and frontend pages. It enforces multi-tenant conventions, UUID primary keys, soft deletes, per-tenant routing, and consistent frontend composables to ensure structural integrity.

What conventions do I need to follow when adding a new domain module to a multi-tenant Laravel backend?▼

Adding a domain module requires adherence to tenancy patterns, UUID primary keys, and soft deletes. The scaffolding process coordinates backend migrations, models, controllers, policies, permissions, and resources to maintain a consistent multi-tenant architecture across the project.

Does multi-tenant module scaffolding include frontend pages and sidebar entries?▼

Yes, multi-tenant module scaffolding includes frontend page generation. It creates corresponding Nuxt pages, composables, layout entries, and sidebar entries alongside backend components to ensure the user interface matches the backend domain structure.

Why do I need a canonical recipe for onboarding new ERP domain areas?▼

A canonical recipe for onboarding new ERP domain areas prevents structural drift. It provides a consistent approach to scaffolding migrations, models, services, controllers, and frontend pages, ensuring new modules match existing project namespaces, permissions, and tenancy models.

Can I use this scaffolding recipe for a single-tenant Laravel application?▼

This scaffolding recipe is designed specifically for a multi-tenant Laravel and Nuxt project. It strictly enforces per-tenant routing, tenancy patterns, and UUID primary keys, making it unsuitable for single-tenant applications without significant structural modifications.