create-prisma-php-app 5.0.0-alpha.29 → 5.0.0-alpha.30
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -9,6 +9,14 @@
|
|
|
9
9
|
- Do not assume installed consumer apps also ship a root `.github/copilot-instructions.md` unless the generator explicitly creates one.
|
|
10
10
|
- Keep every `dist/docs/*.md` page AI-discoverable on its own: the frontmatter description and opening section should clearly say when agents should read that file and which adjacent docs to consult next.
|
|
11
11
|
|
|
12
|
+
## Project Structure Recommendations
|
|
13
|
+
|
|
14
|
+
- Keep `src/app` focused on route files, layouts, handlers, and route-scoped partials.
|
|
15
|
+
- Prefer `src/Components` for reusable application UI components shared across pages or layouts.
|
|
16
|
+
- Keep reusable non-UI code such as services, auth, middleware, Prisma classes, and helpers in `src/Lib`.
|
|
17
|
+
- If a partial starts as route-local but becomes shared across the app, move it from `src/app` to `src/Components`.
|
|
18
|
+
- Suggest this structure by default when helping users organize growing Prisma PHP apps.
|
|
19
|
+
|
|
12
20
|
## Framework-Managed Package Scripts
|
|
13
21
|
|
|
14
22
|
- Prisma PHP can generate `package.json` scripts for BrowserSync, Tailwind, TypeScript, WebSocket, MCP, Swagger docs, and related helpers.
|
package/dist/AGENTS.md
CHANGED
|
@@ -176,6 +176,16 @@ Treat `files-list.json` as a framework-generated file for route discovery and in
|
|
|
176
176
|
|
|
177
177
|
If a route task appears to require editing `files-list.json`, that is almost certainly the wrong approach.
|
|
178
178
|
|
|
179
|
+
## Reusable project organization
|
|
180
|
+
|
|
181
|
+
When organizing a growing Prisma PHP app, keep route code and reusable code separated.
|
|
182
|
+
|
|
183
|
+
- keep `src/app` focused on the route tree, route-local layouts, pages, handlers, and route-scoped partials
|
|
184
|
+
- prefer `src/Components` for reusable application UI components shared across multiple routes or layouts
|
|
185
|
+
- keep reusable non-UI code such as services, auth, middleware, Prisma classes, and helper libraries in `src/Lib`
|
|
186
|
+
- if a partial starts in `src/app` but becomes shared across the app, promote it into `src/Components`
|
|
187
|
+
- do **not** default to placing app-wide reusable components under `src/app` unless the user explicitly wants route-local colocation
|
|
188
|
+
|
|
179
189
|
## Framework-managed package scripts
|
|
180
190
|
|
|
181
191
|
Prisma PHP can generate `package.json` scripts for BrowserSync, Tailwind, TypeScript, WebSocket, MCP, Swagger docs, and related project helpers.
|