create-caspian-app 0.2.0-beta.36 → 0.2.0-beta.37
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.
|
@@ -6,6 +6,7 @@
|
|
|
6
6
|
## Global Rules
|
|
7
7
|
|
|
8
8
|
- Use this source-of-truth order: app runtime and app-owned code first, installed `casp` runtime second, packaged markdown docs third.
|
|
9
|
+
- As the app grows, prefer `src/components/` for reusable application UI and reserve `src/lib/` for reusable non-UI code such as services, validators, adapters, and shared helpers.
|
|
9
10
|
- Read `./caspian.config.json` almost immediately before making feature, tooling, scaffolding, or file-placement decisions. Treat it as the workspace feature gate for flags such as `backendOnly`, `tailwindcss`, `mcp`, `prisma`, `typescript`, and `componentScanDirs`.
|
|
10
11
|
- Treat `caspian.config.json` as the single source of truth for whether optional Caspian features are enabled in the current workspace. Use feature-specific docs, files, and commands only after the matching flag is confirmed as enabled.
|
|
11
12
|
- If a feature is disabled and the user wants it, ask whether they want to enable it first, then update `caspian.config.json` and follow `npx casp update project` so framework-managed files align with the new feature set.
|
|
@@ -46,11 +47,18 @@
|
|
|
46
47
|
|
|
47
48
|
### `src/lib/**/*.py`
|
|
48
49
|
|
|
49
|
-
- Keep `src/lib/` for app-owned shared code, service wrappers, and reusable helpers.
|
|
50
|
+
- Keep `src/lib/` for app-owned shared non-UI code, service wrappers, validators, adapters, and reusable helpers.
|
|
51
|
+
- Prefer `src/components/` for reusable rendered UI instead of placing component modules in `src/lib/`.
|
|
50
52
|
- Reuse the generated `src/lib/prisma/` package for Python database access, but do not hand-edit files under `src/lib/prisma/`; regenerate them with `npx ppy generate` after schema changes.
|
|
51
53
|
- When `caspian.config.json` has `mcp: true`, keep app-owned MCP tools in `src/lib/mcp/mcp_server.py` and keep the default FastMCP config in `src/lib/mcp/fastmcp.json`. If those locations change, update `settings/restart-mcp.ts` and the MCP docs together.
|
|
52
54
|
- Keep auth policy in `src/lib/auth/auth_config.py`. Keep auth bootstrap and middleware order changes in `main.py`.
|
|
53
55
|
|
|
56
|
+
### `src/components/**/*.py`
|
|
57
|
+
|
|
58
|
+
- Keep `src/components/` as the default home for reusable application UI components.
|
|
59
|
+
- Move shared cards, forms, shells, navigation, and other reusable rendered building blocks here once they are used across routes or features.
|
|
60
|
+
- Keep route-owned markup in `src/app/**`, and keep non-UI helpers or services in `src/lib/**`.
|
|
61
|
+
|
|
54
62
|
### `public/js/main.js`
|
|
55
63
|
|
|
56
64
|
- Treat `public/js/main.js` as the thin browser bootstrap entry point.
|
package/dist/AGENTS.md
CHANGED
|
@@ -54,6 +54,7 @@ Treat `caspian.config.json` as the single source of truth for whether an optiona
|
|
|
54
54
|
- The schema-change workflow in this workspace is: `npx prisma migrate dev`; if seed flow or `prisma/seed.ts` is involved, run `npx prisma generate` and then `npx prisma db seed`; then run `npx ppy generate`.
|
|
55
55
|
- `npx ppy generate` owns `src/lib/prisma/__init__.py`, `src/lib/prisma/db.py`, `src/lib/prisma/models.py`, and `settings/prisma-schema.json`; do not hand-edit those generated files.
|
|
56
56
|
- `caspian.config.json` is the first config file to check for enabled workspace features. In the current workspace it sets `backendOnly: false`, `tailwindcss: true`, `mcp: false`, `prisma: true`, `typescript: false`, and `componentScanDirs: ["src"]`.
|
|
57
|
+
- As the app grows, prefer `src/components/` for reusable rendered UI and `src/lib/` for reusable non-UI support code.
|
|
57
58
|
- PulsePoint runtime code is shipped in `public/js/pp-reactive-v2.js` and loaded from `public/js/main.js`.
|
|
58
59
|
- `pp-component` is injected by the Python render pipeline onto page, layout, and component roots; authored route and component templates should not add it manually.
|
|
59
60
|
- `main.py` runs `transform_scripts(...)`, so authored body `<script>` tags are rewritten to `<script type="text/pp">` in rendered HTML; route, layout, and component templates should write plain `<script>` in source.
|
|
@@ -88,7 +89,9 @@ Use this map before making changes.
|
|
|
88
89
|
## Editing Rules
|
|
89
90
|
|
|
90
91
|
- Keep app-owned shared code in `src/lib/**`.
|
|
92
|
+
- Keep reusable application UI components in `src/components/**`.
|
|
91
93
|
- Keep route-specific logic in `src/app/**`.
|
|
94
|
+
- When deciding between `src/components/**` and `src/lib/**`, put reusable rendered UI in `src/components/**` and put services, validators, adapters, database helpers, and other non-UI support code in `src/lib/**`.
|
|
92
95
|
- Read `caspian.config.json` before deciding whether a Caspian feature should be used, documented, scaffolded, or avoided in the current workspace.
|
|
93
96
|
- Treat `caspian.config.json` as the single source of truth for optional features. Do not use feature-specific files, commands, or docs until the corresponding flag is enabled.
|
|
94
97
|
- If a feature flag is false and the user wants that feature, ask for confirmation first, then update `caspian.config.json` and run `npx casp update project` so framework-managed files align with the new feature set.
|