@lynxflow/seo-engine 1.5.3 → 1.5.4

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.
Files changed (4) hide show
  1. package/dist/index.js +10 -7
  2. package/dist/index.mjs +10 -7
  3. package/package.json +1 -1
  4. package/src/llm-prompt.ts +10 -7
package/dist/index.js CHANGED
@@ -3642,17 +3642,20 @@ Your role is to configure, resolve, and maintain programmatic SEO pages, XML sit
3642
3642
 
3643
3643
  ---
3644
3644
 
3645
- ### \uD83D\uDEA8 1. CRITICAL RULE: FEATURE DISCOVERY FROM FRONTEND ONLY (NEVER USE BACKEND / PROVIDERS)
3645
+ ### \uD83D\uDEA8 1. CRITICAL RULE: SEMANTIC PRODUCT DISCOVERY FROM THE FRONTEND
3646
3646
 
3647
- When discovering or listing product modules, features, or services to build the SEO matrices:
3647
+ When discovering product modules, features, or services to build the SEO matrices:
3648
3648
  - **❌ NEVER inspect backend API routes, internal database folders, or third-party providers:**
3649
3649
  - DO NOT create programmatic pages for internal plumbing like: \`/api/stripe\`, \`/api/resend\`, \`/api/auth\`, \`/api/d1\`, \`/api/webhooks\`, \`/api/openai\`.
3650
3650
  - DO NOT expose internal infrastructure, vendors, or suppliers (e.g. Stripe, Resend, Cloudflare D1, Better-Auth, Supabase, PostgreSQL drivers) as public product features. End users never search for or buy your internal backend plumbing.
3651
- - **✅ ALWAYS inspect the FRONTEND user-facing interface & commercial value propositions:**
3652
- - **Step 1A - Marketing Navbars & Dropdowns:** Scan \`components/Navbar.tsx\`, \`components/Header.tsx\`, \`components/Navigation.tsx\` to list all primary product modules.
3653
- - **Step 1B - Marketing Feature Pages & Pricing:** Scan \`app/(marketing)/*\`, \`pages/features/*\`, \`app/pricing/*\` to list commercial feature names and pricing tiers.
3654
- - **Step 1C - Dashboard Navigation & User Tools:** Scan \`components/dashboard/*\`, \`components/sidebar/*\` to find actual user workflows.
3655
- - **Step 1D - Extraction Requirement:** For EACH discovered module (or major product branch), create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
3651
+ - **✅ DEEPLY READ & UNDERSTAND THE FRONTEND PRODUCT (SEMANTIC ANALYSIS):**
3652
+ - **Framework-Agnostic Exploration:** Do not look for specific filenames (e.g. \`Navbar.tsx\` or \`Header.tsx\`). Every codebase organizes UI differently (React, Vue, Svelte, Astro, Remix, Next.js, HTML).
3653
+ - **Read the Public Product Pages & User UI:** Read the website's landing pages, public feature descriptions, menus/navigation (whatever they are named), pricing tables, and user dashboard views.
3654
+ - **Understand the Core Value & Workflows:** For every distinct tool or capability of the application:
3655
+ - *What does this module actually do?* (e.g. "Automates quote follow-ups", "Visual drag-and-drop pipeline", "Real-time client portal").
3656
+ - *What pain point does it solve for the end user?*
3657
+ - *Who is the primary persona/industry benefiting from it?*
3658
+ - **Extraction Requirement:** For EACH detected product module or major feature branch, create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
3656
3659
 
3657
3660
  ---
3658
3661
 
package/dist/index.mjs CHANGED
@@ -3544,17 +3544,20 @@ Your role is to configure, resolve, and maintain programmatic SEO pages, XML sit
3544
3544
 
3545
3545
  ---
3546
3546
 
3547
- ### \uD83D\uDEA8 1. CRITICAL RULE: FEATURE DISCOVERY FROM FRONTEND ONLY (NEVER USE BACKEND / PROVIDERS)
3547
+ ### \uD83D\uDEA8 1. CRITICAL RULE: SEMANTIC PRODUCT DISCOVERY FROM THE FRONTEND
3548
3548
 
3549
- When discovering or listing product modules, features, or services to build the SEO matrices:
3549
+ When discovering product modules, features, or services to build the SEO matrices:
3550
3550
  - **❌ NEVER inspect backend API routes, internal database folders, or third-party providers:**
3551
3551
  - DO NOT create programmatic pages for internal plumbing like: \`/api/stripe\`, \`/api/resend\`, \`/api/auth\`, \`/api/d1\`, \`/api/webhooks\`, \`/api/openai\`.
3552
3552
  - DO NOT expose internal infrastructure, vendors, or suppliers (e.g. Stripe, Resend, Cloudflare D1, Better-Auth, Supabase, PostgreSQL drivers) as public product features. End users never search for or buy your internal backend plumbing.
3553
- - **✅ ALWAYS inspect the FRONTEND user-facing interface & commercial value propositions:**
3554
- - **Step 1A - Marketing Navbars & Dropdowns:** Scan \`components/Navbar.tsx\`, \`components/Header.tsx\`, \`components/Navigation.tsx\` to list all primary product modules.
3555
- - **Step 1B - Marketing Feature Pages & Pricing:** Scan \`app/(marketing)/*\`, \`pages/features/*\`, \`app/pricing/*\` to list commercial feature names and pricing tiers.
3556
- - **Step 1C - Dashboard Navigation & User Tools:** Scan \`components/dashboard/*\`, \`components/sidebar/*\` to find actual user workflows.
3557
- - **Step 1D - Extraction Requirement:** For EACH discovered module (or major product branch), create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
3553
+ - **✅ DEEPLY READ & UNDERSTAND THE FRONTEND PRODUCT (SEMANTIC ANALYSIS):**
3554
+ - **Framework-Agnostic Exploration:** Do not look for specific filenames (e.g. \`Navbar.tsx\` or \`Header.tsx\`). Every codebase organizes UI differently (React, Vue, Svelte, Astro, Remix, Next.js, HTML).
3555
+ - **Read the Public Product Pages & User UI:** Read the website's landing pages, public feature descriptions, menus/navigation (whatever they are named), pricing tables, and user dashboard views.
3556
+ - **Understand the Core Value & Workflows:** For every distinct tool or capability of the application:
3557
+ - *What does this module actually do?* (e.g. "Automates quote follow-ups", "Visual drag-and-drop pipeline", "Real-time client portal").
3558
+ - *What pain point does it solve for the end user?*
3559
+ - *Who is the primary persona/industry benefiting from it?*
3560
+ - **Extraction Requirement:** For EACH detected product module or major feature branch, create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
3558
3561
 
3559
3562
  ---
3560
3563
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lynxflow/seo-engine",
3
- "version": "1.5.3",
3
+ "version": "1.5.4",
4
4
  "description": "High-Performance Multilingual Programmatic SEO & AI Search Engine SDK",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
package/src/llm-prompt.ts CHANGED
@@ -10,17 +10,20 @@ Your role is to configure, resolve, and maintain programmatic SEO pages, XML sit
10
10
 
11
11
  ---
12
12
 
13
- ### 🚨 1. CRITICAL RULE: FEATURE DISCOVERY FROM FRONTEND ONLY (NEVER USE BACKEND / PROVIDERS)
13
+ ### 🚨 1. CRITICAL RULE: SEMANTIC PRODUCT DISCOVERY FROM THE FRONTEND
14
14
 
15
- When discovering or listing product modules, features, or services to build the SEO matrices:
15
+ When discovering product modules, features, or services to build the SEO matrices:
16
16
  - **❌ NEVER inspect backend API routes, internal database folders, or third-party providers:**
17
17
  - DO NOT create programmatic pages for internal plumbing like: \`/api/stripe\`, \`/api/resend\`, \`/api/auth\`, \`/api/d1\`, \`/api/webhooks\`, \`/api/openai\`.
18
18
  - DO NOT expose internal infrastructure, vendors, or suppliers (e.g. Stripe, Resend, Cloudflare D1, Better-Auth, Supabase, PostgreSQL drivers) as public product features. End users never search for or buy your internal backend plumbing.
19
- - **✅ ALWAYS inspect the FRONTEND user-facing interface & commercial value propositions:**
20
- - **Step 1A - Marketing Navbars & Dropdowns:** Scan \`components/Navbar.tsx\`, \`components/Header.tsx\`, \`components/Navigation.tsx\` to list all primary product modules.
21
- - **Step 1B - Marketing Feature Pages & Pricing:** Scan \`app/(marketing)/*\`, \`pages/features/*\`, \`app/pricing/*\` to list commercial feature names and pricing tiers.
22
- - **Step 1C - Dashboard Navigation & User Tools:** Scan \`components/dashboard/*\`, \`components/sidebar/*\` to find actual user workflows.
23
- - **Step 1D - Extraction Requirement:** For EACH discovered module (or major product branch), create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
19
+ - **✅ DEEPLY READ & UNDERSTAND THE FRONTEND PRODUCT (SEMANTIC ANALYSIS):**
20
+ - **Framework-Agnostic Exploration:** Do not look for specific filenames (e.g. \`Navbar.tsx\` or \`Header.tsx\`). Every codebase organizes UI differently (React, Vue, Svelte, Astro, Remix, Next.js, HTML).
21
+ - **Read the Public Product Pages & User UI:** Read the website's landing pages, public feature descriptions, menus/navigation (whatever they are named), pricing tables, and user dashboard views.
22
+ - **Understand the Core Value & Workflows:** For every distinct tool or capability of the application:
23
+ - *What does this module actually do?* (e.g. "Automates quote follow-ups", "Visual drag-and-drop pipeline", "Real-time client portal").
24
+ - *What pain point does it solve for the end user?*
25
+ - *Who is the primary persona/industry benefiting from it?*
26
+ - **Extraction Requirement:** For EACH detected product module or major feature branch, create at least 1 programmatic service entry with \`slug\`, \`name\`, \`category\`, \`description\`, \`keyFeatures\`, and \`priceMonthly\`.
24
27
 
25
28
  ---
26
29