cabloy 5.1.51 → 5.1.52

package/.claude/skills/cabloy-contract-loop/SKILL.md

@@ -139,7 +139,7 @@ Typical examples in Cabloy Basic include:
 - `cd zova && npm run build:rest:cabloyBasicAdmin`
 - `cd zova && npm run build:rest:cabloyBasicWeb`
 
-For Cabloy Start, verify the exact Start-specific flavor names and paths in the Start repo.
+For Cabloy Start, verify the exact Start-specific flavor names, paths, SSR site baselines, and project assets in the licensed Start repo.
 
 ### Path C: Downstream frontend alignment
 

package/.claude/skills/cabloy-frontend-scaffold/SKILL.md

@@ -154,7 +154,7 @@ Check whether the feature needs:
 - build
 - metadata regeneration verification
 - SSR or route-path verification
-- edition-specific flavor verification
+- edition-specific flavor, SSR site baseline, and project-asset verification
 
 ### Optional backend-contract reminder
 

package/.claude/skills/cabloy-workflow/SKILL.md

@@ -28,7 +28,7 @@ Interpretation:
 - `__CABLOY_START__` present → this is Cabloy Start
 - neither present → inspect the repo scripts and ask the user before making a strong edition-specific assumption
 
-This matters most for frontend work, UI-library assumptions, flavor names, and edition-specific modules.
+This matters most for frontend work, UI-layer assumptions, flavor names, suite/module availability, SSR site baselines, project assets, and edition-specific AI guidance.
 
 ## Step 2: Identify the task layer
 
@@ -61,7 +61,7 @@ Use the frontend path when the task is about:
 
 - page, component, mock, bean
 - SSR, Web, Admin, SPA
-- UI-library-sensitive work
+- UI-layer-sensitive work
 - OpenAPI SDK generation
 - frontend refactors such as page params, page query, component props, or model helpers
 
@@ -236,19 +236,23 @@ When the task is frontend-sensitive or examples differ between editions, branch
 
 Bias toward:
 
+- the public framework/reference edition
 - current public monorepo source
+- the default `npm create cabloy` project route
 - public docs examples
 - the Basic repo marker
-- current Basic frontend flavors and module layout
+- current Basic frontend flavors, module layout, and DaisyUI + Tailwind CSS UI assumptions
 
 ### Cabloy Start
 
 Bias toward:
 
+- the private commercial edition
 - the Start repo marker
+- the licensed private repository source
 - Vuetify-sensitive examples
 - Start-specific frontend flavor names
-- Start-specific modules and private-value repo structure
+- Start-specific suites/modules, SSR site baselines, project assets, and licensed private-repo structure
 
 Do not silently reuse Basic examples when Start-specific assumptions matter.
 

package/.claude/skills/cabloy-workflow/references/edition-detection.md

@@ -13,10 +13,11 @@ They prevent the most common category error in Cabloy AI work: assuming Cabloy B
 
 That assumption is especially dangerous for:
 
-- UI-library-sensitive examples
+- UI-layer-sensitive examples
 - frontend flavor names
 - page/component workflows
-- module availability
+- suite/module availability
+- SSR site baselines and project assets
 - docs and skills that try to support both repos
 
 ## Secondary checks

package/.github/workflows/docs-pages.yml

@@ -34,6 +34,8 @@ jobs:
       - name: install docs dependencies
         run: pnpm --dir cabloy-docs install --frozen-lockfile
       - name: build docs
+        env:
+          GA_MEASUREMENT_ID: ${{ vars.GA_MEASUREMENT_ID }}
         run: pnpm --dir cabloy-docs docs:build
       - name: setup pages
         uses: actions/configure-pages@v5

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 5.1.52
+
+### Features
+
+- Add SSR memory diagnostic endpoints.
+- Expand framework capabilities across SSR, controller, module, component, utility, and runtime integration areas.
+- Add virtual decorator guidance to the AI documentation.
+
+### Bug Fixes
+
+- Correct runtime home paths in the documentation.
+- Fix homepage scope badge layout in the documentation.
+
+### Improvements
+
+- Refine SSR internals and metadata handling.
+- Polish controller and page base implementation details.
+- Update monkey patching and runtime support code.
+- Improve package metadata and lockfile consistency.
+- Pass the GA measurement ID into the docs build pipeline.
+- Add GA4 tracking support for the documentation site.
+- Improve CLI, index, glossary, skill, and README documentation.
+- Add and refine the Cabloy framework comparison and fullstack introduction content.
+- Polish branding, wording, and AI vibe coding terminology across the docs.
+
 ## 5.1.51
 
 ### Features

package/CLAUDE.md

@@ -2,15 +2,15 @@
 
 ## Repository identity
 
-This repository is **Cabloy Basic**, identified by the root marker file:
+This repository is **Cabloy Basic**, the public framework/reference edition, identified by the root marker file:
 
 - `__CABLOY_BASIC__`
 
-A sibling repository named `cabloy-start` is a separate source repository and is identified by:
+A sibling repository named `cabloy-start` is the private commercial edition, delivered as a licensed separate source repository and identified by:
 
 - `__CABLOY_START__`
 
-Always detect the active edition before making UI-sensitive assumptions, choosing frontend examples, or recommending module-specific workflows.
+Always detect the active edition before making UI-sensitive assumptions, choosing frontend examples, recommending module-specific workflows, or assuming the project creation path.
 
 ## Monorepo layout
 
@@ -43,7 +43,7 @@ Before inventing a custom implementation path:
 
 - Prefer CLI-backed workflows over manual scaffolding whenever Vona or Zova already provides a generator, refactor, metadata, or verification command.
 - Treat legacy docs as input material, not as unquestioned truth. When docs conflict with source code, prefer current source code.
-- For frontend work, assume Cabloy Basic and Cabloy Start may diverge in UI library, frontend flavors, module availability, and generated outputs.
+- For frontend work, assume Cabloy Basic and Cabloy Start share a frontend engineering layer but may diverge in UI layer, frontend flavors, suite/module availability, SSR site baselines, project assets, and generated outputs.
 - Reuse existing repo terminology: Cabloy, Vona, Zova, suite, module, bean, SSR, SPA, Web, Admin.
 - For backend base-class placement, use the A / B1 / B2 rule from `cabloy-docs/ai/class-placement-rule.md`.
 - Pure helper bases belong in `src/lib`; subclass-only bases should be evaluated case by case and often belong in `src/lib`.

package/README.md

@@ -3,16 +3,16 @@
 [![License MIT](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/cabloy/cabloy/blob/main/LICENSE)
 [![npm version](https://img.shields.io/npm/v/cabloy.svg?style=flat-square&label=cabloy)](https://www.npmjs.com/package/cabloy)
 [![npm downloads](https://img.shields.io/npm/dm/cabloy?color=orange&label=downloads)](https://www.npmjs.com/package/cabloy)
-[![Docs](https://img.shields.io/badge/docs-cabloy-4f46e5.svg?style=flat-square)](https://github.com/cabloy/cabloy/tree/main/cabloy-docs)
+[![Docs](https://img.shields.io/badge/docs-cabloy-4f46e5.svg?style=flat-square)](https://docs.cabloy.com)
 [![Demo](https://img.shields.io/badge/demo-cabloy.com-059669.svg?style=flat-square)](https://cabloy.com)
 
 Cabloy is a Node.js fullstack framework for AI vibe coding.
 
-Use one framework system instead of stitching together separate backend and frontend stacks.
+Use one fullstack framework instead of stitching together separate backend and frontend stacks.
 
-With **Vona** on the backend, **Zova** on the frontend, and CLI-first workflows across the stack, Cabloy turns common scaffolding and verification into explicit commands so AI coding can stay more accurate, use fewer tokens, and move faster.
+With Vona, Zova, suite-based modules, and CLI-first workflows, Cabloy turns common scaffolding, metadata, refactors, and verification into explicit commands for faster, more accurate AI vibe coding.
 
-[Documentation](https://github.com/cabloy/cabloy/tree/main/cabloy-docs) · [npm](https://www.npmjs.com/package/cabloy) · [Web Demo](https://cabloy.com) · [Admin Demo](https://cabloy.com/admin) · [GitHub](https://github.com/cabloy/cabloy)
+[Documentation](https://docs.cabloy.com) · [npm](https://www.npmjs.com/package/cabloy) · [Web Demo](https://cabloy.com) · [Admin Demo](https://cabloy.com/admin) · [GitHub](https://github.com/cabloy/cabloy)
 
 ## Get Started
 
@@ -38,16 +38,19 @@ Create a new Cabloy project:
 npm create cabloy
 ```
 
-The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. Open this project in Claude Code and start coding immediately with project-specific guidance.
+The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. This path creates a Cabloy Basic project baseline. Open this project in Claude Code and start coding immediately with project-specific guidance.
+
+For **Cabloy Start**, purchase access to the licensed private repository, clone `git@github.com:cabloy/cabloy-start.git`, and run `npm run init`. For the complete Start onboarding flow, read the [Cabloy Start](https://docs.cabloy.com/editions/cabloy-start) page.
 
 Then continue with the framework docs:
 
-- [Fullstack Quickstart](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/fullstack/quickstart.md)
-- [Documentation](https://github.com/cabloy/cabloy/tree/main/cabloy-docs)
-- [Fullstack Introduction](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/fullstack/introduction.md)
-- [Backend Introduction](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/backend/introduction.md)
-- [Frontend Introduction](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/frontend/introduction.md)
-- [Editions Overview](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/editions/overview.md)
+- [Fullstack Quickstart](https://docs.cabloy.com/fullstack/quickstart)
+- [Documentation](https://docs.cabloy.com)
+- [Fullstack Introduction](https://docs.cabloy.com/fullstack/introduction)
+- [Backend Introduction](https://docs.cabloy.com/backend/introduction)
+- [Frontend Introduction](https://docs.cabloy.com/frontend/introduction)
+- [Editions Overview](https://docs.cabloy.com/editions/overview)
+- [Choosing Between Cabloy Basic and Cabloy Start](https://docs.cabloy.com/editions/choosing-between-basic-and-start)
 
 To upgrade an existing Cabloy project:
 
@@ -57,11 +60,12 @@ npm run upgrade
 
 ## Highlights
 
-- **One framework system** — build backend and frontend in one Node.js fullstack architecture
-- **Vona + Zova** — use aligned backend and frontend frameworks instead of stitching together separate stacks
-- **Multiple delivery modes** — support SSR, SPA, Web, and Admin applications with shared conventions
-- **CLI-first workflows for AI coding** — turn scaffolding, metadata, refactors, and verification into explicit commands so AI can stay more accurate, use fewer tokens, and move faster
-- **Monorepo-native development** — keep framework source, docs, and tooling aligned in one repository model
+- **One framework system** — build backend and frontend in one fullstack architecture
+- **Vona + Zova** — use aligned backend and frontend frameworks for code sharing, workflow reuse, and cross-stack consistency
+- **Suite-based modular system** — organize capabilities as suites and modules so services, features, metadata, and tooling evolve in composable units
+- **Multiple delivery modes** — deliver SSR, SPA, Web, and Admin applications with shared conventions across the stack
+- **CLI-first workflows for AI vibe coding** — turn common scaffolding, metadata, refactors, and verification into explicit commands for faster, more accurate AI vibe coding
+- **Monorepo-native development** — keep framework source, docs, and tooling aligned in one monorepo workflow
 
 ## Technology Stack
 
@@ -92,7 +96,16 @@ npm run upgrade
 | TanStack Form  | `^1.32.0`   |
 | TanStack Table | `^8.21.3`   |
 
-### Edition-specific UI Stack
+### Shared Frontend Engineering Layer
+
+- Vue
+- Vite
+- Quasar tooling such as `quasar dev` and `quasar build`
+- TanStack libraries where applicable
+
+Quasar is used here for engineering tooling rather than as the edition UI component library.
+
+### Edition-specific UI Layer
 
 - **Cabloy Basic**: DaisyUI + Tailwind CSS
 - **Cabloy Start**: Vuetify
@@ -113,14 +126,16 @@ npm run build
 
 For more details, see:
 
-- [Repo Scripts](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/reference/repo-scripts.md)
-- [Package Map](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/reference/package-map.md)
-- [AI Development Introduction](https://github.com/cabloy/cabloy/blob/main/cabloy-docs/ai/introduction.md)
+- [Editions Overview](https://docs.cabloy.com/editions/overview)
+- [Choosing Between Cabloy Basic and Cabloy Start](https://docs.cabloy.com/editions/choosing-between-basic-and-start)
+- [Repo Scripts](https://docs.cabloy.com/reference/repo-scripts)
+- [Package Map](https://docs.cabloy.com/reference/package-map)
+- [AI Development Introduction](https://docs.cabloy.com/ai/introduction)
 
 Contribution guidelines:
 
 - prefer CLI-backed workflows with `npm run vona` and `npm run zova`
-- put user-facing and agent-facing guidance in [cabloy-docs/](https://github.com/cabloy/cabloy/tree/main/cabloy-docs)
+- put user-facing and agent-facing guidance in [docs.cabloy.com](https://docs.cabloy.com)
 - put maintainer rationale, architecture notes, and ADRs in [.docs-internal/](https://github.com/cabloy/cabloy/tree/main/.docs-internal)
 - verify framework changes with the narrowest meaningful checks first, then shared root scripts when broader confidence is needed
 

package/cabloy-docs/.vitepress/config.mjs

@@ -2,6 +2,10 @@ import { defineConfig } from 'vitepress';
 
 const editionsItems = [
   { text: 'Overview', link: '/editions/overview' },
+  {
+    text: 'Choosing Basic vs Start',
+    link: '/editions/choosing-between-basic-and-start',
+  },
   { text: 'Cabloy Basic', link: '/editions/cabloy-basic' },
   { text: 'Cabloy Start', link: '/editions/cabloy-start' },
   { text: 'Edition Detection', link: '/editions/detection' },
@@ -23,6 +27,7 @@ const aiItems = [
   { text: 'CLI for Agents', link: '/ai/cli-for-agents' },
   { text: 'Rules and Config', link: '/ai/rules-and-config' },
   { text: 'Edition Detection', link: '/ai/edition-detection' },
+  { text: 'Edition Consistency Checklist', link: '/ai/edition-consistency-checklist' },
   { text: 'Verification', link: '/ai/verification' },
 ];
 
@@ -34,12 +39,34 @@ const referenceItems = [
   { text: 'Glossary', link: '/reference/glossary' },
 ];
 
+const GA_MEASUREMENT_ID = process.env.GA_MEASUREMENT_ID;
+const gaHead = GA_MEASUREMENT_ID
+  ? [
+      [
+        'script',
+        {
+          async: '',
+          src: `https://www.googletagmanager.com/gtag/js?id=${GA_MEASUREMENT_ID}`,
+        },
+      ],
+      [
+        'script',
+        {},
+        `window.dataLayer = window.dataLayer || [];
+function gtag(){dataLayer.push(arguments);}
+gtag('js', new Date());
+gtag('config', '${GA_MEASUREMENT_ID}');`,
+      ],
+    ]
+  : [];
+
 export default defineConfig({
   title: 'Cabloy',
   description: 'Unified fullstack and AI-development documentation for the Cabloy monorepo',
   lang: 'en-US',
   base: '/',
   ignoreDeadLinks: [/^https?:\/\/localhost/],
+  head: gaHead,
   markdown: {
     lineNumbers: true,
   },
@@ -59,7 +86,13 @@ export default defineConfig({
           text: 'Fullstack',
           items: [
             { text: 'Introduction', link: '/fullstack/introduction' },
+            {
+              text: 'Comparison with Other Frameworks',
+              link: '/fullstack/comparison-with-other-frameworks',
+            },
             { text: 'Quickstart', link: '/fullstack/quickstart' },
+            { text: 'CLI', link: '/fullstack/cli' },
+            { text: 'VS Code Extensions', link: '/fullstack/vscode-extensions' },
             { text: 'Vona + Zova Integration', link: '/fullstack/vona-zova-integration' },
             { text: 'Backend OpenAPI to Frontend SDK', link: '/fullstack/openapi-to-sdk' },
             {

package/cabloy-docs/ai/class-placement-rule.md

@@ -135,4 +135,5 @@ Read these pages together:
 - [Backend Foundation](/backend/foundation)
 - [Service Guide](/backend/service-guide)
 - [Global Bean Lookup](/ai/global-bean-lookup)
+- [Virtual Decorator Guidance](/ai/virtual-decorator-guidance)
 - [Docs, Skills, Rules, and CLI Mapping](/ai/docs-skills-rules-mapping)

package/cabloy-docs/ai/cli-for-agents.md

@@ -53,4 +53,4 @@ Typical use cases:
 
 ## Edition-aware CLI usage
 
-The command families are shared, but examples and generated targets may differ between Cabloy Basic and Cabloy Start. Detect the edition before recommending a frontend-specific example.
+The command families are shared, but examples and generated targets may differ between Cabloy Basic and Cabloy Start because the editions can diverge in UI layer, frontend flavors, suites/modules, SSR site baselines, and project assets. Detect the edition before recommending a frontend-specific example.

package/cabloy-docs/ai/docs-skills-rules-mapping.md

@@ -115,6 +115,7 @@ Use this quick rule:
 ### Example: “Always detect Basic vs Start before giving UI-sensitive advice”
 
 - public explanation → [AI Edition Detection](/ai/edition-detection)
+- consistency review surface → [Edition Consistency Checklist](/ai/edition-consistency-checklist)
 - repo-wide behavior rule → `CLAUDE.md`
 - procedural enforcement → `cabloy-workflow` skill
 

package/cabloy-docs/ai/edition-consistency-checklist.md

@@ -0,0 +1,150 @@
+# Edition Consistency Checklist
+
+This checklist helps maintainers keep docs, rules, commands, and skills aligned when writing or reviewing Cabloy Basic and Cabloy Start guidance.
+
+Use it whenever you add or revise:
+
+- edition-aware docs
+- `CLAUDE.md` guidance
+- `.claude/commands/`
+- `.claude/skills/`
+- AI workflow playbooks
+
+## The baseline story that should stay consistent
+
+Before checking details, confirm that the content still tells the same baseline story:
+
+- **Cabloy Basic** is the public framework/reference edition
+- `npm create cabloy` creates the default Cabloy Basic project route
+- **Cabloy Start** is the private commercial edition
+- Cabloy Start is used by cloning the licensed private repository source directly
+- both editions share the same Cabloy fullstack core
+- both editions share a frontend engineering layer built around Zova, Vue, Vite, Quasar tooling, and related libraries
+- the editions diverge in UI layer, frontend flavors, suites/modules, SSR site baselines, project assets, and some generated outputs
+
+If a page, rule, or skill contradicts one of those points, align that content before polishing wording.
+
+## Checklist 1: edition detection is explicit
+
+Confirm that the content:
+
+- tells the reader or agent to check `__CABLOY_BASIC__` or `__CABLOY_START__`
+- treats edition detection as mandatory before UI-sensitive guidance
+- does not assume Cabloy Basic examples apply to Cabloy Start automatically
+- does not assume the project creation path is the same for both editions
+
+## Checklist 2: creation path assumptions are correct
+
+Confirm that the content states or implies the right project-entry model:
+
+- **Cabloy Basic** → `npm create cabloy`
+- **Cabloy Start** → licensed private repository clone
+
+Watch for drift such as:
+
+- implying that Cabloy Start is created through `npm create cabloy`
+- implying that both editions use the same bootstrap path
+- omitting the Start licensing/private-repo model when it matters to the workflow
+
+## Checklist 3: shared core vs edition divergence is separated cleanly
+
+Confirm that the content distinguishes:
+
+### Shared core
+
+- Vona
+- Zova
+- suite-based architecture
+- CLI-first workflows
+- shared frontend engineering direction
+
+### Edition divergence
+
+- UI layer
+- frontend flavors
+- suites/modules
+- SSR site baselines
+- project assets
+- edition-specific generated outputs or script paths where applicable
+
+Avoid collapsing the whole difference into “different UI library only.”
+
+## Checklist 4: UI language uses the right layer
+
+When the content talks about frontend differences, confirm that it uses the right level:
+
+- shared frontend engineering layer
+- edition-specific UI layer
+
+Prefer wording such as:
+
+- **Cabloy Basic**: DaisyUI + Tailwind CSS UI layer
+- **Cabloy Start**: Vuetify UI layer
+
+Avoid wording that makes Quasar sound like the edition UI component library when the intended meaning is tooling.
+
+## Checklist 5: operational examples match the active edition
+
+For scripts, flavors, paths, and examples, confirm that:
+
+- Basic examples use Basic markers and Basic flavor names
+- Start examples tell the reader to verify the Start repo directly
+- Start workflows do not silently reuse Basic script or flavor assumptions
+- SSR site baseline assumptions match the edition being discussed
+- project-asset references match the repo being discussed
+
+## Checklist 6: docs, rules, and skills play different roles
+
+Confirm that the same guidance is distributed correctly:
+
+- **docs** explain the workflow in durable prose
+- **`CLAUDE.md`** captures short repo-wide behavioral rules
+- **skills** encode procedural branching and follow-up logic
+- **commands** are used only for named operator workflows, not as the only home for conceptual guidance
+
+Avoid these drifts:
+
+- a skill contains the only explanation of an edition rule
+- `CLAUDE.md` grows into a long architectural essay
+- docs duplicate every procedural branch that belongs in a skill
+
+## Checklist 7: verification guidance matches the edition model
+
+When content ends with verification steps, confirm that it reminds the reader or agent to verify the right edition-specific surfaces when relevant:
+
+- flavor names
+- script paths
+- suites/modules
+- SSR site baselines
+- generated outputs
+- project assets
+
+For Start-sensitive workflows, confirm that verification points back to the licensed Start repository rather than pretending the current Basic repo is the direct source of truth.
+
+## Checklist 8: wording about system size stays appropriately scoped
+
+If the content talks about project fit, confirm that it keeps the intended nuance:
+
+- **Cabloy Basic** is optimized for public reference, learning, community workflows, and faster small-to-medium system development
+- **Cabloy Start** is optimized as a stronger baseline for more complex business systems
+
+Avoid overstating this into a hard claim that Basic cannot support larger systems.
+
+## Quick review questions
+
+Before you finish an edition-aware change, ask:
+
+1. Did I clearly separate shared core from edition-specific divergence?
+2. Did I preserve the correct Basic vs Start creation path?
+3. Did I avoid turning UI difference into the whole story?
+4. Did I point Start-specific operational truth back to the licensed Start repo where needed?
+5. Do docs, rules, and skills each play their proper role?
+
+## Read together with
+
+- [Choosing Between Cabloy Basic and Cabloy Start](/editions/choosing-between-basic-and-start)
+- [Editions Overview](/editions/overview)
+- [Edition Detection for AI Workflows](/ai/edition-detection)
+- [Docs, Skills, Rules, and CLI Mapping](/ai/docs-skills-rules-mapping)
+- [Rules and Config](/ai/rules-and-config)
+- [Verification](/ai/verification)

package/cabloy-docs/ai/edition-detection.md

@@ -8,10 +8,10 @@ Edition detection should happen before any AI workflow that assumes a frontend s
 
 If an agent skips edition detection, it can:
 
-- scaffold against the wrong UI assumptions
+- scaffold against the wrong UI-layer assumptions
 - suggest the wrong frontend flavors
-- cite modules that do not exist in the active repo
-- generate docs or skills that accidentally hardcode Basic-only behavior into Start workflows
+- cite suites, modules, SSR site baselines, or project assets that do not exist in the active repo
+- generate docs or skills that accidentally hardcode Basic-only behavior or `npm create cabloy` assumptions into Start workflows
 
 ## Operational rule
 

package/cabloy-docs/ai/global-bean-lookup.md

@@ -152,6 +152,7 @@ Avoid these mistakes:
 Read these pages together:
 
 - [Class Placement Rule](/ai/class-placement-rule)
+- [Virtual Decorator Guidance](/ai/virtual-decorator-guidance)
 - [Repo Guidance](/ai/repo-guidance)
 - [Rules and Config](/ai/rules-and-config)
 - [Verification](/ai/verification)

package/cabloy-docs/ai/introduction.md

@@ -1,8 +1,8 @@
 # AI Development Introduction
 
-This page is the entrypoint for contributors who are designing, reviewing, or maintaining AI-assisted workflows in the Cabloy repository.
+This page is the entrypoint for contributors who are designing, reviewing, or maintaining AI vibe coding workflows in the Cabloy repository.
 
-The Cabloy monorepo is a good fit for AI-assisted development because the source tree already contains most of the framework knowledge an agent needs:
+The Cabloy monorepo is a good fit for AI vibe coding because the source tree already contains most of the framework knowledge an agent needs:
 
 - root scripts for shared workflows
 - Vona CLI source and command groups
@@ -29,7 +29,7 @@ The goal is to make AI **reuse the repo’s existing conventions directly**, esp
 
 Use `cabloy-docs/` for user-facing and agent-facing guidance that should remain durable and source-aligned.
 
-For normal project usage, prefer the user-facing entry docs such as [Fullstack Quickstart](/fullstack/quickstart). This AI section focuses on repository workflows and AI-assisted development.
+For normal project usage, prefer the user-facing entry docs such as [Fullstack Quickstart](/fullstack/quickstart). This AI section focuses on repository workflows and AI vibe coding.
 
 ### Internal engineering docs
 

package/cabloy-docs/ai/repo-guidance.md

@@ -38,9 +38,9 @@ Edition detection is especially important when the work touches:
 
 - page creation
 - component generation
-- UI library usage
+- UI-layer usage
 - frontend flavor scripts
-- edition-specific modules or assets
+- edition-specific suites, modules, SSR site baselines, or project assets
 
 ## 5. Use the right lookup surface before searching broadly
 

package/cabloy-docs/ai/rules-and-config.md

@@ -10,7 +10,7 @@ Use the root `CLAUDE.md` for concise, durable operational guidance such as:
 - where public docs live
 - where internal docs live
 - which command entrypoints are preferred
-- why edition detection is mandatory before UI-sensitive guidance
+- why edition detection is mandatory before UI-sensitive guidance or project-creation assumptions
 
 ## `.claude/commands/`
 

package/cabloy-docs/ai/skills.md

@@ -33,3 +33,5 @@ A strong Cabloy skill usually includes:
 5. references to durable source-of-truth files
 
 When a skill needs to apply an architectural rule such as backend class placement, prefer a branching decision tree that points back to durable docs instead of embedding the full architecture rationale inside the skill itself.
+
+For edition-aware skills, use [Edition Detection for AI Workflows](/ai/edition-detection) and [Edition Consistency Checklist](/ai/edition-consistency-checklist) as the durable review surfaces before expanding edition-specific branches.

package/cabloy-docs/ai/verification.md

@@ -18,6 +18,7 @@ For skills and repo guidance:
 - confirm the workflow still points to real command entrypoints
 - confirm edition branches match the active repo markers and scripts
 - confirm public docs, skills, and root `CLAUDE.md` tell the same story
+- review edition-aware changes against [Edition Consistency Checklist](/ai/edition-consistency-checklist)
 
 ## Code-generation verification