@dyrected/core 1.0.9 → 2.1.0

package/dist/index.js

@@ -1,6 +1,7 @@
 import {
+  createDyrectedApp,
   normalizeConfig
-} from "./chunk-GM4WW6IE.js";
+} from "./chunk-22JTWD74.js";
 
 // src/utils/setup-prompt.ts
 function buildEnvironmentSection(frameworkLabel, isSelfHosted, config) {
@@ -10,41 +11,75 @@ function buildEnvironmentSection(frameworkLabel, isSelfHosted, config) {
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
 1. ENVIRONMENT
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-- Framework : ${frameworkLabel}
+- Framework : ${frameworkLabel || "Detect it"}
 - Host Type : ${isSelfHosted ? "Self-Hosted (Local/Private Server)" : "Managed (Dyrected Cloud)"}
 - API Base  : ${config.baseUrl || "http://localhost:3000"}
 ${credentialLines}`;
 }
-function buildDiagnosticSection(existingSite) {
-  if (existingSite) {
-    return `
-\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-2. PHASE 0 \u2014 DIAGNOSTIC (EXISTING SITE)
-\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-Before writing any code, scan the existing codebase and report:
-- All hardcoded text strings that should be CMS-managed
-- All repeated data structures that should become collections
-- All static pages that marketing will want to edit independently
-- Any existing fetch or API calls that overlap with Dyrected
-
-Then propose a backup plan: extract all current content into a
-migration/ folder as structured .md or .json files BEFORE
-modifying any code.
-
-Do NOT write any implementation code until you have reported
-your findings and the user has confirmed the content plan.`;
-  }
+function buildDiagnosticSection() {
   return `
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-2. PHASE 0 \u2014 DISCOVERY (NEW SITE)
+2. PHASE 0 \u2014 DISCOVERY
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-This is a new project. Before designing the content model, ask:
-- "What are your core content types? (e.g. Services, Team, Blog, Projects)"
-- "Which pages should marketing manage independently with blocks?"
-- "Are there any pages that must remain static and never become CMS-managed?"
-- "What is the primary goal of the site \u2014 marketing, e-commerce, portfolio, SaaS?"
-
-Do NOT write any code until the user has answered these questions.`;
+Before writing any code, you MUST ask the user these questions.
+Write them exactly as shown below \u2014 in plain language with examples.
+Wait for the user to answer ALL of them before proceeding.
+
+\u2500\u2500\u2500 QUESTION 1 \u2500\u2500\u2500
+Ask:
+"Do you already have a website built, or are we starting fresh?
+
+  \u2192 Already built: share your project or describe what pages you have
+    (e.g. Home, About, Services, Contact)
+  \u2192 Starting fresh: just say 'new site' and describe what the site is for"
+
+\u2500\u2500\u2500 QUESTION 2 \u2500\u2500\u2500
+Ask:
+"What kind of content will your client need to update regularly?
+
+  Here are some examples to help you think:
+  \u2192 Blog posts or news articles
+  \u2192 Team member profiles (name, photo, bio)
+  \u2192 Services or product descriptions
+  \u2192 Testimonials or reviews
+  \u2192 Event listings
+  \u2192 FAQs
+  \u2192 Homepage text (headline, hero image, call-to-action button)
+
+  Just list the ones that apply. You can say things like:
+  'They need to update blog posts and team members'"
+
+\u2500\u2500\u2500 QUESTION 3 \u2500\u2500\u2500
+Ask:
+"Are there any pages on the site that should NEVER change \u2014 like a
+  custom-coded page you want to leave exactly as it is?
+
+  Example answer: 'The homepage has a custom animation, leave that alone.
+  Everything else can be managed from the CMS.'
+
+  If everything should be manageable, just say 'all pages'"
+
+\u2500\u2500\u2500 QUESTION 4 \u2500\u2500\u2500
+Ask:
+"What is this website for? Pick the closest description:
+
+  A) A business or agency marketing site (show services, get leads)
+  B) A blog or content site (publish articles regularly)
+  C) A SaaS or product site (landing page, pricing, features)
+  D) A portfolio (show work, case studies)
+  E) An e-commerce or product catalogue
+  F) Something else \u2014 describe it in one sentence"
+
+\u2500\u2500\u2500 IF EXISTING SITE \u2500\u2500\u2500
+If the user confirms they have an existing site, also:
+- Scan the codebase for all hardcoded text that should be CMS-managed
+- Identify repeated data structures that should become collections
+- Propose saving current content to a migration/ folder as .json files
+  BEFORE touching any code
+- Report your findings to the user and get confirmation before proceeding
+
+Do NOT write any implementation code until all questions are answered
+and the user has confirmed the content plan.`;
 }
 function buildConstraintsSection() {
   return `
@@ -74,7 +109,7 @@ function buildSchemaRulesSection() {
 - Never drop existing fields from the schema. Mark unused fields as deprecated only.
 - All new fields must have a defaultValue.
 - Never rename a field slug \u2014 add a new field and migrate data separately.
-- Run npx @dyrected/cli sync:schema after every config change.`;
+- For Cloud deployments, run npx @dyrected/cli sync:schema after every config change. Self-hosted deployments sync automatically on startup.`;
 }
 function buildDoNotSection() {
   return `
@@ -85,7 +120,7 @@ function buildDoNotSection() {
 - Do NOT add custom auth middleware to the admin route.
   Dyrected handles admin authentication internally. Do not wrap,
   protect, or redirect the admin route yourself.
-- Do NOT use renderAdminUI in a Nuxt project. Use the DyrectedAdmin
+- Do NOT use renderAdminUI in a Nuxt.js project. Use the DyrectedAdmin
   component which is auto-imported by @dyrected/nuxt.
 - Do NOT modify or overwrite existing pages without first preserving their data.
 - Do NOT drop, rename, or remove fields from an existing schema.
@@ -100,23 +135,26 @@ function buildTechnicalReferenceSection() {
 Use defineCollection, defineGlobal, and defineConfig from '@dyrected/core'.
 
 FIELD TYPES:
-- Primitive  : text | textarea | richText | number | boolean | date | email | url | json
+- Primitive  : text | textarea | richText | number | boolean | date | email | url | json | image
 - Choice     : select | multiSelect           (requires options: [{ label, value }])
 - Structural : array | object                 (requires nested fields: [...])
-- Relation   : relationship                   (requires collection: '<slug>')
+- Relation   : relationship                   (requires relationTo: '<slug>')
 - Media      : relationship to an upload collection (e.g. 'media')
 - Blocks     : blocks                         (requires blocks: [{ slug, labels, fields }])
 
 COLLECTION OPTIONS:
 - upload: true       \u2014 media library with file upload support
 - auth: true         \u2014 adds login/me endpoints; password field is auto-managed
+- audit: true        \u2014 enables activity logging
 - admin.useAsTitle   \u2014 field used as display title in admin list view
 - admin.group        \u2014 groups collection under a sidebar heading
 - admin.hidden       \u2014 hides collection from the sidebar (internal/system use)
 
 FIELD OPTIONS:
+- label              \u2014 user-friendly display name (REQUIRED for all fields)
 - required           \u2014 validation
 - unique             \u2014 database-level uniqueness constraint
+- hasMany            \u2014 allow multiple values (for relationship, select, image)
 - defaultValue       \u2014 fallback value (required on all new fields added to existing schemas)
 - admin.condition    \u2014 Jexl expression string to conditionally show/hide field
                        e.g. "status == \\"published\\""
@@ -138,14 +176,13 @@ Always include a default case in your switch for unknown block types.
 COMPLETE SCHEMA EXAMPLE:
 \`\`\`ts
 import { defineCollection, defineGlobal, defineConfig } from '@dyrected/core'
-import { MongoAdapter } from '@dyrected/db-mongodb'
-import { S3StorageAdapter } from '@dyrected/storage-s3'
+import { SqliteAdapter } from '@dyrected/db-sqlite'
 
 const media = defineCollection({
   slug: 'media',
   upload: true,
   fields: [
-    { name: 'alt', type: 'text', label: 'Alt Text' },
+    { name: 'alt', label: 'Alt Text', type: 'text' },
   ],
 })
 
@@ -153,44 +190,45 @@ const pages = defineCollection({
   slug: 'pages',
   admin: { useAsTitle: 'title', group: 'Content' },
   fields: [
-    { name: 'title', type: 'text', required: true },
-    { name: 'slug',  type: 'text', required: true, unique: true },
-    { name: 'seo', type: 'object', fields: [
-      { name: 'metaTitle',       type: 'text' },
-      { name: 'metaDescription', type: 'textarea' },
-      { name: 'ogImage',         type: 'relationship', collection: 'media' },
+    { name: 'title', label: 'Title', type: 'text', required: true },
+    { name: 'slug',  label: 'URL Slug', type: 'text', required: true, unique: true },
+    { name: 'seo', label: 'SEO Metadata', type: 'object', fields: [
+      { name: 'metaTitle',       label: 'Meta Title',       type: 'text' },
+      { name: 'metaDescription', label: 'Meta Description', type: 'textarea' },
+      { name: 'ogImage',         label: 'OG Image',         type: 'relationship', relationTo: 'media' },
     ]},
     {
       name: 'layout',
+      label: 'Page Layout',
       type: 'blocks',
       blocks: [
         {
           slug: 'hero',
           labels: { singular: 'Hero', plural: 'Heroes' },
           fields: [
-            { name: 'heading',    type: 'text',         required: true },
-            { name: 'subheading', type: 'textarea' },
-            { name: 'image',      type: 'relationship', collection: 'media' },
-            { name: 'ctaLabel',   type: 'text' },
-            { name: 'ctaLink',    type: 'url' },
+            { name: 'heading',    label: 'Heading',    type: 'text',         required: true },
+            { name: 'subheading', label: 'Subheading', type: 'textarea' },
+            { name: 'image',      label: 'Hero Image', type: 'relationship', relationTo: 'media' },
+            { name: 'ctaLabel',   label: 'Button Label', type: 'text' },
+            { name: 'ctaLink',    label: 'Button Link',  type: 'url' },
           ],
         },
         {
           slug: 'richContent',
           labels: { singular: 'Rich Content', plural: 'Rich Content Blocks' },
           fields: [
-            { name: 'content', type: 'richText', required: true },
+            { name: 'content', label: 'Content', type: 'richText', required: true },
           ],
         },
         {
           slug: 'callToAction',
           labels: { singular: 'Call to Action', plural: 'Calls to Action' },
           fields: [
-            { name: 'heading',     type: 'text', required: true },
-            { name: 'description', type: 'textarea' },
-            { name: 'buttonLabel', type: 'text' },
-            { name: 'buttonLink',  type: 'url' },
-            { name: 'theme', type: 'select', options: [
+            { name: 'heading',     label: 'Heading',     type: 'text', required: true },
+            { name: 'description', label: 'Description', type: 'textarea' },
+            { name: 'buttonLabel', label: 'Button Text', type: 'text' },
+            { name: 'buttonLink',  label: 'Button Link',  type: 'url' },
+            { name: 'theme', label: 'Theme', type: 'select', options: [
               { label: 'Primary',   value: 'primary' },
               { label: 'Secondary', value: 'secondary' },
               { label: 'Dark',      value: 'dark' },
@@ -206,28 +244,17 @@ const settings = defineGlobal({
   slug: 'settings',
   label: 'Site Settings',
   fields: [
-    { name: 'siteName',   type: 'text' },
-    { name: 'tagline',    type: 'text' },
-    { name: 'logo',       type: 'relationship', collection: 'media' },
-    { name: 'footerText', type: 'textarea' },
+    { name: 'siteName',   label: 'Site Name',    type: 'text' },
+    { name: 'tagline',    label: 'Site Tagline', type: 'text' },
+    { name: 'logo',       label: 'Site Logo',    type: 'relationship', relationTo: 'media' },
+    { name: 'footerText', label: 'Footer Text',  type: 'textarea' },
   ],
 })
 
 export default defineConfig({
   collections: [media, pages],
-  globals: [settings],
-  db: new MongoAdapter({
-    url: process.env.DATABASE_URL!,
-    dbName: 'dyrected_cms',
-  }),
-  storage: new S3StorageAdapter({
-    bucket: process.env.S3_BUCKET!,
-    region: process.env.S3_REGION!,
-    credentials: {
-      accessKeyId: process.env.S3_ACCESS_KEY_ID!,
-      secretAccessKey: process.env.S3_SECRET_ACCESS_KEY!,
-    },
-  }),
+  globals:     [settings],
+  db: new SqliteAdapter({ filename: './dyrected.db' }),
 })
 \`\`\``;
 }
@@ -246,7 +273,8 @@ Return your response in exactly this order. Do not combine steps. Do not skip st
 6. Migration/fallback strategy \u2014 numbered steps
 7. Schema sync command
 
-API Reference: https://docs.dyrected.com`;
+API Reference: https://docs.dyrected.com
+If you are unsure about any syntax or property, refer to the documentation above.`;
 }
 function buildFrameworkSection(activeTab, isSelfHosted, config) {
   const envPrefix = activeTab === "next" ? "NEXT_PUBLIC_" : activeTab === "nuxt" ? "NUXT_PUBLIC_" : "";
@@ -268,14 +296,14 @@ export const dyrected = createClient({
 })
 \`\`\`
 
-2. Admin Route (app/admin/[[...slug]]/page.tsx):
+2. Admin Route (app/cms/page.tsx):
 \`\`\`tsx
 import { DyrectedAdmin } from '@dyrected/next/admin'
 
 export default function AdminPage() {
   // DyrectedAdmin handles routing, auth, and CSS automatically.
   // Do NOT wrap this in custom auth middleware.
-  return <DyrectedAdmin basename="/admin" />
+  return <DyrectedAdmin basename="/cms" />
 }
 \`\`\`
 
@@ -300,9 +328,9 @@ export default async function CmsPage({ params }: { params: { slug: string[] } }
 \`\`\``,
     nuxt: `
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-8. IMPLEMENTATION \u2014 Nuxt
+8. IMPLEMENTATION \u2014 Nuxt.js
 \u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
-1. Nuxt Config (nuxt.config.ts):
+1. Nuxt.js Config (nuxt.config.ts):
 \`\`\`ts
 export default defineNuxtConfig({
   modules: ['@dyrected/nuxt'],
@@ -314,7 +342,7 @@ export default defineNuxtConfig({
 })
 \`\`\`
 
-2. Admin Route (pages/admin.vue):
+2. Admin Route (pages/cms/index.vue):
 \`\`\`vue
 <script setup lang="ts">
 // DyrectedAdmin is auto-imported by @dyrected/nuxt.
@@ -326,7 +354,7 @@ definePageMeta({ layout: false })
 
 <template>
   <ClientOnly>
-    <DyrectedAdmin basename="/admin" />
+    <DyrectedAdmin basename="/cms" />
   </ClientOnly>
 </template>
 \`\`\`
@@ -373,7 +401,7 @@ export const dyrected = createClient({
 })
 \`\`\`
 
-2. Admin Route (pages/admin.tsx):
+2. Admin Route (pages/cms.tsx):
 \`\`\`tsx
 import { AdminUI } from '@dyrected/admin'
 import '@dyrected/admin/styles'
@@ -405,7 +433,7 @@ export const dyrected = createClient({
 })
 \`\`\`
 
-2. Admin Route (pages/admin.vue):
+2. Admin Route (pages/cms.vue):
 \`\`\`vue
 <template>
   <div ref="container" style="height: 100vh" />
@@ -433,14 +461,350 @@ onUnmounted(() => cleanup?.())
   };
   return sections[activeTab] || sections.next;
 }
+function generateFreshSetupPrompt(activeTab, config) {
+  const frameworkLabel = activeTab === "next" ? "Next.js" : activeTab === "nuxt" ? "Nuxt.js" : activeTab ? activeTab.charAt(0).toUpperCase() + activeTab.slice(1) : "the project's detected framework";
+  const isSelfHosted = config.isSelfHosted === true || !config.apiKey && !config.siteId;
+  const frameworkSetup = {
+    nuxt: `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+3. INSTALLATION STEPS \u2014 Run these in order
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+Tell the user to follow these steps exactly. Explain each one in plain
+language before showing the command. Do not skip any step.
+
+STEP 1 \u2014 Initialize Dyrected
+Tell the user:
+"Run this command in your terminal inside your Nuxt.js project folder.
+It will set everything up for you automatically."
+
+\`\`\`bash
+npx @dyrected/cli init
+\`\`\`
+
+When it asks questions, tell the user to:
+- Choose: Nuxt.js 3
+- Choose: SQLite (easiest option, no extra setup needed)
+
+The CLI will automatically:
+- Install all required packages
+- Create a dyrected.config.ts file
+- Mount the Admin UI at pages/cms/index.vue
+- Generate a .env.example file
+
+STEP 2 \u2014 Register the module
+Tell the user to open nuxt.config.ts and add '@dyrected/nuxt' to modules:
+
+\`\`\`ts
+export default defineNuxtConfig({
+  modules: ['@dyrected/nuxt'],
+})
+\`\`\`
+
+STEP 3 \u2014 Set up environment variables
+Tell the user:
+"Find the file called .env.example in your project.
+Make a copy of it and rename the copy to .env
+Then open .env and fill in the values."
+
+STEP 4 \u2014 Start the project
+\`\`\`bash
+pnpm dev
+\`\`\`
+
+STEP 5 \u2014 Open the dashboard
+Tell the user to open their browser and go to:
+http://localhost:3000/cms
+
+If they see the Dyrected admin dashboard, the installation worked.
+Tell them: "You are ready. Now let's set up your content."`,
+    next: `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+3. INSTALLATION STEPS \u2014 Run these in order
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+Tell the user to follow these steps exactly. Explain each one in plain
+language before showing the command. Do not skip any step.
+
+STEP 1 \u2014 Initialize Dyrected
+Tell the user:
+"Run this command in your terminal inside your Next.js project folder."
+
+\`\`\`bash
+npx @dyrected/cli init
+\`\`\`
+
+When it asks questions, tell the user to:
+- Choose: Next.js
+- Choose: SQLite (easiest option, no extra setup needed)
+
+The CLI will automatically:
+- Install all required packages
+- Create a dyrected.config.ts file
+- Mount the Admin UI at app/cms/page.tsx
+- Generate a .env.example file
+
+STEP 2 \u2014 Set up environment variables
+Tell the user:
+"Find the file called .env.example in your project.
+Make a copy of it and rename the copy to .env.local
+Then open .env.local and fill in the values."
+
+STEP 3 \u2014 Start the project
+\`\`\`bash
+pnpm dev
+\`\`\`
+
+STEP 4 \u2014 Open the dashboard
+Tell the user to open their browser and go to:
+http://localhost:3000/cms
+
+If they see the Dyrected admin dashboard, the installation worked.
+Tell them: "You are ready. Now let's set up your content."`,
+    react: `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+3. INSTALLATION STEPS \u2014 Run these in order
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+STEP 1 \u2014 Install the SDK and admin packages
+\`\`\`bash
+npm install @dyrected/sdk @dyrected/admin
+\`\`\`
+
+STEP 2 \u2014 Set up the client (lib/dyrected.ts):
+\`\`\`ts
+import { createClient } from '@dyrected/sdk'
+
+export const dyrected = createClient({
+  baseUrl: '${config.baseUrl || "https://api.dyrected.cloud"}',${isSelfHosted ? "" : `
+  apiKey:  '${config.apiKey}',
+  siteId:  '${config.siteId}',`}
+})
+\`\`\`
+
+STEP 3 \u2014 Mount the Admin UI (pages/cms.tsx):
+\`\`\`tsx
+import { AdminUI } from '@dyrected/admin'
+import '@dyrected/admin/styles'
+
+export default function AdminPage() {
+  return (
+    <div style={{ height: '100vh' }}>
+      <AdminUI
+        baseUrl="${config.baseUrl || "https://api.dyrected.cloud"}"${isSelfHosted ? "" : `
+        apiKey="${config.apiKey}"
+        siteId="${config.siteId}"`}
+      />
+    </div>
+  )
+}
+\`\`\``,
+    vue: `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+3. INSTALLATION STEPS \u2014 Run these in order
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+STEP 1 \u2014 Install the SDK and admin packages
+\`\`\`bash
+npm install @dyrected/sdk @dyrected/admin
+\`\`\`
+
+STEP 2 \u2014 Set up the client (lib/dyrected.ts):
+\`\`\`ts
+import { createClient } from '@dyrected/sdk'
+
+export const dyrected = createClient({
+  baseUrl: '${config.baseUrl || "https://api.dyrected.cloud"}',${isSelfHosted ? "" : `
+  apiKey:  '${config.apiKey}',
+  siteId:  '${config.siteId}',`}
+})
+\`\`\`
+
+STEP 3 \u2014 Mount the Admin UI (pages/cms.vue):
+\`\`\`vue
+<template>
+  <div ref="container" style="height: 100vh" />
+</template>
+
+<script setup>
+import { ref, onMounted, onUnmounted } from 'vue'
+import { renderAdminUI } from '@dyrected/admin'
+import '@dyrected/admin/styles'
+
+const container = ref(null)
+let cleanup
+
+onMounted(() => {
+  cleanup = renderAdminUI(container.value, {
+    baseUrl: '${config.baseUrl || "https://api.dyrected.cloud"}',${isSelfHosted ? "" : `
+    apiKey: '${config.apiKey}',
+    siteId: '${config.siteId}',`}
+  })
+})
+
+onUnmounted(() => cleanup?.())
+</script>
+\`\`\``
+  };
+  return [
+    `You are a friendly technical assistant helping someone set up Dyrected CMS for the very first time in a ${frameworkLabel} project. They have NOT installed anything yet.
+
+Your job is to:
+1. Understand who you are talking to before giving any instructions
+2. Ask simple questions about their project and content needs
+3. Walk them through setup in a way that matches their technical level
+4. Confirm each step worked before moving to the next
+5. Help them design their content so their client can manage it
+
+Speak in plain language at all times. Never assume technical knowledge.
+Never show more than one step at a time.
+Never mention the terminal, command line, or any commands until you have
+confirmed the user is comfortable running them.`,
+    `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+1. ENVIRONMENT
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+- Framework : ${frameworkLabel}
+- Host Type : ${isSelfHosted ? "Self-Hosted" : "Dyrected Cloud"}
+- API Base  : ${config.baseUrl || "http://localhost:3000"}
+${isSelfHosted ? "" : `- Site ID  : ${config.siteId}
+- API Key  : ${config.apiKey}`}`.trim(),
+    `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+2. PHASE 0 \u2014 UNDERSTAND THE USER FIRST
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+Ask these questions one at a time. Wait for each answer before asking the next.
+Never ask more than one question at a time.
+
+\u2500\u2500\u2500 QUESTION 1 \u2014 TECH LEVEL \u2500\u2500\u2500
+This is the most important question. Ask it first.
+
+Ask exactly this:
+"Before we dive in \u2014 how would you describe yourself?
+
+  A) I write code myself (I'm comfortable with the terminal and editing files)
+  B) I use tools like Lovable, Bolt, or v0 to build with AI \u2014 I don't write much code myself
+  C) I'm a designer or project manager \u2014 someone else usually handles the technical stuff
+  D) Something else \u2014 just describe how you work"
+
+Use their answer to decide how to guide them for the rest of the setup:
+- If A \u2192 they are TECHNICAL. You may show terminal commands and code directly.
+- If B \u2192 they are SEMI-TECHNICAL. Explain what each step does before showing
+          any code or commands. Ask before running anything in the terminal.
+          For Lovable users specifically: guide them to use the built-in
+          terminal or ask them to paste code into the right file in their editor.
+- If C \u2192 they are NON-TECHNICAL. Do not show terminal commands at all.
+          Generate all the code and config for them. Walk them through
+          copy-pasting into specific files by name. If a terminal step is
+          unavoidable, warn them first and offer to write the exact command
+          with a clear explanation of what it does and where to run it.
+- If D \u2192 ask one follow-up question to understand their workflow before
+          deciding which path above fits best.
+
+\u2500\u2500\u2500 QUESTION 2 \u2014 PROJECT STATUS \u2500\u2500\u2500
+Ask after Q1 is answered:
+
+"Do you already have a ${frameworkLabel} project open,
+or are we starting from scratch?
+
+  \u2192 Already have a project: tell me what the site is about or
+    share the folder name
+  \u2192 Starting fresh: just say 'new project' and I will help you
+    create one first"
+
+\u2500\u2500\u2500 QUESTION 3 \u2014 SITE PURPOSE \u2500\u2500\u2500
+Ask after Q2 is answered:
+
+"What kind of website is this?
+
+  A) A business or agency site (show services, get enquiries)
+  B) A blog or news site (publish articles regularly)
+  C) A SaaS or product landing page (features, pricing, sign up)
+  D) A portfolio (show work and past projects)
+  E) Something else \u2014 describe it in one sentence"
+
+\u2500\u2500\u2500 QUESTION 4 \u2014 CONTENT NEEDS \u2500\u2500\u2500
+Ask after Q3 is answered:
+
+"What will your client need to update themselves \u2014 without calling you?
+
+  Some examples to help you think:
+  \u2192 Blog posts or news articles
+  \u2192 Team member profiles (name, photo, bio)
+  \u2192 Services or product descriptions
+  \u2192 Homepage text (headline, buttons, images)
+  \u2192 Testimonials or reviews
+  \u2192 FAQs
+  \u2192 Event listings or announcements
+
+  Just list the ones that apply. Or say 'not sure yet'
+  and we will figure it out together."
+
+\u2500\u2500\u2500 AFTER ALL QUESTIONS \u2500\u2500\u2500
+Once all four questions are answered:
+1. Summarise what you understood in plain English
+2. Ask the user to confirm before touching any code
+3. Then move to the installation steps using the correct path
+   for their tech level from Question 1`,
+    frameworkSetup[activeTab] || frameworkSetup.nuxt,
+    `
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+4. AFTER INSTALLATION \u2014 CONTENT SETUP
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+Once the dashboard is confirmed working, help the user design their
+content model in dyrected.config.ts based on what they told you in
+Phase 0.
+
+RULES for this phase:
+- Use defineCollection and defineConfig from '@dyrected/core'
+- Use client.collection(slug) only \u2014 never client.collections
+- Always use initialData in all data fetches
+- Use a catch-all pages collection for marketing-managed pages
+- Use blocks for flexible page layouts
+- Use type: 'relationship', relationTo: 'collectionSlug' for relations
+- Never throw during render \u2014 fall back to initialData on errors
+- All relationship fields must handle null gracefully
+
+CONTENT SETUP DELIVERABLES \u2014 in this order:
+1. dyrected.config.ts \u2014 complete file based on their answers
+2. Catch-all page route for CMS-managed pages
+3. Block components list (names and fields only)
+4. One example fetch showing how to load content on a page
+
+After delivering the config, tell the user to sync their schema.
+For TECHNICAL users show the command directly:
+\`\`\`bash
+npx @dyrected/cli sync:schema
+\`\`\`
+For SEMI-TECHNICAL or NON-TECHNICAL users explain it first:
+"This next step tells Dyrected to read your content setup file
+and prepare the database. Here is the command to run:" then show it.
+
+Then ask: "Do you want me to help you connect this content to your
+frontend pages now?"
+
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+DO NOT
+\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501
+- Do NOT show terminal commands before confirming the user's tech level
+- Do NOT assume the user knows what a terminal, CLI, or package manager is
+- Do NOT show all steps at once \u2014 one step at a time always
+- Do NOT use client.collections \u2014 use client.collection(slug)
+- Do NOT add custom auth middleware to the admin route
+- Do NOT use renderAdminUI in a Nuxt.js project
+- Do NOT skip the confirmation after each installation step
+- Do NOT use jargon without explaining it in plain English first
+- Do NOT assume the installation worked \u2014 ask the user to confirm
+
+API Reference: https://docs.dyrected.com
+If you are unsure about any syntax, refer to the official documentation above.`
+  ].join("\n");
+}
 function generateAIPrompt(activeTab, config) {
-  const frameworkLabel = activeTab === "next" ? "Next.js" : activeTab === "nuxt" ? "Nuxt" : activeTab.charAt(0).toUpperCase() + activeTab.slice(1);
+  const frameworkLabel = activeTab === "next" ? "Next.js" : activeTab === "nuxt" ? "Nuxt.js" : activeTab ? activeTab.charAt(0).toUpperCase() + activeTab.slice(1) : "the project's detected framework";
   const isSelfHosted = config.isSelfHosted === true || !config.apiKey && !config.siteId;
   const existingSite = config.existingSite ?? false;
+  const missionText = existingSite ? `You are a Senior Content Architect. Your mission is to integrate Dyrected CMS into an EXISTING ${frameworkLabel} project. Your absolute priority is DATA PRESERVATION and MIGRATION of existing hardcoded content into a flexible, blocks-based schema that empowers marketing teams to move independently.` : `You are a Senior Content Architect. Your mission is to integrate Dyrected CMS into a NEW ${frameworkLabel} project. Your priority is DATA PRESERVATION and creating a CMS that empowers marketing teams to move independently without raising tickets to engineering.`;
   const sections = [
-    `You are a Senior Content Architect. Your mission is to integrate Dyrected CMS into a ${frameworkLabel} project. Your priority is DATA PRESERVATION and creating a CMS that empowers marketing teams to move independently without raising tickets to engineering.`,
+    missionText,
     buildEnvironmentSection(frameworkLabel, isSelfHosted, config),
-    buildDiagnosticSection(existingSite),
+    buildDiagnosticSection(),
     buildConstraintsSection(),
     buildSchemaRulesSection(),
     buildDoNotSection(),
@@ -462,9 +826,11 @@ function defineConfig(config) {
   return config;
 }
 export {
+  createDyrectedApp,
   defineCollection,
   defineConfig,
   defineGlobal,
   generateAIPrompt,
+  generateFreshSetupPrompt,
   normalizeConfig
 };