@marvalt/digivalt-core 0.2.30 → 0.2.33

package/docs/LOVABLE-MASTER-PROMPT.md

@@ -1,140 +0,0 @@
-# AI master prompt — DigiVAlt full local WordPress control
-
-Use this as a single copy-paste master prompt in Cursor, Claude Code, Antigravity, Lovable, or similar AI coding tools.
-
-The objective is a DigiValt app scaffold that is production-shaped from day one, where after generation a human only needs to set `.env` / `.env.local` values before first local run:
-
-```bash
-npm run build && npm run dev
-```
-
-## Scope
-
-- **AI responsibilities:** scaffold code, install/wire dependencies, run `digivalt-init`, ensure scripts/files are correct, keep cloud/function wiring and SEO enabled, and build a WordPress-driven shell.
-- **Human responsibilities:** set real env values on local PC and cloud dashboard, run first local build/dev, replace placeholder static data with real generated exports as needed.
-
-## Canonical sources
-
-- [README.md](../README.md)
-- [template/DIGIVALT_SETUP.md](../template/DIGIVALT_SETUP.md)
-- [template/scripts/generate.ts](../template/scripts/generate.ts)
-- [docs/SEO-PERFORMANCE.md](./SEO-PERFORMANCE.md)
-- [digivalt-landing/DIGIVALT_SETUP.md](../../../digivalt-landing/DIGIVALT_SETUP.md)
-
----
-
-## Master prompt text (paste below into your AI tool)
-
-You are a senior full-stack engineer scaffolding a DigiValt consumer app (Vite + React + TypeScript) with full WordPress-controlled static content behavior. This workflow must work the same whether run from Cursor, Claude Code, Antigravity, Lovable, or another AI assistant.
-
-### Non-negotiables
-
-- Install `@marvalt/digivalt-core@latest`.
-- Use `npx digivalt-init` to enforce DigiValt-managed scaffold files and scripts.
-- Keep Cloudflare Pages Functions + `wrangler.toml` enabled.
-- Keep SEO enabled by default (Helmet provider + DigiValt SEO helpers).
-- Keep local secrets out of git and ignore `.env`, `.env.local`, `.env.*.local`, `.dev.vars`.
-- Do not hand-maintain `public/sitemap-paths.json`; it is generated.
-- Do not create `public/sitemap.xml` when using `functions/sitemap.xml.ts`.
-
-### File/path requirements
-
-Use these exact static data paths:
-
-- `public/wordpress-data.json`
-- `public/gravity-forms-data.json`
-- `src/data/mautic-data.json`
-
-If real exports are unavailable, use template starter fixtures (or equivalent minimal placeholders) so the app boots. Mark placeholders clearly.
-
-### Build wiring requirements
-
-Ensure these commands exist and are used:
-
-```bash
-npm install @marvalt/digivalt-core@latest
-npm install -D vite-node
-npx digivalt-init
-npm install react-helmet-async
-```
-
-Expected scripts:
-
-- `generate`: `npx vite-node --options.deps.inline="@marvalt/digivalt-core/generators" scripts/generate.ts`
-- `build`: `npx vite-node --options.deps.inline="@marvalt/digivalt-core/generators" scripts/generate.ts && vite build`
-- `build:dev`: `npx vite-node --options.deps.inline="@marvalt/digivalt-core/generators" scripts/generate.ts && vite build --mode development`
-- `dev`: `vite`
-
-### `scripts/generate.ts` behavior
-
-Import from `@marvalt/digivalt-core/generators` only:
-
-- In hosted fixture mode (`VITE_IS_LOVABLE=true`): skip fetch, run `generateSitemapPathsSafe()`.
-- In normal local mode (default): run `generateAllData()` then sitemap; on fetch failure still run sitemap safe fallback.
-
-### WordPress-driven runtime wiring (must implement)
-
-After `loadWordPressData()` from `@marvalt/digivalt-core/static`, wire the app shell and routes using WordPress static data:
-
-1. Menus from `getNavigationMenu()` / `getFooterNavigationMenu()` / `getMenuById()` (+ `getParsedHeader()` / `getHeaderMenuId()` / `getFooterMenuId()`). Assign classic menus in WP under **Appearance → Menus → Manage Locations** (`{frontendId}-header|footer`, then `default-*`).
-2. Optional header/footer template blocks from `getHeader()` / `getFooter()` (legacy). Prefer app-owned chrome + location menus for multi-frontend.
-3. Site identity from `getSiteSettings()` / `getLogoUrl()` / `getSiteIconUrl()`.
-4. Theme styles from `getWordPressData().theme_styles` mapped into app styling/tokens.
-5. Pages/posts/CPT routes from `getWordPressPages()`, `getWordPressPageBySlug()`, `getWordPressPosts()`, and `front_page`.
-
-For forms, support Gravity Forms and Mautic via `@marvalt/digivalt-core/services` and/or JSON static stores.
-
-### Cloudflare and sitemap requirements
-
-- Keep `functions/sitemap.xml.ts`.
-- Keep `functions/api/*` handlers from template and keep `wrangler.toml`.
-- Ensure sitemap flow is active:
-  - input: `public/sitemap-static-paths.json`
-  - generated output: `public/sitemap-paths.json`
-  - runtime endpoint: `/sitemap.xml` from Pages Function
-
-### AI output constraints
-
-- Do not request humans to hand-edit code before first run.
-- After scaffolding, the only required manual step before first run is env values in `.env` / `.env.local`.
-- Provide a final validation checklist and commands:
-  - `npm run build`
-  - `npm run dev`
-
----
-
-## Built-in defaults (use unless humans override later)
-
-- Package: `@marvalt/digivalt-core@latest`
-- Static data: template starter fixtures for WordPress, Gravity Forms, Mautic
-- SEO: ON
-- Cloudflare Functions + `wrangler.toml`: ON
-- Form/page mapping: derive from WordPress content and shortcodes first (`gf_embed`, `mautic_form`, `phplist_subscribe`; see `GLOBAL-SHORTCODES.md`)
-
----
-
-## Pre-flight checklist
-
-| Step | Done |
-|------|------|
-| `@marvalt/digivalt-core@latest` installed | ☐ |
-| `digivalt-init` run and scripts verified | ☐ |
-| Required static data files exist (`wordpress`, `gravity-forms`, `mautic`) | ☐ |
-| `sitemap-static-paths.json` exists and `sitemap-paths.json` is generated | ☐ |
-| Cloudflare functions/wrangler files present | ☐ |
-| SEO imports + `HelmetProvider` wired | ☐ |
-| `.gitignore` excludes local secret files | ☐ |
-
----
-
-## Reference paths in this monorepo
-
-| Concern | File |
-|---------|------|
-| Local setup baseline | [digivalt-landing/DIGIVALT_SETUP.md](../../../digivalt-landing/DIGIVALT_SETUP.md) |
-| Template setup baseline | [template/DIGIVALT_SETUP.md](../template/DIGIVALT_SETUP.md) |
-| Init behavior and script expectations | [README.md](../README.md) |
-| Generator script template | [template/scripts/generate.ts](../template/scripts/generate.ts) |
-| Landing generator implementation | [digivalt-landing/scripts/generate.ts](../../../digivalt-landing/scripts/generate.ts) |
-| SEO and sitemap behavior | [docs/SEO-PERFORMANCE.md](./SEO-PERFORMANCE.md) |
-| WP static getters and shell helpers | [src/static/wpStatic.ts](../src/static/wpStatic.ts) |