cabloy 5.1.161 → 5.1.162

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

@@ -1,30 +0,0 @@
-# Edition Detection for AI Workflows
-
-This page applies the general detection rule from [Editions / Detection](/editions/detection) to AI-assisted development specifically.
-
-Edition detection should happen before any AI workflow that assumes a frontend stack, module set, or example path.
-
-## AI-specific consequence
-
-If an agent skips edition detection, it can:
-
-- scaffold against the wrong UI-layer assumptions
-- suggest the wrong frontend flavors
-- 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
-
-Before an AI workflow recommends implementation steps:
-
-1. check the edition marker
-2. verify the relevant package scripts or CLI entrypoints
-3. branch the guidance only where the editions truly diverge
-
-## Where this rule should live
-
-Keep the same rule in three places on purpose:
-
-- **public docs** so people can review it
-- **skills** so agents execute it consistently
-- **`CLAUDE.md`** so repo-wide Claude behavior stays aligned

package/repo-docs/editions/cabloy-basic.md

@@ -1,26 +0,0 @@
-# Cabloy Basic
-
-Cabloy Basic is the public framework/reference edition you are reading right now.
-
-## Repository marker
-
-The repository root contains:
-
-- `__CABLOY_BASIC__`
-
-This marker is the quickest safe signal for docs, skills, and rules that need to distinguish Cabloy Basic from Cabloy Start.
-
-## Typical role
-
-Use Cabloy Basic as the public reference edition for:
-
-- shared architecture explanations
-- root scripts and monorepo entrypoints
-- Vona and Zova source browsing
-- public CLI-backed workflows
-- public user-facing documentation
-- projects created with `npm create cabloy`
-
-## Frontend bias
-
-In the current source and docs, Cabloy Basic examples commonly align with a shared frontend engineering layer built on Zova, Vue, Vite, and Quasar tooling, plus a Basic-specific UI layer built with DaisyUI + Tailwind CSS. That does not mean Zova is limited to that UI stack, but it does mean docs and AI outputs should not accidentally project Vuetify-specific assumptions into Cabloy Basic unless the current source explicitly requires it.

package/repo-docs/editions/cabloy-start.md

@@ -1,53 +0,0 @@
-# Cabloy Start
-
-Cabloy Start is the public MIT-licensed edition. It is a sibling repository that shares the Cabloy fullstack direction while intentionally differing from Cabloy Basic.
-
-## Repository marker
-
-The Cabloy Start root contains:
-
-- `__CABLOY_START__`
-
-Use that marker before choosing examples, UI assumptions, or automation behavior.
-
-## Typical role
-
-Use Cabloy Start as the edition-aware target when work depends on:
-
-- direct use of the public Cabloy Start repository source
-- Vuetify-specific frontend workflows
-- Cabloy Start flavor names in frontend scripts
-- edition-specific module composition in the active Start repository
-- separate-repository structure and edition-specific project composition
-- edition-specific SSR site baselines and project assets
-
-## Clone and initialize
-
-Cabloy Start is public and MIT-licensed. It does not use the default `npm create cabloy` project route.
-
-To use Cabloy Start:
-
-1. clone the public repository directly
-2. run the edition initialization flow in the cloned project
-
-Repository:
-
-- `https://github.com/cabloy/cabloy-start`
-
-Clone the repository:
-
-```bash
-git clone git@github.com:cabloy/cabloy-start.git
-```
-
-After cloning, run:
-
-```bash
-npm run init
-```
-
-This initializes the project and installs dependencies.
-
-## Relationship to this docs site
-
-This unified docs site treats Cabloy Start as a supported edition, not as a clone of Cabloy Basic. Shared architecture should remain shared, but any Start-specific script, module path, or UI workflow must be labeled explicitly.

package/repo-docs/editions/choosing-between-basic-and-start.md

@@ -1,83 +0,0 @@
-# Choosing Between Cabloy Basic and Cabloy Start
-
-This guide helps you choose the right Cabloy edition before you start a new project, adopt a frontend UI strategy, or prepare AI workflow guidance.
-
-## Short answer
-
-Choose **Cabloy Basic** when you want the public framework/reference edition, the default `npm create cabloy` project route, and a faster path for open, community-oriented, or small-to-medium system development.
-
-Choose **Cabloy Start** when you want the public MIT-licensed edition in its own repository and a stronger baseline for more complex business systems built around Start-oriented SSR sites, project assets, and a Vuetify-aligned UI layer.
-
-## What stays the same in both editions
-
-Both editions share the same Cabloy fullstack core:
-
-- **Vona** as the backend framework
-- **Zova** as the frontend framework
-- suite-based modular architecture
-- CLI-first workflows
-- shared frontend engineering direction built around Vue, Vite, Quasar tooling, and related libraries
-
-So the decision is not about choosing two unrelated products. It is about choosing the edition baseline that fits your delivery goals best.
-
-## Choose Cabloy Basic when
-
-Cabloy Basic is usually the better fit when you want:
-
-- the public framework/reference edition
-- the default project route created by `npm create cabloy`
-- open-source visibility and community-friendly workflows
-- public examples and docs that match your repo directly
-- a UI layer aligned with DaisyUI + Tailwind CSS
-- a faster path for small-to-medium system development
-
-## Choose Cabloy Start when
-
-Cabloy Start is usually the better fit when you want:
-
-- the public MIT-licensed edition maintained in its own repository
-- direct cloning of the public Start repository
-- Start-specific flavors, SSR site baselines, and project assets
-- a UI layer aligned with Vuetify
-- a stronger starting point for more complex business systems
-- edition-specific rules, skills, and docs optimized for the Start repo assumptions
-
-## The most practical decision factors
-
-### Project creation path
-
-- **Cabloy Basic**: create the project with `npm create cabloy`
-- **Cabloy Start**: clone the public repository directly, then run `npm run init`
-
-### UI strategy
-
-- **Cabloy Basic**: DaisyUI + Tailwind CSS
-- **Cabloy Start**: Vuetify
-
-### Repo and asset model
-
-- **Cabloy Basic**: public repository and public reference materials
-- **Cabloy Start**: separate public repository with edition-specific SSR sites and project assets
-
-### AI workflow assumptions
-
-- **Cabloy Basic**: use Basic-specific examples, flavors, modules, and UI assumptions
-- **Cabloy Start**: use Start-specific examples, flavors, SSR site baselines, and UI assumptions
-
-This is why edition detection matters so much for AI vibe coding.
-
-## A simple recommendation rule
-
-Use this rule when you need a fast decision:
-
-1. If you want the public, default, `npm create cabloy` path, choose **Cabloy Basic**.
-2. If you want the public MIT-licensed Start repository with Start-oriented assets, a Vuetify-based business-system baseline, and a clone-plus-`npm run init` onboarding path, choose **Cabloy Start**.
-3. If AI workflow accuracy matters for UI generation, SSR site assumptions, or flavor-specific commands, confirm the edition before writing prompts, rules, skills, or docs.
-
-## Read together with
-
-- [Editions Overview](/editions/overview)
-- [Cabloy Basic](/editions/cabloy-basic)
-- [Cabloy Start](/editions/cabloy-start)
-- [Edition Detection](/editions/detection)
-- [Fullstack Quickstart](/fullstack/quickstart)

package/repo-docs/editions/detection.md

@@ -1,31 +0,0 @@
-# Edition Detection
-
-Edition detection is a first-class requirement for documentation, rules, and skills.
-
-## Repository markers
-
-Use these root markers:
-
-- `__CABLOY_BASIC__` → Cabloy Basic
-- `__CABLOY_START__` → Cabloy Start
-
-## Why this matters
-
-The two editions share many concepts but differ in important operational details, especially around:
-
-- frontend UI library assumptions
-- flavor-specific frontend scripts
-- module availability
-- Start-specific value-add project content
-
-If an agent skips edition detection, it may generate the wrong instructions, recommend the wrong module, or use the wrong UI stack.
-
-## Recommended rule for skills and repo guidance
-
-Before suggesting a cross-stack implementation path:
-
-1. check the repository marker
-2. verify the relevant root scripts or package scripts
-3. only then choose the edition-specific example or workflow branch
-
-When neither marker is present, fall back to code inspection and ask the user before making a strong edition-specific assumption.