syntaxmatrix 2.6.4.4__py3-none-any.whl → 3.0.1__py3-none-any.whl

syntaxmatrix/settings/prompts.py

@@ -1,425 +1,1158 @@
+SMXAI_CHAT_IDENTITY = ""
+
+SMXAI_CHAT_INSTRUCTIONS = ""
+
+SMXAI_WEBSITE_DESCRIPTION = ""
+
+
+SMXAI_LANDING_PAGE_INSTRUCTIONS = f"""
+> IMPORTANT CONTEXT FOR THE GENERATOR
+
+## PLAN GENERATION CONTRACT (MANDATORY)
+
+When generating the page plan JSON:
+
+- EVERY major section MUST include:
+  - needsImage: true
+  - imgQuery: "<specific, concrete image search query>"
+- Images MUST be attached at section level.
+- Do NOT rely on templates to infer images.
+- If a section lacks needsImage + imgQuery, the plan is INVALID.
+
+This applies to:
+- hero
+- problem framing
+- solution overview
+- platform highlights
+- deployment models
+- trust / governance
+- licensing model
+- plans overview
+- proof / credibility
+- final CTA
+
+---
+
+## GLOBAL CONTENT RULES (NON-NEGOTIABLE)
+
+- Each MAJOR section must include 2–3 full paragraphs minimum.
+- Each paragraph must be 4–6 complete sentences.
+- Prose explanations MUST come before cards or bullets.
+- Cards and bullets may ONLY summarise AFTER prose.
+- Avoid slogans without explanation.
+- Assume the reader is technical and sceptical.
+
+Thin or overly short content is invalid.
+
+---
+
+## GLOBAL IMAGE RULES (NON-NEGOTIABLE)
+
+- Each major section must include exactly ONE image.
+- Prefer: architecture diagrams, platform UI visuals, system diagrams, abstract technical visuals.
+- Avoid: lifestyle photos, generic startup imagery, people (unless explicitly requested).
+- Do not reuse the same imgQuery across sections.
+
+---
+
+## A) LAYOUT & HERO VISUAL RULES
+
+### Hero Alignment Options (EXPLICIT)
+Support both and select one:
+
+- Default: heroAlignment = "left"
+- Alternative: heroAlignment = "center"
+
+The chosen alignment MUST be emitted in the plan.
+
+### Hero Overlay Rules (MANDATORY)
+- Hero text overlay MUST be glassy/translucent.
+- The hero MUST NOT use an opaque white banner/card that blocks the image.
+- Overlay opacity must allow the hero image to remain clearly visible.
+
+---
+
+## B) REQUIRED HOMEPAGE STRUCTURE (IN ORDER)
+
+### B.1 HERO — Company + Product Positioning
+
+Content requirements:
+- 2–3 paragraphs explaining:
+  - what SyntaxMatrix is (AI infrastructure + algorithm design company)
+  - what smxPP is (deployable platform provisioner)
+  - why client-owned deployment matters (data sovereignty, governance, control)
+- Avoid hype. Use concrete, operational language.
+
+Hero Headline (choose one strong, enterprise option):
+- "Provision Client-Owned AI Platforms — Securely, Governably, Repeatably"
+OR
+- "Enterprise AI Platforms You Can Own, Deploy, and Govern"
+
+Subheadline:
+- Must mention smxPP explicitly and clarify it provisions a complete platform, not a single chatbot.
+
+CTAs:
+- Primary: "Explore Services"
+- Secondary: "Read Documentation"
+Optional tertiary link: "Licensing Explained"
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise AI platform hero architecture abstract dark glassmorphism"
+
+---
+
+### B.2 THE PROBLEM — Why AI Prototypes Fail in Production
+
+Content requirements:
+- 2–3 paragraphs explaining the real pain points:
+  - teams rebuilding AI infrastructure repeatedly
+  - fragile RAG pipelines and unreproducible behaviour
+  - lack of governance, audit trails, and role separation
+  - mismatch between content systems and AI systems
+  - vendor lock-in and unclear data boundaries
+- Follow with a short bullet list summarising 5–7 issues.
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise AI production challenges diagram fragmentation governance"
+
+---
+
+### B.3 THE SOLUTION — What smxPP Provisions
+
+Content requirements:
+- 2–3 paragraphs explaining:
+  - smxPP provisions a complete platform surface (not a toy UI)
+  - how modules fit together (admin panel, ingestion, assistant, pages, ML tooling, analytics)
+  - how this reduces time-to-deploy and increases operational stability
+
+Include a short summary list after prose:
+- Role-aware Admin Panel
+- Knowledge ingestion + RAG assistant
+- Page Studio and documentation surfaces
+- ML Lab outputs and exports (where enabled)
+- Licensing boundaries and entitlements (premium)
+
+Visual:
+- needsImage: true
+- imgQuery: "AI platform overview diagram admin panel RAG page studio ML lab"
+
+---
+
+### B.4 PLATFORM HIGHLIGHTS — What Enterprises Actually Get
+
+Content requirements:
+- 2 paragraphs introducing the philosophy: operational value > demos.
+- Then provide 6 highlight blocks (each with a 4–6 sentence paragraph, not one-liners):
+  1) Role-aware access and governance
+  2) Document ingestion and retrieval architecture
+  3) RAG assistant with controlled grounding
+  4) Page Studio for internal/external portals
+  5) Documentation viewer integrated into the platform
+  6) Optional ML Lab workflows and exports
+
+Cards may summarise each after the prose paragraphs.
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise software dashboard UI panels RAG admin governance"
+
+---
+
+### B.5 DEPLOYMENT MODELS — Client-Owned by Design
+
+Content requirements:
+- 2–3 paragraphs explaining:
+  - self-hosted deployment model (client instance)
+  - why SyntaxMatrix does not host client instances by default
+  - how BYOK and data locality reduce procurement friction
+- Include a comparison block after prose:
+  - On-premise
+  - Private cloud
+  - Controlled cloud deployments (e.g., container-based)
+
+Visual:
+- needsImage: true
+- imgQuery: "deployment models on premise private cloud architecture diagram"
+
+---
+
+### B.6 TRUST & GOVERNANCE — Built for Sceptical Environments
+
+Content requirements:
+- 2–3 paragraphs addressing:
+  - auditability, role separation, operational controls
+  - how content ingestion is managed and traceable
+  - how organisations can govern AI behaviour over time
+- Include a short list of enterprise trust signals:
+  - controlled permissions
+  - clear data boundary
+  - reproducible upgrades
+  - documented operations
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise compliance security audit governance diagram"
+
+---
+
+### B.7 LICENSING MODEL — Sustainable, Enforceable, Enterprise-Friendly
+
+Content requirements:
+- 2–3 paragraphs explaining:
+  - open-core commercial model
+  - signed, instance-bound licences
+  - remote validation where enabled for subscription integrity
+  - grace period handling to avoid sudden disruption
+- Explain the self-serve portal benefits:
+  - update payment method
+  - view invoices
+  - cancel at period end
+- Emphasise fraud resistance as investor-grade assurance, without sounding adversarial.
+
+Visual:
+- needsImage: true
+- imgQuery: "software licensing cryptographic signature keys enterprise diagram"
+
+---
+
+### B.8 PLANS OVERVIEW — Capability Progression (No Prices)
+
+Content requirements:
+- 2–3 paragraphs explaining plan philosophy:
+  - Trial is full access for evaluation
+  - Free is constrained but functional
+  - Pro is for small teams adopting smxPP seriously
+  - Business is for scaled operations needing more caps and governance
+  - Enterprise is for institutions with strict requirements and deeper controls
+- Do NOT include pricing. Explain operational value and typical fit.
+- Provide a concise summary table AFTER prose (caps/features high-level only).
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise pricing tiers progression comparison chart abstract"
+
+---
+
+### B.9 PROOF & CREDIBILITY — Why This Is Real
+
+Content requirements:
+- 2–3 paragraphs explaining:
+  - engineering-first platform design
+  - documented deployment approach
+  - measurable operational focus (reliability, governance, reproducibility)
+- Include a short credibility block:
+  - Founder profile line (Bobga Nti — Founder / AI Engineer; MSc AI, platform engineering focus)
+  - Company governance line (Yvonne Motuba — Company Secretary; corporate oversight)
+- Keep it professional and factual.
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise software engineering credibility diagram architecture blueprint"
+
+---
+
+### B.10 FINAL CTA — Next Steps
+
+Content requirements:
+- 1–2 paragraphs reinforcing:
+  - client-owned AI platform value
+  - governance-first stance
+  - how to engage (services + documentation + licensing trust)
+
+CTAs:
+- "Talk to SyntaxMatrix"
+- "Explore Services"
+- "Read Documentation"
+Optional link: "Licensing Explained"
+
+Visual:
+- needsImage: true
+- imgQuery: "enterprise call to action abstract technology background dark"
+
+---
+
+## C) PAGE STUDIO RENDERING RULES
+
+- Prose first, UI blocks second
+- No compressed sections
+- Maintain enterprise rhythm and spacing
+- Ensure hero overlay is glassy and does NOT block the image
+
+Failure to satisfy content depth or image rules is invalid.
 
-SMXAI_CHAT_IDENTITY = f"""
-    Your name is 'smxAI'. 
-    You are the expert AI Engineer and Data Scientist at SyntaxMatrix Ltd. 
-    Your creator is SyntaxMatrix and you will represent them in any way, shape or form. 
-    Your Company is based in Ireland. It designs and develop AI algorithms and softwares for business applications. 
 """
 
-SMXAI_CHAT_INSTRUCTIONS = """
-    Content & Formatting Blueprint (Adhere Strictly):
-    Structure your response using the following elements as appropriate for the topic. Prioritize clarity and information density. If the query is not a question or if there is no context: generate an appropriate general response based on your training knowledge.
-    else if the query is a question:
-    1. Generate a response to the given query based on the given user context and/or system context.
-    2. Use the chat history to stay relevant.
-    3. You must always respond in a conversational tone and do not Hallucinate.
-    4. Determine whether based on the query, you should generate a list, table, or just plain text response.
-    5. If the response is plain text, each sentence must begin on a new line - use the <br> tag.
-    6. If the query is a question that requires a list or table, you must generate the content in the appropriate format.
-    7. Use clear, hierarchical headings if the response is longer than a paragraph.
-    8. Be direct and concise. Avoid unnecessary fluff or repetition.
-    9. Lead with your key conclusion or answer in the first sentence.
-    10. Support your answer with clear, factual points.
-    
-    ────────  FORMAT INSTRUCTIONS ───────────────
-        1. Decide which of the following layouts best fits the content:
-            • Comparison across attributes or (Key:Value) pairs → HTML <table>. 
-            • When creating a table, adhere to the following styling instructions:
-                a. First, declare 3 colors: c1="#EDFBFF", c2="#CCCCCC", c3="#E3E3E3".
-                b. The generated table must be formatted so that table cells have border lines.
-                c. The table head (<thead>) must always have a background color of c1.
-                d. The rest of the rows in the table body (<tbody>) must alternate between 2 background colors, c2 and c3 (striped).
-            • Use bullet points for simple lists of items, features → HTML <ul>
-            • Use ordered (numbered or step-by-step) list for sequences or steps in a process → HTML <ol>
-        2. Keep cells/list items concise (one fact or metric each).  
-        3. All markup must be raw HTML. Avoid using markdown symbols like **asterisks** or _underscores_ for emphasis.
-        4. Do not wrap the answer inside triple back-ticks.
-        6. If emphasis is needed, use clear language (e.g., "It is important to note that...").
-        7. Use horizontal lines (<hr>) sparingly to separate distinct sections.
-        8. The final output should be professional, easy to scan, and ready to be pasted into a document or email.
+
+SMXAI_ABOUT_PAGE_INSTRUCTIONS = f"""
+IMPORTANT CONTEXT FOR THE GENERATOR
+This page must read like the About page of a serious infrastructure and design by the website desc.
+This is NOT marketing copy. This is NOT a teaser. This is a full company profile.
+Failure to follow layout, image, or depth requirements invalidates the output.
+
+🔒 PLAN GENERATION CONTRACT (MANDATORY)
+When generating the internal page plan JSON:
+EVERY major section MUST explicitly include an image block
+For EACH section, the planner MUST emit:
+needsImage: true
+
+imgQuery: "<specific, concrete image search query>"
+Images must be attached at section level
+Do NOT rely on defaults
+If any section lacks needsImage + imgQuery, the plan is INVALID
+
+This applies to:
+hero
+mission / vision
+problem statement
+platform architecture
+capabilities
+principles
+founders
+credibility / roadmap
+final CTA
+
+🎯 PAGE GOAL
+Generate a comprehensive, long-form About page that explains:
+What SyntaxMatrix is
+Why it exists
+What it builds (smxPP)
+How the platform works internally
+How it is deployed and governed
+Who built it and why they are qualified
+Why enterprises should trust it
+Audience:
+
+CTOs
+Heads of Engineering
+AI Architects
+Enterprise Buyers
+Technical Investors
+
+Tone:
+enterprise-grade
+technical
+confident
+explanatory
+sceptic-aware
+never hype-driven
+
+📐 GLOBAL CONTENT RULES (NON-NEGOTIABLE)
+This page MUST be long-form prose
+Each MAJOR section must include:
+3-4 full paragraphs minimum
+Each paragraph 6-7 sentences
+Bullet points and cards are allowed ONLY as summaries
+Prose explanations MUST come first
+No slogans without explanation
+Assume the reader is technically competent and distrustful
+Thin content = failure.
+
+🖼️ GLOBAL IMAGE RULES (NON-NEGOTIABLE)
+Every MAJOR section MUST include an image
+Images support comprehension — they do NOT replace text
+
+Prefer:
+architecture diagrams
+abstract technical visuals
+interfaces
+
+Avoid:
+lifestyle photos
+generic startup imagery
+Do NOT reuse images across sections
+
+🧩 A) LAYOUT & HERO RULES
+Hero Layout Options (EXPLICIT)
+The generator MUST support both layouts:
+Default: heroAlignment = "left"
+Alternative: heroAlignment = "center"
+The chosen alignment MUST be emitted in the plan.
+Hero Overlay Rules (MANDATORY)
+Overlay style MUST be glassy / translucent
+NO opaque white cards
+Overlay opacity should allow the hero image to remain visible
+The hero image must visually dominate
+
+🧱 B) REQUIRED SECTION STRUCTURE (IN ORDER)
+B.1 Hero — Company Identity & Positioning
+Content requirements:
+
+3-4 paragraphs explaining:
+what SyntaxMatrix is as a company
+its focus on AI infrastructure and algorithm design
+the difference between SyntaxMatrix and hosted AI tools
+Clearly introduce smxPP as the core product
+Explain “client-owned AI platforms” in concrete terms
+
+CTAs:
+“View Services”
+“Read Documentation”
+Visual:
+needsImage: true
+imgQuery: "enterprise AI infrastructure architecture abstract dark"
+
+B.2 Mission and Vision
+Mission:
+2 paragraphs explaining what the company delivers today
+
+Focus on engineering outcomes, not aspirations
+
+Vision:
+2 paragraphs explaining the long-term direction:
+governed AI systems
+composable platforms
+ownership, auditability, control
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise technology mission vision abstract diagram"
+
+B.3 Why SyntaxMatrix Exists
+Content requirements:
+3-4 paragraphs describing industry pain points in depth:
+repeated rebuilding of AI stacks
+fragile RAG systems
+lack of governance and audit trails
+separation of AI from content systems
+Follow with a short bullet summary
+
+Visual:
+needsImage: true
+imgQuery: "enterprise AI complexity fragmentation diagram"
+B.4 The smxPP Platform Architecture
+Content requirements:
+
+4-5 paragraphs explaining:
+internal architecture of smxPP
+subsystem interaction
+why this design enables reuse and governance
+Explicitly describe:
+role-aware UI
+document ingestion
+
+RAG pipelines
+
+Page Studio
+
+ML Lab
+
+vector stores
+
+licensing boundaries
+
+Visual:
+
+needsImage: true
+
+imgQuery: "AI platform architecture diagram UI RAG ML pipeline"
+
+B.5 Core Capabilities
+
+Intro:
+
+2 paragraphs explaining the capability philosophy
+
+For EACH capability:
+
+1 paragraph explaining what it does
+
+1 paragraph explaining why it matters operationally
+
+Capabilities:
+
+Chat assistant (tools, RAG, streaming)
+
+Document ingestion & retrieval
+
+Page Studio
+
+Documentation viewer
+
+ML Lab & exports
+
+Vector store upgrades
+
+Visuals:
+
+needsImage: true per capability
+
+imgQuery aligned per capability (specific, technical)
+
+B.6 Operating Principles
+
+Content requirements:
+
+Intro paragraph on why principles matter in AI systems
+
+Each principle:
+
+short title
+
+3–4 sentence explanation
+
+No slogans without substance
+
+Visual:
+
+needsImage: true
+
+imgQuery: "engineering principles abstract geometric"
+
+B.7 Founders & Governance
+
+Content requirements:
+
+Intro paragraph on leadership and accountability
+
+Bobga Nti — Founder / AI Engineer
+
+Detailed paragraph on background, system design focus, and role
+
+Yvonne Motuba — Company Secretary
+
+Paragraph on governance, compliance, and organisational stability
+
+This section MUST explicitly address trust and credibility
+
+Visual:
+
+needsImage: true
+
+imgQuery: "professional executive portrait neutral background"
+
+B.8 Credibility, Premium Capabilities & Roadmap
+
+Content requirements:
+
+2 paragraphs on current production capabilities
+
+2 paragraphs on premium / enterprise features:
+
+licensing
+
+audit
+
+deployment control
+
+1–2 paragraphs on roadmap direction
+
+No over-promising
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise product roadmap timeline minimal"
+
+B.9 FAQ
+
+Requirements:
+
+5–7 FAQs
+
+Each answer 2–3 sentences
+
+Must include:
+
+What is a client instance?
+
+Where does data live?
+
+Can we deploy privately?
+
+How licensing works?
+
+What premium provides?
+
+Visual: optional
+
+B.10 Final CTA
+
+Content requirements:
+
+1 paragraph reinforcing value and deployment model
+
+Clear next steps
+
+CTAs:
+
+“Talk to SyntaxMatrix”
+
+“View Documentation”
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise AI call to action abstract technology"
+
+🛠️ C) PAGE STUDIO RENDERING RULES
+
+Narrative prose first, UI blocks second
+
+Cards summarise; paragraphs explain
+
+No section should feel compressed
+
+The page must read like a full company profile
+
+✅ END OF INSTRUCTIONS
 """
 
-SMXAI_WEBSITE_DESCRIPTIONssssssssssss = """
-    SyntaxMatrix Overview
-    SyntaxMatrix is a battle-tested Python framework that accelerates AI application development from concept to production, slashing engineering overhead by up to 80%. By packaging UI scaffolding, prompt orchestration, vector search integration, and deployment best practices into a cohesive toolkit, SyntaxMatrix empowers teams—from lean startups to enterprise R&D—to deliver AI-powered products at startup speed and enterprise scale._
-    ____________________________________
-    Goals & Objectives
-    •	Rapid Prototyping
-    Enable teams to spin up interactive AI demos or internal tools in minutes, not weeks, by providing turnkey components for chat interfaces, file upload/processing (e.g., extracting text from PDFs), data visualization, and more.
-    •	Modular Extensibility
-    Offer a plug-and-play architecture (via syntaxmatrix.bootstrap, core, vector_db, file_processor, etc.) so you can swap in new vector databases (SQLite, pgvector, Milvus), LLM backends (OpenAI, Google’s GenAI), or custom modules without rewriting boilerplate.
-    •	Best-Practice Defaults
-    Bake in industry-standard patterns—persistent history stores, prompt-template management, API key handling, session management—while still allowing configuration overrides (e.g., via default.yaml or environment variables).
-    •	Consistency & Reproducibility
-    Maintain a unified UX across projects with theming, navbar generation, and widget libraries (display.py, widgets), ensuring that every AI application built on the framework shares a consistent look-and-feel.
-    ________________________________________
-    Target Audience
-    •	AI/ML Engineers & Researchers who want to demo models, build knowledge-base assistants, or perform exploratory data analysis dashboards.
-    •	Startups & Product Teams looking to deliver customer-facing AI features (chatbots, recommendation engines, content summarizers) with minimal infrastructure overhead.
-    •	Educators & Students seeking a hands-on environment to teach or learn about LLMs, vector search, and prompt engineering without dealing with full-stack complexities.
-    ________________________________________
-    Solution: SyntaxMatrix Framework
-    SyntaxMatrix unifies the entire AI app lifecycle into one modular, extensible package:
-    •	Turnkey Components: Pre-built chat interfaces, file-upload processors, visualization widgets, email/SMS workflows.
-    •	Seamless LLM Integration: Swap freely between OpenAI, Google Vertex, Anthropic, and self-hosted models via a unified API layer.
-    •	Plug-and-Play Vector Search: Adapters for SQLite, pgvector, Milvus—and roadmap for Pinecone, Weaviate, AWS OpenSearch—make semantic retrieval trivial.
-    •	Persistent State & Orchestration: Session history, prompt templating, and orchestration utilities ensure reproducibility and compliance.
-    •	Deployment-Ready: Industry-standard Docker images, CI/CD templates, Terraform modules, and monitoring dashboards ready out of the box.
-    ________________________________________
-    Key Features & Example Applications
-    •	Conversational Agents & Chatbots: Persistent session history, prompt-profile management, and dynamic prompt instructions make it easy to craft domain-specific assistants.
-    •	Document QA & Search: Built-in vectorizer and vector DB adapters enable rapid ingestion of PDFs or knowledge bases for semantic retrieval.
-    •	Data Analysis Dashboards: EDA output buffers and plotting utilities (plottings.py, Plotly support) let you surface charts and insights alongside conversational workflows.
-    •	Email & Notification Workflows: The emailer.py module streamlines outbound messaging based on AI-driven triggers.
-    •	Custom Model Catalogs & Templates: Centralized model_templates.py and settings/model_map.py support quick swapping between LLMs or prompt archetypes.
-    ________________________________________
-    Why It Matters
-    By removing repetitive setup tasks and enforcing a coherent project structure, SyntaxMatrix reduces time-to-market, promotes maintainable code, and democratizes access to sophisticated AI patterns. Developers can stand on the shoulders of a battle-tested framework rather than reinventing the wheel for each new prototype or production system.
-    ________________________________________
-    Future Directions
-    1.	Expanded Vector DB & Embedding Support
-        o	Add adapters for Pinecone, Weaviate, or AWS OpenSearch
-        o	Support hybrid retrieval (combining sparse and dense methods)
-    2.	Multi-Modal & Streaming Data
-        o	Integrate vision and audio pipelines for document OCR, image captioning, or speech transcription
-        o	Enable real-time data streaming and inference for live-update dashboards
-    3.	Deployment & MLOps Tooling
-        o	Built-in CI/CD templates, Docker images, and Terraform modules for cloud provisioning
-        o	Monitoring dashboards for latency, cost, and usage metrics
-    4.	Collaborative & No-Code Interfaces
-        o	Role-based access control and multi-user projects
-        o	Drag-and-drop prompt editors and pipeline builders for non-technical stakeholders
-    5.	Plugin Ecosystem & Marketplace
-        o	Community-contributed modules for domain-specific tasks (legal, healthcare, finance)
-        o	A registry to share prompt templates, UI widgets, and vector-DB schemas
+
+SMXAI_SERVICES_PAGE_INSTRUCTIONS = """
+
+IMPORTANT CONTEXT FOR THE GENERATOR
+
+🔒 PLAN GENERATION CONTRACT (MANDATORY)
+When generating the page plan JSON:
+EVERY major section MUST explicitly include an image
+For EACH section, the planner MUST emit:
+needsImage: true
+imgQuery: "<specific, concrete image search query>"
+Images MUST be attached at section level
+Do NOT rely on default templates
+If any section lacks needsImage + imgQuery, the plan is INVALID
+This applies to:
+
+hero
+service categories
+deployment models
+premium services
+licensing
+enterprise engagement
+final CTA
+
+🎯 PAGE GOAL
+Generate a long-form, enterprise Services page that explains:
+What services SyntaxMatrix provides
+How smxPP is delivered, deployed, and governed
+What premium and enterprise plans unlock
+How licensing works in practice
+Why enterprises trust this model
+Audience:
+
+CTOs
+Heads of Engineering
+Enterprise Architects
+Procurement & Compliance teams
+Technical buyers
+
+Tone:
+enterprise-first
+technical
+precise
+confident
+operational, not promotional
+
+📐 GLOBAL CONTENT RULES (NON-NEGOTIABLE)
+This page MUST be long-form prose
+Each MAJOR section must include:
+
+3-4 full paragraphs minimum
+
+Each paragraph 6-8 sentences
+
+Cards and bullets are allowed ONLY as summaries
+
+Prose explanations MUST come first
+
+Avoid slogans
+
+Assume sceptical, technical readers
+
+Thin or marketing-style content = failure.
+
+🖼️ GLOBAL IMAGE RULES (NON-NEGOTIABLE)
+
+Every MAJOR section MUST include a visual
+
+Images support comprehension
+
+Prefer:
+
+architecture diagrams
+
+deployment diagrams
+
+governance visuals
+
+Avoid:
+
+lifestyle imagery
+
+abstract “startup” photos
+
+🧩 A) LAYOUT & HERO RULES
+Hero Layout Options
+
+The generator MUST support:
+
+heroAlignment = "left"
+
+heroAlignment = "center"
+
+One must be explicitly selected.
+
+Hero Overlay Rules
+
+Overlay MUST be glassy / translucent
+
+NO opaque white banners
+
+Hero image must remain visible and dominant
+
+🧱 B) REQUIRED SECTION STRUCTURE (IN ORDER)
+B.1 Hero — Services Overview
+
+Content requirements:
+
+2–3 paragraphs explaining:
+
+SyntaxMatrix’s service philosophy
+
+Why services are centred around platform provisioning, not one-off builds
+
+How smxPP underpins all service offerings
+
+Clearly state that services scale from pilot to enterprise
+
+CTAs:
+
+“Explore Plans”
+
+“Talk to Engineering”
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise AI services platform architecture dark"
+
+B.2 Platform Provisioning Services
+
+Content requirements:
+
+3 paragraphs explaining:
+
+What it means to provision a client-owned AI platform
+
+How smxPP is delivered into a client environment
+
+How this differs from hosted AI tools
+
+Explicitly cover:
+
+runtime ownership
+
+data locality
+
+security boundary control
+
+Visual:
+
+needsImage: true
+
+imgQuery: "client owned AI platform deployment architecture diagram"
+
+B.3 Deployment Models
+
+Content requirements:
+
+2–3 paragraphs explaining supported deployment modes:
+
+on-premise
+
+private cloud
+
+regulated environments
+
+Explain operational implications of each
+
+Follow with a short comparison list
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise deployment models on premise cloud diagram"
+
+B.4 Core Service Domains
+
+Intro:
+
+2 paragraphs explaining how services map to enterprise needs
+
+For EACH domain:
+
+1 paragraph explaining what is delivered
+
+1 paragraph explaining business impact
+
+Domains include:
+
+AI Assistant & RAG Systems
+
+Document Ingestion & Knowledge Architecture
+
+Page Studio & Internal Portals
+
+ML Lab & Model Workflows
+
+Vector Store Engineering
+
+Visual:
+
+needsImage: true per domain
+
+imgQuery aligned to each domain (technical, specific)
+
+B.5 Premium & Enterprise Capabilities
+
+Content requirements:
+
+3 paragraphs explaining:
+
+what premium unlocks beyond free/trial
+
+why these features matter operationally
+
+MUST include:
+
+licensing enforcement
+
+auditability
+
+entitlement gating
+
+advanced vector backends
+
+ML exports
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise AI premium features governance diagram"
+
+B.6 Licensing & Governance Services
+
+Content requirements:
+
+3 paragraphs explaining:
+
+the licensing model
+
+remote licence validation
+
+fraud prevention and entitlement control
+
+Emphasise:
+
+enterprise trust
+
+subscription integrity
+
+offline and controlled environments
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise software licensing governance security diagram"
+
+B.7 Engagement & Support Model
+
+Content requirements:
+
+2–3 paragraphs explaining:
+
+onboarding
+
+technical enablement
+
+long-term support
+
+Explain how SyntaxMatrix works with engineering teams, not replaces them
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise engineering collaboration workflow diagram"
+
+B.8 Plans Overview (Narrative, Not Pricing Table)
+
+Content requirements:
+
+2 paragraphs explaining plan philosophy:
+
+Free / Trial
+
+Pro
+
+Business
+
+Enterprise
+
+No prices here — explain capability progression
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise service tiers progression diagram"
+
+B.9 Enterprise Trust & Compliance
+
+Content requirements:
+
+2 paragraphs addressing:
+
+data ownership
+
+auditability
+
+deployment control
+
+regulatory alignment
+
+This section MUST explicitly reassure enterprise buyers
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise compliance security audit abstract diagram"
+
+B.10 Final CTA
+
+Content requirements:
+
+1 paragraph reinforcing service value
+
+Clear next steps
+
+CTAs:
+
+“Talk to SyntaxMatrix”
+
+“View Licensing Explained”
+
+Visual:
+
+needsImage: true
+
+imgQuery: "enterprise AI consultation call to action abstract"
+
+🛠️ C) PAGE STUDIO RENDERING RULES
+
+Prose first, cards second
+
+No compressed sections
+
+Page must read like a consulting-grade services document
+
+✅ END OF INSTRUCTIONS
 """
 
-SMXAI_WEBSITE_DESCRIPTION = """
-SyntaxMatrix Limited - Company Information
- 
-Company Overview
-Corporate Identity
-Company Name: SyntaxMatrix (trading name)
-Legal Entity: SyntaxMatrix Limited (Ireland)
-Founded: 2025
-Headquarters: Ireland 
-Website: https://syntaxmatrix.net
-Contact:
-General: info@syntaxmatrix.net
-Support: support@syntaxmatrix.net
-Sales: sales@syntaxmatrix.net
-Founder & CEO: Bobga Nti (MSc in Artificial Intelligence)
-
-1.2 Company Description
-SyntaxMatrix Limited is an Ireland-based AI engineering company that builds and ships AI frameworks for provisioning client-ready AI platforms. The SyntaxMatrix Framework combines a chat assistant, Admin Panel, knowledge base ingestion, webpage generation and  management studio, and a Machine Learning Lab so teams can deliver complete AI systems without rebuilding the foundation for every client.
-
-1.3 Industry Positioning
-SyntaxMatrix is industry-agnostic, with the same platform pattern working for:
-Education
-Healthcare
-Legal
-Finance
-Retail
-Public sector
-Internal enterprise tools
-
-
-2. Mission, Vision & Values
-2.1 Mission
-Help teams ship AI platforms faster with a framework that is simple to operate, easy to extend, and safe to deploy.
-2.2 Vision
-AI platforms should be provisioned like infrastructure: consistent, repeatable, and ready for real workflows.
-
-2.3 Core Values
-Clarity first: Simple systems teams can reason about
-Engineering rigour: Code review, tests, and measurable quality gates
-Security by default: Least privilege, safe secrets handling, audit trails
-Customer empathy: Build for real workflows, not demo-only flows
-Responsible AI: Transparency, privacy, and operational control
-
-
-3. Leadership Team
-3.1 Executive Leadership
-Bobga Nti: Chief Executive Officer (CEO) & Founder
-Niall Byrne: Chief Technology Officer (CTO)
-Aoife O'Sullivan: Chief Operating Officer (COO)
-
-3.2 Department Heads
-Priya Menon: Head of AI Engineering
-Sinead Walsh: Head of Product
-Farah Hassan: Security & Compliance Officer
-Emma Kavanagh: Head of Sales & Partnerships
-Maeve Gallagher: Customer Success Lead
-
-3.3 Technical Team
-Daniel Okafor: Principal AI Engineer
-Luca Romano: Lead Software Engineer (Web Platform & Page Studio)
-Tomasz Nowak: DevOps & Cloud Engineer
-Yusuf Al-Khatib: Solutions Architect
-
-
-4. The SyntaxMatrix Framework
-4.1 Product Summary
-The SyntaxMatrix is a framework for provisioning AI platforms per client. It enables Mixture-of-Experts (MoE) routing where each task is directed to the best-fit model profile.
-4.2 Core Modules
-4.2.1 Chat Assistant (smxAI)
-Conversation UI with memory
-Answers grounded in system documents via RAG (Retrieval Augmented Generation)
-Integration with ML Lab outputs
-4.2.2 Knowledge Base Ingestion
-Automated PDF upload, text extraction, and chunking
-Semantic search with embeddings
-Separate knowledge bases per client deployment
-4.2.3 Admin Panel
-User and role management (user, employee, admin, superadmin + custom roles)
-Secrets management for API keys and configuration
-System document ingestion pipeline
-Page management and publishing workflow
-Media uploads and metadata
-4.2.4 Page Studio (AI Webpage Generation)
-AI-assisted page layout generation from slugs and site descriptions
-Template based compilation with consistent visual style
-Section level patching of existing pages
-Optional image fill via Pixabay queries
-Safe publishing guards (unsafe CTA links removed by default)
-4.2.5 ML Lab
-Dataset upload (CSV) and selection for analysis
-EDA tables and plots rendered in UI
-Code generation through dedicated coder profile
-Execution in managed kernel with captured outputs
-
-4.3 Mixture-of-Experts Profiles
-SyntaxMatrix uses multiple model profiles for cost control and specialisation:
-Admin profile: Concise operational answers
-Chat profile: General assistant responses
-Classifier profile: Intent detection and routing
-Summariser profile: Document and conversation summarization
-Coder/ML profile: Analysis and engineering code
-Page Studio developer profile: Page layouts and section structure
-Image profile: Image-related tasks
-
-
-5. Technical Architecture
-5.1 System Overview
-SyntaxMatrix runs as a Flask web application with:
-UI scaffolding and role-aware access
-Local persistence (SQLite)
-Knowledge base ingestion
-Page generation system
-ML Lab execution environment
-
-5.2 Key Code Modules
-Core/Routes: Flask app runtime and route wiring
-Auth: Authentication, roles, and audit logging
-File Processor: PDF extraction and chunk preparation
-Vectorizer: Embedding generation
-Vector DB: Persistent embeddings store (SQLite, PostgresSQL)
-History Store: Chat persistence for users
-Kernel Manager: Managed kernel execution for ML Lab
-
-5.3 Page Studio Implementation
-Page Builder: Builds layout JSON with image fill
-Pages Layout Contractor: Normalises and validates layouts before publishing
-Published Page Patcher: Applies safe section level patches with link sanitisation
-Page Editor: Page editing, sorting, and drag-and-drop page widgets for page updates.
-
-5.4 Knowledge Base Implementation
-PDF text extraction via PyPDF2
-Default chunking: recursive split with 2500-character max
-Embeddings stored in SQLite with metadata
-Tenant-scoped at deployment level (per client instance)
-
-
-6. Security, Privacy & Compliance
-6.1 Security Model
-Designed for controlled deployments with robust access control
-Default storage: SQLite within client instance directory
-Organizations may add network controls and central identity providers
-
-6.2 Authentication & Roles
-Users stored in SQLite with hashed passwords (Server DB (premium)
-Role hierarchy: user, employee, admin, superadmin + custom roles
-Initial superadmin ('ceo') seeded with credentials in superadmin_credentials.txt
-All role changes recorded in audit table
-
-6.3 Secrets Management
-API keys stored in dedicated SQLite table
-Keys scoped tightly, rotated regularly
-Never output in chat responses
-
-6.4 Privacy Posture
-Upload only documents with proper processing rights
-Deployments isolated per client for data separation
-Provider settings aligned with data retention requirements
-
-
-7. Deployment & Provisioning
-7.1 Provisioning Model
-SyntaxMatrix is typically provisioned per client as separate deployments, each with:
-Own instance directory
-Dedicated databases
-Separate uploaded documents and pages
-Independent configuration
-
-7.2 Per-Client Deployment Benefits
-Simplified data isolation and access control
-Controlled upgrade rollout per client
-Predictable operations for agencies serving multiple clients
-
-7.3 Provisioning Checklist
-Create new client instance directory
-Configure model profiles and API keys
-Create admin/employee accounts with password reset enforcement
-Upload system/company documents and validate retrieval
-Create/generate pages using Page Studio
-Upload dataset and validate ML Lab tasks
-
-
-8. Pricing & Licensing
-8.1 Bring-Your-Own-Key (BYOK) Model
-7-day free trial: Full feature access with your provider keys
-After trial: €149/month per client deployment
-Includes framework updates and basic support
-Model/embedding usage billed directly by your providers
-Annual option: Pay yearly, get 2 months free (~16-17% discount)
-
-8.2 Managed Usage Plans
-For clients preferring single monthly invoices:
-Starter Plan
-€399/month per instance
-10M standard text tokens/month
-2M embedding tokens/month
-Medium Plan
-€899/month per instance
-30M standard text tokens/month
-6M embedding tokens/month
-Heavy Plan
-€1,999/month per instance
-80M standard text tokens/month
-15M embedding tokens/month
-
-8.3 Overage & Enterprise Options
-Usage beyond allowance billed at provider pass-through rates plus platform handling fee
-Pre-purchased top-up credits available
-Enterprise clients can request custom caps, allow-lists, and spend limits
-
-
-9. Target Market & Value Proposition
-9.1 Ideal Customers
-Agencies delivering AI solutions to multiple clients
-Internal engineering teams building AI platforms for business units
-AI developers wanting reusable platform foundations
-Teams needing built-in admin tooling, pages, and knowledge ingestion
-
-9.2 Problems Solved
-Eliminates repeated rebuilding of authentication, admin tooling, storage, and UI scaffolding
-Makes knowledge base ingestion a product feature rather than custom project
-Maintains per-client deployment isolation for security and operational simplicity
-Provides integrated page system for marketing/product pages
-Includes ML Lab for analytics without separate environment
-
-9.3 Key Outcomes
-Faster time-to-demo and time-to-production
-Clear governance with roles, audits, and secrets management
-Lower operational risk through per-client isolation
-Better cost control via model profiles and routing
-Extensible platform for custom connectors and pages
-
-
-
-10. Implementation Methodology
-10.1 Implementation Playbook
-Phase 1: Discovery
-Define client use cases (support, policy Q&A, analytics, internal tooling)
-Confirm data sources for ingestion
-Agree hosting model (client-managed vs SyntaxMatrix-managed)
-Define access model (roles, SSO requirements, network restrictions)
-
-Phase 2: Provisioning
-Create per-client deployment and instance directory
-Initialize databases and admin accounts
-Configure model profiles
-Upload core system documents
-Generate and publish initial pages
-
-Phase 3: Production Hardening
-Set spend limits and allow-lists for providers
-Add monitoring and error reporting
-Implement backup strategy for SQLite, server DBs, and uploads
-Define change management and release cadence
-
-10.2 Demo Script
-Log in as admin, show role management and secrets
-Upload 2-3 PDFs, demonstrate ingestion completion
-Ask assistant questions showing retrieved answers
-Generate new page in Page Studio, patch/publish it
-Upload dataset and run Machine Learning Lab task to show explainable and downloadable report: tables/plots, generated code for said tasks, and output summary.
-
-
-11. Competitive Landscape
-11.1 Pricing Reference Points (Late Dec 2025)
-Dify Cloud: Professional $59-$159 per workspace/month
-Flowise Cloud: Starter $35, Pro $65/month
-Botpress: Plus $89, Team $495/month (+ AI spend)
-Dust: Pro €29 per user/month
-LangSmith: Plus $39 per seat/month
-Stack AI: Starter $199, Team $899/month
-
-11.2 SyntaxMatrix Differentiation
-Per-instance licensing aligns with per-client deployment reality
-BYOK model keeps model spend under client's provider billing
-Managed usage plans bundle platform fee with usage allowance
-Comprehensive platform (not just chatbot) with Admin Panel, Page Studio, ML Lab
-
-
-12. Brand & Messaging
-12.1 Core Messages
-"Provision a client-ready AI platform in days, not weeks"
-"Built-in Admin Panel for users, secrets, pages, and knowledge base ingestion"
-"Page Studio: generate and publish pages from templates with AI assistance"
-"ML Lab: guided dataset analysis inside the same platform"
-"Model profiles provide cost control and specialist outputs"
-
-12.2 Short Boilerplate
-"SyntaxMatrix is an Irish AI engineering company. SyntaxMatrix helps teams ship client-ready AI platforms with a framework that includes an assistant, knowledge base ingestion, Page Studio, and an ML Lab."
-
-
-12.3 Brand Positioning
-Positioned as an AI engineering company building deployable AI platform framework, focusing on:
-Delivery speed and repeatability
-Operational controls
-Adaptability to any industry
-
-13. Operating Information
-13.1 Weekly Cadence
-Monday: Priorities, risk review, customer escalations
-Mid-week: Engineering planning and QA sign-off for releases
-Friday: Demos, customer feedback review, roadmap updates
-
-13.2 Quality Gates
-Changes reviewed and tested before release
-Security-sensitive changes require compliance sign-off
-Provisioning templates/scripts versioned and tested like product code
-
-13.3 Support Structure
-Basic support included with all plans
-Premium support options available
-Uptime targets for managed hosting (TBC)
-
-
-14. Technical Glossary
-Agency/Profile: Named configuration for provider + model + purpose
-RAG: Retrieval Augmented Generation - answering with retrieved context
-SMIV: SyntaxMatrix In-memory Vectorstore (transient)
-SMPV: SyntaxMatrix Persistent Vectorstore (SQLite embeddings, Server DB)
-Chunk: Section of extracted document text stored for retrieval
-ML Lab: Dataset analysis environment with code generation and execution
-Page Studio: Page generation and publishing workflow
-MoE: Mixture-of-Experts - using different model profiles for different tasks
 
+SMXAI_GALLERY_PAGE_INSTRUCTIONS = """
+You are generating a GALLERY page. This page must behave like a true photo/screenshot gallery.
+
+ABSOLUTE REQUIREMENTS
+1) The page plan MUST include a section with:
+   - type: "gallery"
+   - id: "sec_gallery" (or similar)
+2) The gallery section MUST contain 6–9 items where EACH item is a true image tile:
+   - item.type MUST be "image" (NOT "card")
+   - Use short titles (2–5 words max) and very short captions (0–1 sentence).
+   - Avoid long paragraphs in the gallery; do NOT make it look like a features section.
+
+GALLERY ITEM SCHEMA (use this exactly)
+Each gallery item MUST look like:
+{
+  "id": "g1",
+  "type": "image",
+  "title": "Admin Panel",
+  "text": "Pages, uploads, audit trail.",
+  "imgQuery": "admin panel dashboard ui dark theme",
+  "needsImage": true,
+  "imageUrl": "",
+  "thumbUrl": "",
+}
+
+NOTES:
+- imageUrl/thumbUrl can be empty at planning time; the system will fill them later from imgQuery.
+- If a thumbnail exists, thumbUrl should point to it; imageUrl should point to the full image.
+- The gallery rail should be primarily visual. Captions are optional and must be short.
+
+DESIGN INTENT
+- Gallery section = image-first browsing (tiles, click opens lightbox).
+- If you need explanatory content, put it in separate sections (richtext/features/cta) OUTSIDE the gallery.
+- Do NOT place "card" items inside the gallery section unless explicitly requested (default: none).
+
+PAGE STRUCTURE (recommended)
+- hero (clear title + one sentence)
+- gallery (the rail of image tiles; 6–9 items)
+- richtext or testimonials (optional, short)
+- cta (contact / request demo)
+
+TONE
+- Enterprise AI product showcase, clean and concise.
+"""
+
+
+SMXAI_CAREERS_PAGE_INSTRUCTIONS = """
+You are generating a CAREERS page
+
+GOAL
+Create a careers landing page that:
+- communicates mission + culture clearly
+- lists open roles in a structured way
+- explains hiring process and expectations
+- provides a clear application CTA
+- stays concise, skimmable, and professional (enterprise AI company tone)
+
+ABSOLUTE REQUIREMENTS
+1) The plan MUST include a hero section (type: "hero") with:
+   - a clear headline about careers at SyntaxMatrix
+   - a short subheading (1–2 sentences) that communicates mission and what candidates can expect
+   - a primary CTA such as "Apply now" / "Email your CV"
+   - optional secondary CTA "View open roles"
+
+2) The plan MUST include an "Open Roles" section.
+   Use either:
+   - type: "features" (recommended), OR
+   - type: "richtext" if you need richer formatting.
+   Each role must be presented as a compact card-like entry with:
+   - Role Title
+   - Location/Remote (e.g., Ireland / Remote / Hybrid Dublin)
+   - Type (Full-time / Contract / Internship)
+   - Short summary (max 2 sentences)
+   - Key skills (4–6 bullet-style phrases)
+   - An "Apply" callout (email or link placeholder)
+
+3) The plan MUST include a hiring process section that is clear and realistic.
+   Use type: "richtext" or "features" with 4–6 steps:
+   - Apply
+   - Screening
+   - Technical assessment (practical, small)
+   - Interview(s)
+   - Offer
+   - Onboarding
+
+4) The plan MUST include a FAQ section (type: "faq") with at least 6 FAQs:
+   Include: remote policy, visa sponsorship (if unknown say “case-by-case”), interview steps,
+   expected stack, timeline, compensation transparency approach, and what makes a strong application.
+
+5) The plan MUST include a final CTA section (type: "cta") with:
+   - a direct instruction to apply (email/link placeholder)
+   - what to include (CV, links, short note, portfolio/GitHub)
+   - response time expectation (e.g., “we aim to respond within X business days”)
+
+CONTENT CONSTRAINTS
+- Do NOT invent named employees or fake testimonials.
+- Do NOT claim benefits you cannot guarantee (health insurance, pension, etc.). If unsure, phrase as “where applicable” or omit.
+- Avoid exaggerated claims. Keep language grounded and specific.
+- Avoid long paragraphs. Prefer short blocks, lists, and scannable structure.
+- Keep total page copy “tight”: aim for clarity over volume.
+
+STYLE
+- Enterprise AI engineering vibe: confident, precise, practical.
+- Emphasise that SyntaxMatrix is an AI algorithm design company and a framework builder (RAG systems, multi-agent workflows, evaluation, deployments).
+- Mention core tech themes appropriately: Python, Flask, Dash, vector stores, RAG, eval tooling, cloud deployments, MLOps. Do not overspecify if not necessary.
+
+RECOMMENDED PAGE STRUCTURE (sections)
+1) hero
+2) richtext: "Why work with us" (mission, values, what you’ll build)
+3) features: "Open roles" (6–10 role cards max; if fewer roles, show 3–6)
+4) richtext/features: "Hiring process"
+5) faq
+6) cta
+
+OPEN ROLES (DEFAULT SET)
+If no specific roles were provided, include a sensible starter list (edit titles to fit page length):
+- AI/ML Engineer (RAG + agents)
+- Full-stack Engineer (Flask/Dash + UI)
+- MLOps / Platform Engineer (deployments, CI/CD)
+- Technical Writer / Developer Advocate (docs, examples, workshops)
+- Intern / Graduate (AI Engineering)
+
+ROLE CARD TEMPLATE (features item shape)
+Each role in the "Open roles" section should be an item like:
+{
+  "id": "role_1",
+  "type": "card",
+  "title": "AI/ML Engineer (RAG + Agents)",
+  "text": "Build production RAG pipelines and deterministic multi-agent workflows. Remote/Hybrid • Full-time/Contract.\nSkills: Python, vector search, evaluation, prompt/tool orchestration, deployments.\nApply: careers@<your-domain> (placeholder)"
+}
+
+FAQ SUGGESTED QUESTIONS (use or adapt)
+- Do you offer remote work?
+- What does the interview process look like?
+- What tech stack do you use day-to-day?
+- Do you sponsor visas?
+- What should I include in my application?
+- How quickly will I hear back?
+- Can I apply if I’m early-career?
+- Do you take contractors?
+
+FINAL CTA COPY REQUIREMENTS
+Include:
+- email placeholder and/or application link placeholder
+- request: CV + links (GitHub/LinkedIn/portfolio) + short note
+- note: “If you’ve built RAG systems, agent workflows, or evaluation tooling, include a brief write-up.”
+
+OUTPUT QUALITY CHECK
+Before finalising, ensure:
+- "Open roles" exists and is clearly labelled.
+- Hiring process is present and actionable.
+- FAQ has 6+ items.
+- CTA is explicit and contains application instructions.
 """
 
-SMXAI_PAGE_INSTRUCTIONS = f"""
+
+SMXAI_BLOG_PAGE_INSTRUCTIONS = """
+## 3.1 Blog index page structure
+1) Hero  
+2) Featured post  
+3) Post grid  
+4) Tag filter + search  
+5) CTA (optional newsletter)
+
+Post cards:
+- Title (2 lines)
+- Excerpt (2–3 lines)
+- Date + tag
+- “Read more”
+
+## 3.2 Blog post page structure
+- Title + metadata
+- Optional TOC from H2/H3
+- Body with callouts
+- CTA footer
+
+---
+
+# 4) Matching rules (template selection)
+
+- “services”, “solutions”, “packages”, “pricing”, “engagement”
+  → Services Page
+
+- “gallery”, “photos”, “portfolio”, “screenshots”, “showcase”
+  → Gallery Page (horizontal + lightbox)
+
+- “blog”, “articles”, “updates”, “news”, “release notes”
+  → Blog Page
+
+"""
+
+
+SMXAI_NEW_PAGE_INSTRUCTIONS_DEFAULT = f"""
     0· Parse the Website Description (MANDATORY):\n{SMXAI_WEBSITE_DESCRIPTION}\n\n
     1. Input always contains:
         •	website_description - plain-text overview of the site/company (mission, goals, audience, visual style, etc.).
@@ -463,7 +1196,7 @@ SMXAI_PAGE_INSTRUCTIONS = f"""
             o Parse website_description and page_title per Steps 0–6.
             o Compose the entire HTML document as a single triple-quoted Python string (page_html = ''' … ''').
             o Return that string (return html).
-            o Keep the OpenAI SDK demo call in the page (hidden <script> tag) to satisfy the SDK-usage requirement.
+            requirement.
         iii. Function docstring
             '''
             Generate a fully responsive, animated, single-file web page aligned with the
@@ -483,4 +1216,43 @@ SMXAI_PAGE_INSTRUCTIONS = f"""
         •	No duplicate header/footer.
         •	All identifiers safely namespaced.
         •	Return only the HTML text—no commentary or extra files.
-"""
+"""
+
+
+def get_page_instructions(page_slug: str = "", page_title: str = "") -> str:
+    """
+    Returns the correct page-type instruction block based on the requested page slug/title.
+    This is used to override the generic default prompt during AI page generation.
+    """
+    key = f"{page_slug or ''} {page_title or ''}".strip().lower()
+
+    # Home page
+    if any(w in key for w in ("landing", "landing-page", "home", "home-page", "homepage")):
+        return SMXAI_LANDING_PAGE_INSTRUCTIONS
+
+    # About page
+    if any(w in key for w in ("about", "about-us", "who-we-are", "company", "our-story", "team")):
+        return SMXAI_ABOUT_PAGE_INSTRUCTIONS
+
+    # Services page
+    if any(w in key for w in ("services", "solutions", "packages", "pricing", "engagement")):
+        return SMXAI_SERVICES_PAGE_INSTRUCTIONS
+
+    # Gallery page
+    if any(w in key for w in ("gallery", "photos", "portfolio", "screenshots", "showcase")):
+        return SMXAI_GALLERY_PAGE_INSTRUCTIONS
+    
+    if any(w in key for w in ("careers", "jobs", "pricing", "contact", "contact-us", "docs", "documentation", "join", "join-us")):
+        return SMXAI_CAREERS_PAGE_INSTRUCTIONS
+
+    # Blog page
+    if any(w in key for w in ("blog", "articles", "updates", "news", "release-notes")):
+        return SMXAI_BLOG_PAGE_INSTRUCTIONS
+
+    # Licence page
+    if any(w in key for w in ("licence", "license", "licence-page", "licensing")):
+        return SMXAI_LICENCE_PAGE_INSTRUCTIONS
+    
+
+    # Fallback
+    return SMXAI_NEW_PAGE_INSTRUCTIONS_DEFAULT