@lenne.tech/cli 1.11.0 → 1.11.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/docs/LT-ECOSYSTEM-GUIDE.md +378 -379
  2. package/docs/VENDOR-MODE-WORKFLOW.md +150 -150
  3. package/package.json +1 -1
package/docs/LT-ECOSYSTEM-GUIDE.md CHANGED
@@ -1,81 +1,81 @@
1
- # lenne.tech Fullstack-Ecosystem: CLI & lt-dev Plugin
1
+ # lenne.tech Fullstack Ecosystem: CLI & lt-dev Plugin
2
2
 
3
- Umfassender Leitfaden für `lt CLI` und das `lt-dev` Claude-Code-Plugin mit Fokus auf **Vendor-Mode-Workflows** für `@lenne.tech/nest-server` und `@lenne.tech/nuxt-extensions`.
3
+ Comprehensive reference for the `lt` CLI and the `lt-dev` Claude Code plugin, with focus on **vendor-mode workflows** for `@lenne.tech/nest-server` and `@lenne.tech/nuxt-extensions`.
4
4
 
5
5
  ---
6
6
 
7
- ## Inhaltsverzeichnis
8
-
9
- - [Überblick](#überblick)
10
- - [Architekturdiagramm](#architekturdiagramm)
11
- - [lt CLI — Funktionen](#lt-cli--funktionen)
12
- - [Projekt-Scaffolding](#projekt-scaffolding)
13
- - [Server-Entwicklung](#server-entwicklung)
14
- - [Frontend-Entwicklung](#frontend-entwicklung)
15
- - [Fullstack-Workflows](#fullstack-workflows)
16
- - [Vendor-Mode-Konvertierung](#vendor-mode-konvertierung)
17
- - [Status & Diagnose](#status--diagnose)
18
- - [Weitere Tools](#weitere-tools)
19
- - [lt-dev Plugin — Funktionen](#lt-dev-plugin--funktionen)
7
+ ## Table of Contents
8
+
9
+ - [Overview](#overview)
10
+ - [Architecture Diagram](#architecture-diagram)
11
+ - [lt CLI — Features](#lt-cli--features)
12
+ - [Project Scaffolding](#project-scaffolding)
13
+ - [Server Development](#server-development)
14
+ - [Frontend Development](#frontend-development)
15
+ - [Fullstack Workflows](#fullstack-workflows)
16
+ - [Vendor-Mode Conversion](#vendor-mode-conversion)
17
+ - [Status & Diagnostics](#status--diagnostics)
18
+ - [Additional Tools](#additional-tools)
19
+ - [lt-dev Plugin — Features](#lt-dev-plugin--features)
20
20
  - [Commands](#commands)
21
21
  - [Autonomous Agents](#autonomous-agents)
22
- - [Skills (Wissensbasis)](#skills-wissensbasis)
23
- - [Vendor-Mode-Prozesse](#vendor-mode-prozesse)
24
- - [Neues Projekt im Vendor-Mode erstellen](#1-neues-projekt-im-vendor-mode-erstellen)
25
- - [npm → Vendor überführen (Backend)](#2-backend-npm--vendor-überführen)
26
- - [npm → Vendor überführen (Frontend)](#3-frontend-npm--vendor-überführen)
27
- - [Vendor → npm zurückführen (Backend)](#4-backend-vendor--npm-rückführung)
28
- - [Vendor → npm zurückführen (Frontend)](#5-frontend-vendor--npm-rückführung)
29
- - [Update-Workflows](#6-update-workflows)
30
- - [Upstream-Contribution](#7-upstream-contribution)
31
- - [Entscheidungsmatrix](#entscheidungsmatrix)
32
- - [Glossar](#glossar)
22
+ - [Skills (Knowledge Base)](#skills-knowledge-base)
23
+ - [Vendor-Mode Processes](#vendor-mode-processes)
24
+ - [1. Create a new project in vendor mode](#1-create-a-new-project-in-vendor-mode)
25
+ - [2. Backend: convert npm → vendor](#2-backend-convert-npm--vendor)
26
+ - [3. Frontend: convert npm → vendor](#3-frontend-convert-npm--vendor)
27
+ - [4. Backend: vendor → npm rollback](#4-backend-vendor--npm-rollback)
28
+ - [5. Frontend: vendor → npm rollback](#5-frontend-vendor--npm-rollback)
29
+ - [6. Update workflows](#6-update-workflows)
30
+ - [7. Upstream contribution](#7-upstream-contribution)
31
+ - [Decision Matrix](#decision-matrix)
32
+ - [Glossary](#glossary)
33
33
 
34
34
  ---
35
35
 
36
- ## Überblick
36
+ ## Overview
37
37
 
38
- Das lenne.tech-Ecosystem besteht aus zwei komplementären Werkzeugen:
38
+ The lenne.tech ecosystem consists of two complementary tools:
39
39
 
40
- - **`lt CLI`** (`@lenne.tech/cli`) — Terminal-Tool für Scaffolding, Generierung, Status und Mode-Konvertierung
41
- - **`lt-dev` Plugin** — Claude-Code-Plugin mit Commands, autonomen Agents und Skills für intelligente Entwicklungs-Workflows
40
+ - **`lt CLI`** (`@lenne.tech/cli`) — Terminal tool for scaffolding, code generation, status, and mode conversion
41
+ - **`lt-dev` Plugin** — Claude Code plugin providing commands, autonomous agents, and skills for intelligent development workflows
42
42
 
43
- Beide Werkzeuge unterstützen den **Vendor-Mode** als Pilot für `@lenne.tech/nest-server` (Backend) und `@lenne.tech/nuxt-extensions` (Frontend). Im Vendor-Mode wird der Framework-Code direkt als Projekt-Source in `src/core/` (Backend) bzw. `app/core/` (Frontend) kopiert — ohne npm-Dependency.
43
+ Both tools support the **vendor mode** as a pilot for `@lenne.tech/nest-server` (backend) and `@lenne.tech/nuxt-extensions` (frontend). In vendor mode, the framework code is copied directly into the project as source code under `src/core/` (backend) or `app/core/` (frontend) — without an npm dependency.
44
44
 
45
45
  ---
46
46
 
47
- ## Architekturdiagramm
47
+ ## Architecture Diagram
48
48
 
49
49
  ```
50
50
  ┌─────────────────────────────────────────────────────────────────────┐
51
- │ Entwickler / Claude Code │
51
+ │ Developer / Claude Code │
52
52
  └─────────┬────────────────────────────────────────────────┬──────────┘
53
53
  │ │
54
- │ Terminal │ Slash-Commands
54
+ │ Terminal │ Slash commands
55
55
  ▼ ▼
56
56
  ┌──────────────────────┐ ┌────────────────────────┐
57
57
  │ lt CLI │ │ lt-dev Plugin │
58
58
  │ │ │ │
59
59
  │ • Scaffolding │ │ • Commands │
60
- │ • Mode-Conversion │◄─── invoked by ──────┤ • Agents │
61
- │ • Code-Generation │ │ • Skills │
62
- │ • Status/Diagnose │ │ │
60
+ │ • Mode conversion │◄─── invoked by ──────┤ • Agents │
61
+ │ • Code generation │ │ • Skills │
62
+ │ • Status/diagnosis │ │ │
63
63
  └──────────┬───────────┘ └────────────┬───────────┘
64
64
  │ │
65
65
  │ writes to │ operates on
66
66
  ▼ ▼
67
- ┌──────────────────────────────────────────────────────────────────────┐
68
- │ Fullstack-Projekt │
67
+ ┌─────────────────────────────────────────────────────────────────────┐
68
+ │ Fullstack Project │
69
69
  │ │
70
70
  │ projects/api (Backend — NestJS) projects/app (Frontend) │
71
71
  │ ├── npm mode: @lenne.tech/nest-server ├── npm mode: @lenne.tech/ │
72
72
  │ │ in package.json │ nuxt-extensions │
73
73
  │ └── vendor mode: src/core/ + VENDOR.md └── vendor mode: app/core/ │
74
74
  │ + VENDOR.md │
75
- └──────────────────────────────────────────────────────────────────────┘
76
- ▲ ▲
77
- │ syncs from │ syncs from
78
- │ │
75
+ └─────────────────────────────────────────────────────────────────────┘
76
+ ▲ ▲
77
+ │ syncs from │ syncs from
78
+ │ │
79
79
  ┌──────────┴──────────────┐ ┌───────────┴────────────┐
80
80
  │ github.com/lenneTech/ │ │ github.com/lenneTech/ │
81
81
  │ nest-server │ │ nuxt-extensions │
@@ -85,21 +85,21 @@ Beide Werkzeuge unterstützen den **Vendor-Mode** als Pilot für `@lenne.tech/ne
85
85
 
86
86
  ---
87
87
 
88
- ## lt CLI — Funktionen
88
+ ## lt CLI — Features
89
89
 
90
- ### Projekt-Scaffolding
90
+ ### Project Scaffolding
91
91
 
92
- | Command | Zweck |
93
- |---------|-------|
94
- | `lt fullstack init` | Erstellt ein neues Monorepo mit API + Frontend. Unterstützt npm- und vendor-Mode für beide Seiten |
95
- | `lt frontend nuxt` | Standalone Nuxt-4-Projekt aus `nuxt-base-starter` |
96
- | `lt frontend angular` | Standalone Angular-Projekt aus `ng-base-starter` |
97
- | `lt server create` | Standalone NestJS-Projekt aus `nest-server-starter` |
98
- | `lt starter chrome-extension` | Chrome-Extension-Starter |
99
- | `lt cli create` | Neues CLI-Projekt via Gluegun |
100
- | `lt typescript create` | TypeScript-Library-Starter |
92
+ | Command | Purpose |
93
+ |---------|---------|
94
+ | `lt fullstack init` | Create a new monorepo with API + frontend. Supports npm and vendor mode for both sides |
95
+ | `lt frontend nuxt` | Standalone Nuxt 4 project from `nuxt-base-starter` |
96
+ | `lt frontend angular` | Standalone Angular project from `ng-base-starter` |
97
+ | `lt server create` | Standalone NestJS project from `nest-server-starter` |
98
+ | `lt starter chrome-extension` | Chrome extension starter |
99
+ | `lt cli create` | New CLI project via Gluegun |
100
+ | `lt typescript create` | TypeScript library starter |
101
101
 
102
- **Fullstack-Init mit Vendor-Modes:**
102
+ **Fullstack init with vendor modes:**
103
103
 
104
104
  ```bash
105
105
  lt fullstack init \
@@ -113,78 +113,78 @@ lt fullstack init \
113
113
  ```
114
114
 
115
115
  Flags:
116
- - `--framework-mode npm|vendor` — Backend-Modus
117
- - `--frontend-framework-mode npm|vendor` — Frontend-Modus
118
- - `--framework-upstream-branch <tag>` — Spezifische nest-server Version für Vendor
119
- - `--dry-run` — Plan anzeigen ohne Änderungen
116
+ - `--framework-mode npm|vendor` — Backend mode
117
+ - `--frontend-framework-mode npm|vendor` — Frontend mode
118
+ - `--framework-upstream-branch <tag>` — Specific nest-server version for vendor
119
+ - `--dry-run` — Show plan without making changes
120
120
 
121
121
  ---
122
122
 
123
- ### Server-Entwicklung
123
+ ### Server Development
124
124
 
125
- | Command | Zweck |
126
- |---------|-------|
127
- | `lt server module` | Generiert ein NestJS-Modul (Model, Service, Controller, Resolver, Tests) |
128
- | `lt server object` | Generiert einen Input/Output-Typ |
129
- | `lt server add-property` | Fügt einem existierenden Modul ein Property hinzu |
130
- | `lt server test` | Generiert E2E-Tests für ein Modul |
131
- | `lt server permissions` | Analysiert alle `@Roles`/`@Restricted` Decoratoren, erzeugt Report (md/json/html) |
132
- | `lt server create-secret` | Generiert sichere Secrets für `.env` |
133
- | `lt server set-secrets` | Setzt Secrets im Projekt |
134
- | **`lt server convert-mode`** | **Konvertiert Backend zwischen npm und vendor Mode** |
125
+ | Command | Purpose |
126
+ |---------|---------|
127
+ | `lt server module` | Generate a NestJS module (model, service, controller, resolver, tests) |
128
+ | `lt server object` | Generate an input/output type |
129
+ | `lt server add-property` | Add a property to an existing module |
130
+ | `lt server test` | Generate E2E tests for a module |
131
+ | `lt server permissions` | Analyze all `@Roles`/`@Restricted` decorators, generate report (md/json/html) |
132
+ | `lt server create-secret` | Generate secure secrets for `.env` |
133
+ | `lt server set-secrets` | Set secrets in the project |
134
+ | **`lt server convert-mode`** | **Convert backend between npm and vendor mode** |
135
135
 
136
- Alle Code-Generatoren sind **mode-aware**: Im Vendor-Mode nutzen sie relative Pfade zu `src/core/`, im npm-Mode den bare specifier `@lenne.tech/nest-server`.
136
+ All code generators are **mode-aware**: In vendor mode they use relative paths to `src/core/`; in npm mode they use the bare specifier `@lenne.tech/nest-server`.
137
137
 
138
138
  ---
139
139
 
140
- ### Frontend-Entwicklung
140
+ ### Frontend Development
141
141
 
142
- | Command | Zweck |
143
- |---------|-------|
144
- | `lt frontend nuxt` | Nuxt-Projekt aus Starter erstellen |
145
- | `lt frontend angular` | Angular-Projekt aus Starter erstellen |
146
- | **`lt frontend convert-mode`** | **Konvertiert Frontend zwischen npm und vendor Mode** |
142
+ | Command | Purpose |
143
+ |---------|---------|
144
+ | `lt frontend nuxt` | Create Nuxt project from starter |
145
+ | `lt frontend angular` | Create Angular project from starter |
146
+ | **`lt frontend convert-mode`** | **Convert frontend between npm and vendor mode** |
147
147
 
148
148
  ---
149
149
 
150
- ### Fullstack-Workflows
150
+ ### Fullstack Workflows
151
151
 
152
- | Command | Zweck |
153
- |---------|-------|
154
- | `lt fullstack init` | Fullstack-Monorepo erstellen (siehe oben) |
155
- | `lt fullstack update` | Zeigt mode-spezifische Update-Anweisungen für Backend UND Frontend |
156
- | **`lt fullstack convert-mode`** | **Konvertiert Backend UND Frontend in einem Schritt zwischen npm und vendor Mode** |
152
+ | Command | Purpose |
153
+ |---------|---------|
154
+ | `lt fullstack init` | Create fullstack monorepo (see above) |
155
+ | `lt fullstack update` | Show mode-specific update instructions for backend AND frontend |
156
+ | **`lt fullstack convert-mode`** | **Convert backend AND frontend between npm and vendor mode in a single command** |
157
157
 
158
- **Fullstack Mode-Konvertierung in einem Command:**
158
+ **Fullstack mode conversion in one command:**
159
159
 
160
160
  ```bash
161
- # Beide Subprojekte in vendor mode
161
+ # Both subprojects to vendor mode
162
162
  lt fullstack convert-mode --to vendor --noConfirm
163
163
 
164
- # Mit spezifischen Upstream-Versionen
164
+ # With specific upstream versions
165
165
  lt fullstack convert-mode --to vendor \
166
166
  --framework-upstream-branch 11.24.3 \
167
167
  --frontend-framework-upstream-branch 1.5.3 \
168
168
  --noConfirm
169
169
 
170
- # Beide zurück zu npm
170
+ # Both back to npm
171
171
  lt fullstack convert-mode --to npm --noConfirm
172
172
 
173
- # Nur Backend konvertieren
173
+ # Only convert backend
174
174
  lt fullstack convert-mode --to vendor --skip-frontend --noConfirm
175
175
 
176
- # Nur Frontend konvertieren
176
+ # Only convert frontend
177
177
  lt fullstack convert-mode --to vendor --skip-backend --noConfirm
178
178
 
179
- # Dry-run (Plan ohne Änderungen)
179
+ # Dry-run (plan without changes)
180
180
  lt fullstack convert-mode --to vendor --dry-run
181
181
  ```
182
182
 
183
- Der Command findet automatisch `projects/api/` und `projects/app/` (oder `packages/api` / `packages/app`), erkennt die aktuellen Modi, zeigt einen Plan an und orchestriert dann die Konvertierung beider Seiten mit den passenden Helper-Methoden.
183
+ The command automatically locates `projects/api/` and `projects/app/` (or `packages/api` / `packages/app`), detects the current modes, shows a plan, and then orchestrates the conversion of both sides using the appropriate helper methods.
184
184
 
185
185
  ---
186
186
 
187
- ### Vendor-Mode-Konvertierung
187
+ ### Vendor-Mode Conversion
188
188
 
189
189
  **Backend**: `lt server convert-mode`
190
190
 
@@ -196,7 +196,7 @@ lt server convert-mode --to vendor --upstream-branch 11.24.3 --noConfirm
196
196
  # vendor → npm
197
197
  lt server convert-mode --to npm --version 11.24.3 --noConfirm
198
198
 
199
- # Dry-run (Plan ohne Änderungen)
199
+ # Dry-run (plan without changes)
200
200
  lt server convert-mode --to vendor --dry-run
201
201
  ```
202
202
 
@@ -214,19 +214,19 @@ lt frontend convert-mode --to npm --version 1.5.3 --noConfirm
214
214
  lt frontend convert-mode --to vendor --dry-run
215
215
  ```
216
216
 
217
- Beide Commands klonen das jeweilige Upstream-Repo nach `/tmp/`, führen die Code-Transformation durch und räumen am Ende auf. Es werden **keine lokalen Pfade** benötigt.
217
+ Both commands clone the respective upstream repo into `/tmp/`, perform the code transformation, and clean up at the end. **No local paths** are required.
218
218
 
219
219
  ---
220
220
 
221
- ### Status & Diagnose
221
+ ### Status & Diagnostics
222
222
 
223
- | Command | Zweck |
224
- |---------|-------|
225
- | `lt status` | Zeigt Projekt-Typ, Framework-Modus (Backend + Frontend), Config, Git-Branch, Versionen. Im Monorepo-Root werden beide Subprojekte automatisch gescannt |
226
- | `lt doctor` | Prüft Umgebung, Versionen, Abhängigkeiten |
227
- | `lt history` | Zeigt CLI-Command-Verlauf |
223
+ | Command | Purpose |
224
+ |---------|---------|
225
+ | `lt status` | Shows project type, framework mode (backend + frontend), config, git branch, versions. At the monorepo root, both subprojects are automatically scanned |
226
+ | `lt doctor` | Checks environment, versions, dependencies |
227
+ | `lt history` | Shows CLI command history |
228
228
 
229
- **Beispiel im IMO-Monorepo-Root:**
229
+ **Example at the monorepo root:**
230
230
 
231
231
  ```
232
232
  Monorepo Subprojects:
@@ -236,17 +236,17 @@ Monorepo Subprojects:
236
236
 
237
237
  ---
238
238
 
239
- ### Weitere Tools
239
+ ### Additional Tools
240
240
 
241
- | Bereich | Commands |
242
- |---------|----------|
241
+ | Area | Commands |
242
+ |------|----------|
243
243
  | **Config** | `lt config init`, `lt config validate`, `lt config show`, `lt config help` |
244
244
  | **Git** | `lt git create`, `git get`, `git update`, `git clean`, `git squash`, `git rebase`, `git rename`, `git reset`, `git undo`, `git clear`, `git force-pull` |
245
245
  | **NPM** | `lt npm reinit` |
246
246
  | **MongoDB** | `lt mongodb collection-export`, `mongodb s3-restore` |
247
247
  | **Qdrant** | `lt qdrant stats`, `qdrant delete` |
248
248
  | **Directus** | `lt directus docker-setup`, `directus typegen`, `directus remove` |
249
- | **Deployment** | `lt deployment create` (GitHub/GitLab Pipelines) |
249
+ | **Deployment** | `lt deployment create` (GitHub/GitLab pipelines) |
250
250
  | **Blocks/Components** | `lt blocks add`, `lt components add` |
251
251
  | **Tools** | `lt tools regex`, `tools sha256`, `tools jwt-read`, `tools crypt`, `tools install-scripts` |
252
252
  | **Docs** | `lt docs open` |
@@ -255,188 +255,188 @@ Monorepo Subprojects:
255
255
 
256
256
  ---
257
257
 
258
- ## lt-dev Plugin — Funktionen
258
+ ## lt-dev Plugin — Features
259
259
 
260
- Das `lt-dev` Claude-Code-Plugin enthält **Commands** (User-invocable), **Agents** (autonome Execution) und **Skills** (Wissensbasen).
260
+ The `lt-dev` Claude Code plugin provides **Commands** (user-invocable), **Agents** (autonomous execution), and **Skills** (knowledge bases).
261
261
 
262
262
  ### Commands
263
263
 
264
264
  #### Backend
265
265
 
266
- | Command | Zweck |
267
- |---------|-------|
268
- | `/lt-dev:backend:update-nest-server` | Aktualisiert `@lenne.tech/nest-server` im npm-Mode mit Migration-Guides |
269
- | `/lt-dev:backend:update-nest-server-core` | Synct vendored `src/core/` mit Upstream (Vendor-Mode) |
270
- | `/lt-dev:backend:convert-to-vendor` | Konvertiert bestehendes Projekt von npm → vendor (inkl. Migration-Guides) |
271
- | `/lt-dev:backend:convert-to-npm` | Konvertiert vendored Projekt zurück zu npm |
272
- | `/lt-dev:backend:contribute-nest-server-core` | Bereitet lokale Patches als Upstream-PR für nest-server vor |
273
- | `/lt-dev:backend:sec-audit` | Security-Audit des Backend-Codes |
274
- | `/lt-dev:backend:sec-review` | Security-Review eines spezifischen Code-Bereichs |
275
- | `/lt-dev:backend:test-generate` | Generiert E2E-Tests |
276
- | `/lt-dev:backend:code-cleanup` | Räumt Code auf (imports, formatting) |
266
+ | Command | Purpose |
267
+ |---------|---------|
268
+ | `/lt-dev:backend:update-nest-server` | Update `@lenne.tech/nest-server` in npm mode with migration guides |
269
+ | `/lt-dev:backend:update-nest-server-core` | Sync vendored `src/core/` with upstream (vendor mode) |
270
+ | `/lt-dev:backend:convert-to-vendor` | Convert existing project from npm → vendor (incl. migration guides) |
271
+ | `/lt-dev:backend:convert-to-npm` | Convert vendored project back to npm |
272
+ | `/lt-dev:backend:contribute-nest-server-core` | Prepare local patches as upstream PR for nest-server |
273
+ | `/lt-dev:backend:sec-audit` | Security audit of backend code |
274
+ | `/lt-dev:backend:sec-review` | Security review of a specific code area |
275
+ | `/lt-dev:backend:test-generate` | Generate E2E tests |
276
+ | `/lt-dev:backend:code-cleanup` | Clean up code (imports, formatting) |
277
277
 
278
278
  #### Frontend
279
279
 
280
- | Command | Zweck |
281
- |---------|-------|
282
- | `/lt-dev:frontend:update-nuxt-extensions-core` | Synct vendored `app/core/` mit Upstream |
283
- | `/lt-dev:frontend:convert-to-vendor` | Konvertiert Frontend-Projekt von npm → vendor |
284
- | `/lt-dev:frontend:convert-to-npm` | Konvertiert vendored Frontend zurück zu npm |
285
- | `/lt-dev:frontend:contribute-nuxt-extensions-core` | Bereitet lokale Patches als Upstream-PR für nuxt-extensions vor |
286
- | `/lt-dev:frontend:figma-init` | Initialisiert Figma-Code-Connect Setup |
287
- | `/lt-dev:frontend:figma-research` | Analysiert Figma-Designs für Implementierung |
288
- | `/lt-dev:frontend:figma-to-code` | Übersetzt Figma-Design in Vue/Nuxt-Code |
289
- | `/lt-dev:frontend:env-migrate` | Migriert `.env` von alten Standards |
290
- | `/lt-dev:frontend:init-conventions` | Initialisiert Frontend-Konventionen |
280
+ | Command | Purpose |
281
+ |---------|---------|
282
+ | `/lt-dev:frontend:update-nuxt-extensions-core` | Sync vendored `app/core/` with upstream |
283
+ | `/lt-dev:frontend:convert-to-vendor` | Convert frontend project from npm → vendor |
284
+ | `/lt-dev:frontend:convert-to-npm` | Convert vendored frontend back to npm |
285
+ | `/lt-dev:frontend:contribute-nuxt-extensions-core` | Prepare local patches as upstream PR for nuxt-extensions |
286
+ | `/lt-dev:frontend:figma-init` | Initialize Figma Code Connect setup |
287
+ | `/lt-dev:frontend:figma-research` | Analyze Figma designs for implementation |
288
+ | `/lt-dev:frontend:figma-to-code` | Translate Figma design into Vue/Nuxt code |
289
+ | `/lt-dev:frontend:env-migrate` | Migrate `.env` from old standards |
290
+ | `/lt-dev:frontend:init-conventions` | Initialize frontend conventions |
291
291
 
292
292
  #### Fullstack
293
293
 
294
- | Command | Zweck |
295
- |---------|-------|
296
- | **`/lt-dev:fullstack:update-all`** | **Comprehensive Update**: Backend + Frontend (mode-aware) + Package-Maintenance + CLAUDE.md-Sync + Validation |
297
- | `/lt-dev:fullstack:update` | Einfacher Backend + Frontend Update (legacy, weniger umfassend) |
298
- | `/lt-dev:fullstack:sync-claude-md` | Synct `CLAUDE.md` aus Upstream-Starter-Templates |
294
+ | Command | Purpose |
295
+ |---------|---------|
296
+ | **`/lt-dev:fullstack:update-all`** | **Comprehensive update**: backend + frontend (mode-aware) + package maintenance + CLAUDE.md sync + validation |
297
+ | `/lt-dev:fullstack:update` | Simple backend + frontend update (legacy, less comprehensive) |
298
+ | `/lt-dev:fullstack:sync-claude-md` | Sync `CLAUDE.md` from upstream starter templates |
299
299
 
300
300
  #### Maintenance
301
301
 
302
- | Command | Zweck |
303
- |---------|-------|
304
- | `/lt-dev:maintenance:maintain` | FULL MODE: Package-Update + Audit + Security + Deduplication |
305
- | `/lt-dev:maintenance:maintain-check` | DRY-RUN: Analyse ohne Änderungen |
306
- | `/lt-dev:maintenance:maintain-security` | Nur Security-Patches |
307
- | `/lt-dev:maintenance:maintain-pre-release` | Conservative Patch-only vor Release |
308
- | `/lt-dev:maintenance:maintain-post-feature` | Post-Feature-Cleanup |
302
+ | Command | Purpose |
303
+ |---------|---------|
304
+ | `/lt-dev:maintenance:maintain` | FULL MODE: package update + audit + security + deduplication |
305
+ | `/lt-dev:maintenance:maintain-check` | DRY-RUN: analysis without changes |
306
+ | `/lt-dev:maintenance:maintain-security` | Security patches only |
307
+ | `/lt-dev:maintenance:maintain-pre-release` | Conservative patch-only before release |
308
+ | `/lt-dev:maintenance:maintain-post-feature` | Post-feature cleanup |
309
309
 
310
310
  #### Git
311
311
 
312
- | Command | Zweck |
313
- |---------|-------|
314
- | `/lt-dev:git:commit-message` | Generiert Conventional-Commit-Message aus Staging |
315
- | `/lt-dev:git:create-request` | Erstellt Merge-Request mit beschreibendem Body |
316
- | `/lt-dev:git:mr-description` | Generiert MR-Description aus Commits |
317
- | `/lt-dev:git:mr-description-clipboard` | Dito, kopiert ins Clipboard |
318
- | `/lt-dev:git:rebase` | Rebase auf development-Branch mit Conflict-Resolution |
319
- | `/lt-dev:git:rebase-mrs` | Rebased mehrere MRs hintereinander |
312
+ | Command | Purpose |
313
+ |---------|---------|
314
+ | `/lt-dev:git:commit-message` | Generate conventional commit message from staging |
315
+ | `/lt-dev:git:create-request` | Create merge request with descriptive body |
316
+ | `/lt-dev:git:mr-description` | Generate MR description from commits |
317
+ | `/lt-dev:git:mr-description-clipboard` | Same, copied to clipboard |
318
+ | `/lt-dev:git:rebase` | Rebase onto development branch with conflict resolution |
319
+ | `/lt-dev:git:rebase-mrs` | Rebase multiple MRs sequentially |
320
320
 
321
321
  #### Docker
322
322
 
323
- | Command | Zweck |
324
- |---------|-------|
325
- | `/lt-dev:docker:gen-setup` | Generiert Docker-Konfiguration (Dockerfile + compose + .env) |
323
+ | Command | Purpose |
324
+ |---------|---------|
325
+ | `/lt-dev:docker:gen-setup` | Generate Docker configuration (Dockerfile + compose + .env) |
326
326
 
327
327
  #### Plugin
328
328
 
329
- | Command | Zweck |
330
- |---------|-------|
331
- | `/lt-dev:plugin:check` | Validiert das Plugin-Setup nach Context-Loss |
332
- | `/lt-dev:plugin:element` | Interaktives Erstellen neuer Plugin-Elemente |
329
+ | Command | Purpose |
330
+ |---------|---------|
331
+ | `/lt-dev:plugin:check` | Validate the plugin setup after context loss |
332
+ | `/lt-dev:plugin:element` | Interactive creation of new plugin elements |
333
333
 
334
334
  #### Vibe (Spec-Driven Development)
335
335
 
336
- | Command | Zweck |
337
- |---------|-------|
338
- | `/lt-dev:vibe:plan` | Erstellt Implementierungsplan aus Requirement |
339
- | `/lt-dev:vibe:build` | Implementiert nach Plan |
340
- | `/lt-dev:vibe:build-plan` | Plan + Build in einem Flow |
336
+ | Command | Purpose |
337
+ |---------|---------|
338
+ | `/lt-dev:vibe:plan` | Create implementation plan from requirement |
339
+ | `/lt-dev:vibe:build` | Implement according to plan |
340
+ | `/lt-dev:vibe:build-plan` | Plan + build in one flow |
341
341
 
342
342
  #### Standalone
343
343
 
344
- | Command | Zweck |
345
- |---------|-------|
346
- | `/lt-dev:debug` | Structured Debugging Session |
347
- | `/lt-dev:review` | Code-Review mit mehreren Reviewer-Perspektiven |
348
- | `/lt-dev:refactor-frontend` | Frontend-Refactoring-Helfer |
349
- | `/lt-dev:resolve-ticket` | Linear-Ticket implementieren |
350
- | `/lt-dev:create-ticket` | Linear-Ticket erstellen |
351
- | `/lt-dev:create-story` | User-Story erstellen (DE) |
352
- | `/lt-dev:create-task` | Linear-Task erstellen |
353
- | `/lt-dev:create-bug` | Linear-Bug erstellen |
354
- | `/lt-dev:linear-comment` | Linear-Kommentar erstellen |
355
- | `/lt-dev:dev-submit` | Dev-Submit-Workflow (commit + push + MR) |
356
- | `/lt-dev:interview` | Struktur-Interview für Requirements |
357
- | `/lt-dev:skill-optimize` | Optimiert eine Plugin-Skill |
358
- | `/lt-dev:spec-to-tasks` | Spec → Aufgaben-Liste |
344
+ | Command | Purpose |
345
+ |---------|---------|
346
+ | `/lt-dev:debug` | Structured debugging session |
347
+ | `/lt-dev:review` | Code review with multiple reviewer perspectives |
348
+ | `/lt-dev:refactor-frontend` | Frontend refactoring helper |
349
+ | `/lt-dev:resolve-ticket` | Implement Linear ticket |
350
+ | `/lt-dev:create-ticket` | Create Linear ticket |
351
+ | `/lt-dev:create-story` | Create user story (German) |
352
+ | `/lt-dev:create-task` | Create Linear task |
353
+ | `/lt-dev:create-bug` | Create Linear bug |
354
+ | `/lt-dev:linear-comment` | Create Linear comment |
355
+ | `/lt-dev:dev-submit` | Dev-submit workflow (commit + push + MR) |
356
+ | `/lt-dev:interview` | Structured interview for requirements |
357
+ | `/lt-dev:skill-optimize` | Optimize a plugin skill |
358
+ | `/lt-dev:spec-to-tasks` | Spec → task list |
359
359
 
360
360
  ---
361
361
 
362
362
  ### Autonomous Agents
363
363
 
364
- Autonome Agents führen mehrschrittige Aufgaben ohne Interaktion aus. Sie werden via Commands oder Agent-Tool gespawnt.
364
+ Autonomous agents perform multi-step tasks without interaction. They are spawned via commands or the Agent tool.
365
365
 
366
366
  #### Vendor-Mode Agents
367
367
 
368
- | Agent | Zweck | Gespawnt von |
369
- |-------|-------|--------------|
370
- | `vendor-mode-converter` | Backend npm → vendor Konvertierung inkl. Migration-Guides | `/lt-dev:backend:convert-to-vendor` |
371
- | `vendor-mode-converter-frontend` | Frontend npm → vendor Konvertierung inkl. Changelog | `/lt-dev:frontend:convert-to-vendor` |
372
- | `nest-server-core-updater` | Upstream-Sync für vendored nest-server core | `/lt-dev:backend:update-nest-server-core` |
373
- | `nuxt-extensions-core-updater` | Upstream-Sync für vendored nuxt-extensions core | `/lt-dev:frontend:update-nuxt-extensions-core` |
374
- | `nest-server-core-contributor` | Upstream-PR-Drafts aus lokalen Backend-Patches | `/lt-dev:backend:contribute-nest-server-core` |
375
- | `nuxt-extensions-core-contributor` | Upstream-PR-Drafts aus lokalen Frontend-Patches | `/lt-dev:frontend:contribute-nuxt-extensions-core` |
368
+ | Agent | Purpose | Spawned by |
369
+ |-------|---------|------------|
370
+ | `vendor-mode-converter` | Backend npm → vendor conversion incl. migration guides | `/lt-dev:backend:convert-to-vendor` |
371
+ | `vendor-mode-converter-frontend` | Frontend npm → vendor conversion incl. changelog | `/lt-dev:frontend:convert-to-vendor` |
372
+ | `nest-server-core-updater` | Upstream sync for vendored nest-server core | `/lt-dev:backend:update-nest-server-core` |
373
+ | `nuxt-extensions-core-updater` | Upstream sync for vendored nuxt-extensions core | `/lt-dev:frontend:update-nuxt-extensions-core` |
374
+ | `nest-server-core-contributor` | Upstream PR drafts from local backend patches | `/lt-dev:backend:contribute-nest-server-core` |
375
+ | `nuxt-extensions-core-contributor` | Upstream PR drafts from local frontend patches | `/lt-dev:frontend:contribute-nuxt-extensions-core` |
376
376
 
377
- #### Update-Agents
377
+ #### Update Agents
378
378
 
379
- | Agent | Zweck |
380
- |-------|-------|
381
- | `nest-server-updater` | npm-Mode Update von nest-server inkl. Migration-Guides |
382
- | `fullstack-updater` | Coordinated Backend + Frontend Update (legacy) |
383
- | `npm-package-maintainer` | Package-Optimierung (5 Modes) |
384
- | `branch-rebaser` | Rebase-Automation mit Conflict-Resolution |
379
+ | Agent | Purpose |
380
+ |-------|---------|
381
+ | `nest-server-updater` | npm-mode update of nest-server incl. migration guides |
382
+ | `fullstack-updater` | Coordinated backend + frontend update (legacy) |
383
+ | `npm-package-maintainer` | Package optimization (5 modes) |
384
+ | `branch-rebaser` | Rebase automation with conflict resolution |
385
385
 
386
386
  #### Development Agents
387
387
 
388
- | Agent | Zweck |
389
- |-------|-------|
390
- | `backend-dev` | Autonomous NestJS-Entwicklung |
391
- | `frontend-dev` | Autonomous Nuxt-4-Entwicklung |
392
- | `architect` | Architektur-Planung mit Stack-Enforcement |
393
- | `devops` | Docker, CI/CD, Environment |
388
+ | Agent | Purpose |
389
+ |-------|---------|
390
+ | `backend-dev` | Autonomous NestJS development |
391
+ | `frontend-dev` | Autonomous Nuxt 4 development |
392
+ | `architect` | Architecture planning with stack enforcement |
393
+ | `devops` | Docker, CI/CD, environment |
394
394
 
395
- #### Reviewer-Agents
395
+ #### Reviewer Agents
396
396
 
397
- | Agent | Zweck |
398
- |-------|-------|
399
- | `code-reviewer` | 6-Dimensionen Code-Review |
400
- | `backend-reviewer` | NestJS-spezifisch |
401
- | `frontend-reviewer` | Vue/Nuxt-spezifisch |
397
+ | Agent | Purpose |
398
+ |-------|---------|
399
+ | `code-reviewer` | 6-dimension code review |
400
+ | `backend-reviewer` | NestJS-specific |
401
+ | `frontend-reviewer` | Vue/Nuxt-specific |
402
402
  | `security-reviewer` | OWASP-aligned |
403
403
  | `a11y-reviewer` | Accessibility + Lighthouse |
404
- | `ux-reviewer` | UX-Patterns |
405
- | `performance-reviewer` | Bundle, Queries, Caching |
406
- | `devops-reviewer` | Docker, CI/CD Security |
407
- | `docs-reviewer` | README, JSDoc, Migration-Guides |
408
- | `test-reviewer` | Test-Coverage + Quality |
404
+ | `ux-reviewer` | UX patterns |
405
+ | `performance-reviewer` | Bundle, queries, caching |
406
+ | `devops-reviewer` | Docker, CI/CD security |
407
+ | `docs-reviewer` | README, JSDoc, migration guides |
408
+ | `test-reviewer` | Test coverage + quality |
409
409
 
410
410
  ---
411
411
 
412
- ### Skills (Wissensbasis)
413
-
414
- Skills enthalten strukturiertes Wissen und werden automatisch aktiviert bei passenden Anfragen.
415
-
416
- | Skill | Zweck |
417
- |-------|-------|
418
- | **`nest-server-core-vendoring`** | Backend-Vendoring-Pattern, flatten-fix, Sync-Workflows |
419
- | **`nuxt-extensions-core-vendoring`** | Frontend-Vendoring-Pattern, nuxt.config-Rewrite, Sync |
420
- | `nest-server-updating` | npm-Mode Update-Prozesse, Migration-Guides, Error-Patterns |
421
- | `generating-nest-servers` | NestJS-Module/Services/Controller generieren |
422
- | `developing-lt-frontend` | Nuxt-4-Development, Composables, Forms, Auth |
423
- | `maintaining-npm-packages` | Dependency-Optimierung (5 Modes) |
424
- | `using-lt-cli` | lt CLI Reference, Konventionen |
425
- | `developing-claude-plugins` | Plugin-Development (Skills, Commands, Agents) |
426
- | `coordinating-agent-teams` | Agent-Team-Coordination, Parallelism |
427
- | `building-stories-with-tdd` | TDD-Workflow für User-Stories |
428
- | `rebasing-branches` | Rebase-Strategien mit Conflict-Resolution |
429
- | `general-frontend-security` | OWASP Frontend Security |
412
+ ### Skills (Knowledge Base)
413
+
414
+ Skills contain structured knowledge and are automatically activated on matching queries.
415
+
416
+ | Skill | Purpose |
417
+ |-------|---------|
418
+ | **`nest-server-core-vendoring`** | Backend vendoring pattern, flatten-fix, sync workflows |
419
+ | **`nuxt-extensions-core-vendoring`** | Frontend vendoring pattern, nuxt.config rewrite, sync |
420
+ | `nest-server-updating` | npm-mode update processes, migration guides, error patterns |
421
+ | `generating-nest-servers` | Generate NestJS modules/services/controllers |
422
+ | `developing-lt-frontend` | Nuxt 4 development, composables, forms, auth |
423
+ | `maintaining-npm-packages` | Dependency optimization (5 modes) |
424
+ | `using-lt-cli` | lt CLI reference, conventions |
425
+ | `developing-claude-plugins` | Plugin development (skills, commands, agents) |
426
+ | `coordinating-agent-teams` | Agent team coordination, parallelism |
427
+ | `building-stories-with-tdd` | TDD workflow for user stories |
428
+ | `rebasing-branches` | Rebase strategies with conflict resolution |
429
+ | `general-frontend-security` | OWASP frontend security |
430
430
 
431
431
  ---
432
432
 
433
- ## Vendor-Mode-Prozesse
433
+ ## Vendor-Mode Processes
434
434
 
435
- ### 1. Neues Projekt im Vendor-Mode erstellen
435
+ ### 1. Create a new project in vendor mode
436
436
 
437
437
  ```
438
438
  ┌────────────────────────────────────────────────────────────────┐
439
- │ ENTWICKLER │
439
+ │ DEVELOPER │
440
440
  │ │
441
441
  │ lt fullstack init │
442
442
  │ --name my-project │
@@ -451,7 +451,7 @@ Skills enthalten strukturiertes Wissen und werden automatisch aktiviert bei pass
451
451
  │
452
452
  ▼
453
453
  ┌────────────────────────────────────────────────────────────────┐
454
- │ lt CLI macht: │
454
+ │ lt CLI performs: │
455
455
  │ │
456
456
  │ 1. git clone lt-monorepo │
457
457
  │ 2. setup frontend (nuxt-base-starter) │
@@ -480,7 +480,7 @@ Skills enthalten strukturiertes Wissen und werden automatisch aktiviert bei pass
480
480
  │
481
481
  ▼
482
482
  ┌────────────────────────────────────────────────────────────────┐
483
- │ PROJEKT BEREIT │
483
+ │ PROJECT READY │
484
484
  │ │
485
485
  │ my-project/ │
486
486
  │ ├── projects/ │
@@ -488,10 +488,10 @@ Skills enthalten strukturiertes Wissen und werden automatisch aktiviert bei pass
488
488
  │ │ │ ├── src/ │
489
489
  │ │ │ │ ├── core/ ← Vendored nest-server │
490
490
  │ │ │ │ │ └── VENDOR.md │
491
- │ │ │ │ ├── server/ ← Projekt-Code │
491
+ │ │ │ │ ├── server/ ← Project code │
492
492
  │ │ │ │ └── main.ts │
493
493
  │ │ │ ├── bin/migrate.js │
494
- │ │ │ └── package.json (ohne @lenne.tech/nest-server) │
494
+ │ │ │ └── package.json (no @lenne.tech/nest-server) │
495
495
  │ │ └── app/ │
496
496
  │ │ ├── app/ │
497
497
  │ │ │ ├── core/ ← Vendored nuxt-extensions │
@@ -500,64 +500,64 @@ Skills enthalten strukturiertes Wissen und werden automatisch aktiviert bei pass
500
500
  │ │ │ │ └── VENDOR.md │
501
501
  │ │ │ └── ... │
502
502
  │ │ ├── nuxt.config.ts (modules: ['./app/core/module']) │
503
- │ │ └── package.json (ohne @lenne.tech/nuxt-extensions) │
503
+ │ │ └── package.json (no @lenne.tech/nuxt-extensions) │
504
504
  │ └── CLAUDE.md │
505
505
  └────────────────────────────────────────────────────────────────┘
506
506
  ```
507
507
 
508
- **Alternative**: Nur Backend ODER nur Frontend vendored. Flags weglassen:
508
+ **Alternative**: Only backend OR only frontend vendored. Omit the respective flag:
509
509
 
510
510
  ```bash
511
- # Nur Backend vendored, Frontend bleibt npm
511
+ # Only backend vendored, frontend stays npm
512
512
  lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
513
513
  --framework-mode vendor --framework-upstream-branch 11.24.3 --noConfirm
514
514
 
515
- # Nur Frontend vendored, Backend bleibt npm
515
+ # Only frontend vendored, backend stays npm
516
516
  lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
517
517
  --frontend-framework-mode vendor --noConfirm
518
518
  ```
519
519
 
520
520
  ---
521
521
 
522
- ### 2. Backend: npm → Vendor überführen
522
+ ### 2. Backend: convert npm → vendor
523
523
 
524
- **Ausgangslage**: Existierendes Projekt im npm-Mode (`@lenne.tech/nest-server` in `package.json`).
524
+ **Starting point**: Existing project in npm mode (`@lenne.tech/nest-server` in `package.json`).
525
525
 
526
526
  ```
527
527
  ┌──────────────────────────────────────────────────────────┐
528
- │ ENTWICKLER in projects/api/ │
528
+ │ DEVELOPER in projects/api/ │
529
529
  │ │
530
- │ Option A — Via Claude Code (mit Migration-Guides): │
530
+ │ Option A — Via Claude Code (with migration guides): │
531
531
  │ /lt-dev:backend:convert-to-vendor │
532
532
  │ │
533
- │ Option B — Direkt via CLI (ohne Migration-Guides): │
533
+ │ Option B — Directly via CLI (no migration guides): │
534
534
  │ lt server convert-mode --to vendor │
535
535
  │ │
536
- │ Option C — Dry-Run (Plan ohne Änderungen): │
536
+ │ Option C — Dry-run (plan without changes): │
537
537
  │ lt server convert-mode --to vendor --dry-run │
538
538
  └─────────────┬────────────────────────────────────────────┘
539
539
  │
540
- ▼ Option A nutzt Agent
540
+ ▼ Option A uses agent
541
541
  ┌──────────────────────────────────────────────────────────┐
542
- │ vendor-mode-converter Agent │
542
+ │ vendor-mode-converter agent │
543
543
  │ │
544
544
  │ Phase 0: Prerequisites │
545
545
  │ - Verify npm mode │
546
546
  │ - Verify NOT already vendored │
547
547
  │ - Verify lt CLI available │
548
548
  │ │
549
- │ Phase 1: Version Detection │
549
+ │ Phase 1: Version detection │
550
550
  │ - SOURCE = current @lenne.tech/nest-server version │
551
551
  │ - TARGET = latest (or specified) │
552
552
  │ - Calculate version gap │
553
553
  │ │
554
- │ Phase 2: Migration-Guide Discovery │
554
+ │ Phase 2: Migration-guide discovery │
555
555
  │ - gh api lenneTech/nest-server/contents/migration- │
556
556
  │ guides │
557
557
  │ - Filter by from-version >= SOURCE, < TARGET │
558
558
  │ - Build ordered migration plan │
559
559
  │ │
560
- │ Phase 3: CLI Conversion │
560
+ │ Phase 3: CLI conversion │
561
561
  │ - lt server convert-mode --to vendor │
562
562
  │ --upstream-branch <TARGET> │
563
563
  │ - Applies all transformations: │
@@ -568,12 +568,12 @@ lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
568
568
  │ • express type-imports fix │
569
569
  │ • VENDOR.md │
570
570
  │ │
571
- │ Phase 4: Migration Application │
571
+ │ Phase 4: Migration application │
572
572
  │ - Apply each migration guide in version order │
573
573
  │ - Translate @lenne.tech/nest-server refs to relative │
574
574
  │ paths │
575
575
  │ │
576
- │ Phase 5: Validation Loop │
576
+ │ Phase 5: Validation loop │
577
577
  │ - tsc --noEmit │
578
578
  │ - pnpm lint │
579
579
  │ - pnpm test │
@@ -585,38 +585,38 @@ lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
585
585
 
586
586
  ---
587
587
 
588
- ### 3. Frontend: npm → Vendor überführen
588
+ ### 3. Frontend: convert npm → vendor
589
589
 
590
- **Ausgangslage**: Existierendes Nuxt-Projekt im npm-Mode.
590
+ **Starting point**: Existing Nuxt project in npm mode.
591
591
 
592
592
  ```
593
593
  ┌──────────────────────────────────────────────────────────┐
594
- │ ENTWICKLER in projects/app/ │
594
+ │ DEVELOPER in projects/app/ │
595
595
  │ │
596
- │ Option A — Via Claude Code (mit Changelog): │
596
+ │ Option A — Via Claude Code (with changelog): │
597
597
  │ /lt-dev:frontend:convert-to-vendor │
598
598
  │ │
599
- │ Option B — Direkt via CLI: │
599
+ │ Option B — Directly via CLI: │
600
600
  │ lt frontend convert-mode --to vendor │
601
601
  │ │
602
- │ Option C — Dry-Run: │
602
+ │ Option C — Dry-run: │
603
603
  │ lt frontend convert-mode --to vendor --dry-run │
604
604
  └─────────────┬────────────────────────────────────────────┘
605
605
  │
606
606
  ▼
607
607
  ┌──────────────────────────────────────────────────────────┐
608
- │ vendor-mode-converter-frontend Agent (Option A) │
608
+ │ vendor-mode-converter-frontend agent (Option A) │
609
609
  │ │
610
610
  │ Phase 0: Prerequisites │
611
- │ Phase 1: Version Detection │
611
+ │ Phase 1: Version detection │
612
612
  │ - SOURCE = current @lenne.tech/nuxt-extensions │
613
613
  │ - TARGET = latest │
614
614
  │ │
615
- │ Phase 2: Changelog Discovery │
615
+ │ Phase 2: Changelog discovery │
616
616
  │ - Fetch CHANGELOG.md from nuxt-extensions repo │
617
617
  │ - Fetch GitHub releases for version gap │
618
618
  │ │
619
- │ Phase 3: CLI Conversion │
619
+ │ Phase 3: CLI conversion │
620
620
  │ - lt frontend convert-mode --to vendor │
621
621
  │ --upstream-branch <TARGET> │
622
622
  │ - Transformations: │
@@ -627,8 +627,8 @@ lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
627
627
  │ • remove @lenne.tech/nuxt-extensions dep │
628
628
  │ • VENDOR.md │
629
629
  │ │
630
- │ Phase 4: Changelog Application │
631
- │ - Apply breaking changes from changelog │
630
+ │ Phase 4: Changelog application │
631
+ │ - Apply breaking changes from changelog │
632
632
  │ │
633
633
  │ Phase 5: Validation │
634
634
  │ - nuxt build │
@@ -640,27 +640,27 @@ lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
640
640
 
641
641
  ---
642
642
 
643
- ### 4. Backend: Vendor → npm Rückführung
643
+ ### 4. Backend: vendor → npm rollback
644
644
 
645
- **Ausgangslage**: Projekt im Vendor-Mode (`src/core/VENDOR.md` existiert).
645
+ **Starting point**: Project in vendor mode (`src/core/VENDOR.md` exists).
646
646
 
647
647
  ```
648
648
  ┌──────────────────────────────────────────────────────────┐
649
- │ ENTWICKLER in projects/api/ │
649
+ │ DEVELOPER in projects/api/ │
650
650
  │ │
651
651
  │ Option A — Via Claude Code: │
652
652
  │ /lt-dev:backend:convert-to-npm │
653
653
  │ │
654
- │ Option B — Direkt via CLI: │
654
+ │ Option B — Directly via CLI: │
655
655
  │ lt server convert-mode --to npm │
656
656
  │ │
657
- │ Mit spezifischer Version: │
657
+ │ With specific version: │
658
658
  │ lt server convert-mode --to npm --version 11.24.3 │
659
659
  └─────────────┬────────────────────────────────────────────┘
660
660
  │
661
661
  ▼
662
662
  ┌──────────────────────────────────────────────────────────┐
663
- │ lt CLI macht: │
663
+ │ lt CLI performs: │
664
664
  │ │
665
665
  │ 1. Read baseline version from src/core/VENDOR.md │
666
666
  │ 2. Warn if local patches exist in VENDOR.md │
@@ -680,30 +680,30 @@ lt fullstack init --name my-project --frontend nuxt --api-mode Rest \
680
680
  └──────────────────────────────────────────────────────────┘
681
681
  ```
682
682
 
683
- **⚠️ Warnung vor Rückführung:**
684
- Vor einem `convert-to-npm` sollten alle substantiellen lokalen Patches im vendored core über `/lt-dev:backend:contribute-nest-server-core` **upstream beigetragen** werden — sonst gehen sie verloren.
683
+ **⚠️ Warning before rollback:**
684
+ Before a `convert-to-npm`, all substantial local patches in the vendored core should be **contributed upstream** via `/lt-dev:backend:contribute-nest-server-core` — otherwise they will be lost.
685
685
 
686
686
  ---
687
687
 
688
- ### 5. Frontend: Vendor → npm Rückführung
688
+ ### 5. Frontend: vendor → npm rollback
689
689
 
690
690
  ```
691
691
  ┌──────────────────────────────────────────────────────────┐
692
- │ ENTWICKLER in projects/app/ │
692
+ │ DEVELOPER in projects/app/ │
693
693
  │ │
694
694
  │ Option A — Via Claude Code: │
695
695
  │ /lt-dev:frontend:convert-to-npm │
696
696
  │ │
697
- │ Option B — Direkt via CLI: │
697
+ │ Option B — Directly via CLI: │
698
698
  │ lt frontend convert-mode --to npm │
699
699
  │ │
700
- │ Mit spezifischer Version: │
700
+ │ With specific version: │
701
701
  │ lt frontend convert-mode --to npm --version 1.5.3 │
702
702
  └─────────────┬────────────────────────────────────────────┘
703
703
  │
704
704
  ▼
705
705
  ┌──────────────────────────────────────────────────────────┐
706
- │ lt CLI macht: │
706
+ │ lt CLI performs: │
707
707
  │ │
708
708
  │ 1. Read baseline version from app/core/VENDOR.md │
709
709
  │ 2. Warn if local patches exist in VENDOR.md │
@@ -721,9 +721,9 @@ Vor einem `convert-to-npm` sollten alle substantiellen lokalen Patches im vendor
721
721
 
722
722
  ---
723
723
 
724
- ### 6. Update-Workflows
724
+ ### 6. Update workflows
725
725
 
726
- Der **empfohlene** Weg für alle Updates ist `/lt-dev:fullstack:update-all`. Er ist mode-aware und orchestriert die passenden Agents automatisch.
726
+ The **recommended** path for all updates is `/lt-dev:fullstack:update-all`. It is mode-aware and orchestrates the appropriate agents automatically.
727
727
 
728
728
  ```
729
729
  ┌──────────────────────────────────────────────────────────────────┐
@@ -733,29 +733,29 @@ Der **empfohlene** Weg für alle Updates ist `/lt-dev:fullstack:update-all`. Er
733
733
  │ Backend: test -f <api>/src/core/VENDOR.md → vendor | npm │
734
734
  │ Frontend: test -f <app>/app/core/VENDOR.md → vendor | npm │
735
735
  │ │
736
- │ Phase 2: Version analysis + UPDATE_PLAN.md + User Approval │
736
+ │ Phase 2: Version analysis + UPDATE_PLAN.md + user approval │
737
737
  │ │
738
- │ Phase 3: Backend Framework Update │
738
+ │ Phase 3: Backend framework update │
739
739
  │ IF npm: spawn lt-dev:nest-server-updater │
740
740
  │ IF vendor: spawn lt-dev:nest-server-core-updater │
741
741
  │ │
742
- │ Phase 4: Frontend Framework Update │
742
+ │ Phase 4: Frontend framework update │
743
743
  │ IF npm: spawn lt-dev:fullstack-updater --skip-backend │
744
744
  │ IF vendor: spawn lt-dev:nuxt-extensions-core-updater │
745
745
  │ │
746
- │ Phase 5: Package Maintenance │
746
+ │ Phase 5: Package maintenance │
747
747
  │ → spawn lt-dev:npm-package-maintainer (FULL MODE) │
748
- │ (für Backend UND Frontend package.json) │
748
+ │ (for backend AND frontend package.json) │
749
749
  │ │
750
- │ Phase 6: CLAUDE.md Sync aus Upstream Starters │
750
+ │ Phase 6: CLAUDE.md sync from upstream starters │
751
751
  │ │
752
- │ Phase 7: Cross-Validation (Build + Lint + Tests) │
752
+ │ Phase 7: Cross-validation (build + lint + tests) │
753
753
  │ │
754
- │ Phase 8: Final Report │
754
+ │ Phase 8: Final report │
755
755
  └──────────────────────────────────────────────────────────────────┘
756
756
  ```
757
757
 
758
- **Alle 4 Modus-Kombinationen werden unterstützt:**
758
+ **All 4 mode combinations are supported:**
759
759
 
760
760
  | Backend | Frontend | Backend Agent | Frontend Agent |
761
761
  |---------|----------|---------------|----------------|
@@ -764,179 +764,178 @@ Der **empfohlene** Weg für alle Updates ist `/lt-dev:fullstack:update-all`. Er
764
764
  | vendor | npm | `nest-server-core-updater` | `fullstack-updater --skip-backend` |
765
765
  | vendor | vendor | `nest-server-core-updater` | `nuxt-extensions-core-updater` |
766
766
 
767
- **Skip-Flags:**
767
+ **Skip flags:**
768
768
 
769
769
  ```bash
770
- /lt-dev:fullstack:update-all --dry-run # Nur Plan
771
- /lt-dev:fullstack:update-all --skip-backend # Nur Frontend
772
- /lt-dev:fullstack:update-all --skip-frontend # Nur Backend
773
- /lt-dev:fullstack:update-all --skip-packages # Nur Framework, keine Package-Maintenance
770
+ /lt-dev:fullstack:update-all --dry-run # Plan only
771
+ /lt-dev:fullstack:update-all --skip-backend # Frontend only
772
+ /lt-dev:fullstack:update-all --skip-frontend # Backend only
773
+ /lt-dev:fullstack:update-all --skip-packages # Framework only, no package maintenance
774
774
  ```
775
775
 
776
- **Einzelne Updates** (wenn du nur einen Teil brauchst):
776
+ **Individual updates** (if you only need one part):
777
777
 
778
778
  ```bash
779
- # Backend npm-Mode
779
+ # Backend npm mode
780
780
  /lt-dev:backend:update-nest-server
781
781
 
782
- # Backend vendor-Mode
782
+ # Backend vendor mode
783
783
  /lt-dev:backend:update-nest-server-core
784
784
 
785
- # Frontend vendor-Mode
785
+ # Frontend vendor mode
786
786
  /lt-dev:frontend:update-nuxt-extensions-core
787
787
 
788
- # Nur Packages optimieren
788
+ # Packages only
789
789
  /lt-dev:maintenance:maintain
790
790
  ```
791
791
 
792
792
  ---
793
793
 
794
- ### 7. Upstream-Contribution
794
+ ### 7. Upstream contribution
795
795
 
796
- Wenn du im vendored core **generell nützliche** Änderungen gemacht hast (Bugfixes, Features), können diese als Pull-Request an das Upstream-Repo beigetragen werden.
796
+ If you have made **generally useful** changes to the vendored core (bug fixes, features), they can be contributed back as pull requests to the upstream repo.
797
797
 
798
798
  ```
799
- ┌────────────────────────────────────────────────────────────┐
800
- │ BACKEND: /lt-dev:backend:contribute-nest-server-core │
799
+ ┌──────────────────────────────────────────────────────────┐
800
+ │ BACKEND: /lt-dev:backend:contribute-nest-server-core │
801
801
  │ FRONTEND: /lt-dev:frontend:contribute-nuxt-extensions-core│
802
- │ │
803
- │ Phase 1: git log seit VENDOR.md baseline │
804
- │ Phase 2: Filter cosmetic commits (format, lint) │
805
- │ Phase 3: Categorize: │
806
- │ - upstream-candidate: generic bugfix, framework │
807
- │ enhancement, type correction │
808
- │ - project-specific: business rules, branding │
809
- │ Phase 4: Clone upstream fresh + cherry-pick candidates │
810
- │ Phase 5: Generate PR draft with motivation │
811
- │ Phase 6: Present summary for human review │
812
- │ │
813
- │ Human: reviews + pushes PR via normal GitHub flow │
814
- └────────────────────────────────────────────────────────────┘
802
+ │ │
803
+ │ Phase 1: git log since VENDOR.md baseline │
804
+ │ Phase 2: Filter cosmetic commits (format, lint) │
805
+ │ Phase 3: Categorize: │
806
+ │ - upstream-candidate: generic bugfix, framework │
807
+ │ enhancement, type correction │
808
+ │ - project-specific: business rules, branding │
809
+ │ Phase 4: Clone upstream fresh + cherry-pick candidates │
810
+ │ Phase 5: Generate PR draft with motivation │
811
+ │ Phase 6: Present summary for human review │
812
+ │ │
813
+ │ Human: reviews + pushes PR via normal GitHub flow │
814
+ └──────────────────────────────────────────────────────────┘
815
815
  ```
816
816
 
817
- Nach Merge des PR wird beim nächsten `/lt-dev:backend:update-nest-server-core` bzw. `/lt-dev:frontend:update-nuxt-extensions-core` der Patch als "upstream-delivered" erkannt und aus dem VENDOR.md Local-Changes-Log entfernt.
817
+ After the PR is merged, the next `/lt-dev:backend:update-nest-server-core` or `/lt-dev:frontend:update-nuxt-extensions-core` run will recognize the patch as "upstream-delivered" and remove it from the VENDOR.md local-changes log.
818
818
 
819
819
  ---
820
820
 
821
- ## Entscheidungsmatrix
821
+ ## Decision Matrix
822
822
 
823
- ### Wann npm-Mode?
823
+ ### When to use npm mode?
824
824
 
825
- - ✅ Standard-Projekt ohne lokale Framework-Anpassungen
826
- - ✅ Schnelle Updates via `pnpm update`
827
- - ✅ Weniger komplexe CI/CD
828
- - ✅ Weniger Speicher-Footprint im Repo
825
+ - ✅ Standard project without local framework modifications
826
+ - ✅ Fast updates via `pnpm update`
827
+ - ✅ Simpler CI/CD
828
+ - ✅ Smaller memory footprint in the repo
829
829
 
830
- ### Wann Vendor-Mode?
830
+ ### When to use vendor mode?
831
831
 
832
- - ✅ Claude Code soll den Framework-Code **verstehen** (besseres Kontextverständnis)
833
- - ✅ Lokale Patches am Framework sind erforderlich
834
- - ✅ Upstream-Beiträge sollen aus echter Entwicklung entstehen
835
- - ✅ Debugging in Framework-Code mit Source-Maps / Originalcode
836
- - ✅ Framework-Änderungen sofort testbar ohne npm-Release-Cycle
837
- - ⚠️ Erfordert gelegentliche Merge-Konflikte beim Sync
838
- - ⚠️ Längere Test-Import-Phase (TypeScript source)
832
+ - ✅ Claude Code should **understand** the framework code (better context comprehension)
833
+ - ✅ Local patches to the framework are required
834
+ - ✅ Upstream contributions should emerge from real development
835
+ - ✅ Debugging in framework code with source maps / original code
836
+ - ✅ Framework changes immediately testable without npm release cycle
837
+ - ⚠️ Requires occasional merge conflict handling during sync
838
+ - ⚠️ Longer test import phase (TypeScript source)
839
839
 
840
840
  ---
841
841
 
842
- ## Glossar
842
+ ## Glossary
843
843
 
844
- | Begriff | Bedeutung |
845
- |---------|-----------|
846
- | **npm-Mode** | Framework als `@lenne.tech/nest-server` / `@lenne.tech/nuxt-extensions` npm-Dependency |
847
- | **Vendor-Mode** | Framework-Source kopiert in `src/core/` (Backend) bzw. `app/core/` (Frontend) |
848
- | **VENDOR.md** | Marker-Datei im vendored core mit Baseline-Version, Sync-Historie, Local-Patches |
849
- | **Flatten-Fix** | Import-Path-Rewrites in 4 Backend-Dateien nach dem Kopieren (nur Backend) |
850
- | **Consumer-Import-Codemod** | Rewrite von `@lenne.tech/nest-server` zu relativen Pfaden in Projekt-Code |
851
- | **Upstream-Sync** | Pull von Upstream-Änderungen ins vendored core |
852
- | **Upstream-Contribution** | Push von lokalen Patches als PR zum Upstream-Repo |
853
- | **Mode-aware** | Code der automatisch korrekte Pfade für npm oder vendor wählt |
854
- | **Starter** | `nest-server-starter` / `nuxt-base-starter` — Template-Repo mit Standard-Config |
844
+ | Term | Meaning |
845
+ |------|---------|
846
+ | **npm mode** | Framework as `@lenne.tech/nest-server` / `@lenne.tech/nuxt-extensions` npm dependency |
847
+ | **Vendor mode** | Framework source copied into `src/core/` (backend) or `app/core/` (frontend) |
848
+ | **VENDOR.md** | Marker file in the vendored core with baseline version, sync history, local patches |
849
+ | **Flatten-fix** | Import path rewrites in 4 backend files after copying (backend only) |
850
+ | **Consumer-import codemod** | Rewrite of `@lenne.tech/nest-server` to relative paths in project code |
851
+ | **Upstream sync** | Pulling upstream changes into the vendored core |
852
+ | **Upstream contribution** | Pushing local patches as PR to the upstream repo |
853
+ | **Mode-aware** | Code that automatically chooses correct paths for npm or vendor |
854
+ | **Starter** | `nest-server-starter` / `nuxt-base-starter` — template repo with standard config |
855
855
 
856
856
  ---
857
857
 
858
- ## Quellen & Referenzen
858
+ ## Sources & References
859
859
 
860
- ### GitHub-Repos
860
+ ### GitHub repos
861
861
 
862
862
  | Repo | URL |
863
863
  |------|-----|
864
864
  | lt CLI | https://github.com/lenneTech/cli |
865
865
  | lt-dev Plugin | https://github.com/lenneTech/claude-code |
866
- | nest-server Framework | https://github.com/lenneTech/nest-server |
867
- | nest-server Starter | https://github.com/lenneTech/nest-server-starter |
868
- | nuxt-extensions Module | https://github.com/lenneTech/nuxt-extensions |
869
- | nuxt-base Starter | https://github.com/lenneTech/nuxt-base-starter |
870
- | lt-monorepo Template | https://github.com/lenneTech/lt-monorepo |
866
+ | nest-server framework | https://github.com/lenneTech/nest-server |
867
+ | nest-server starter | https://github.com/lenneTech/nest-server-starter |
868
+ | nuxt-extensions module | https://github.com/lenneTech/nuxt-extensions |
869
+ | nuxt-base starter | https://github.com/lenneTech/nuxt-base-starter |
870
+ | lt-monorepo template | https://github.com/lenneTech/lt-monorepo |
871
871
 
872
- ### Lokale Dokumentation
872
+ ### Local documentation
873
873
 
874
- - `cli/CLAUDE.md` — CLI-interne Dokumentation + Vendor-Touchpoints-Tabelle
875
- - `cli/docs/commands.md` — CLI Command-Reference
876
- - `cli/docs/lt.config.md` — CLI Config-Reference
877
- - `cli/scripts/test-vendor-init.sh` — Backend-Vendor-Integration-Tests (4 Szenarien × ~22 Assertions)
878
- - `cli/scripts/test-frontend-vendor-init.sh` — Frontend-Vendor-Integration-Tests (4 Szenarien)
879
- - `framework-vendoring-pilot-plan.md` — Original Vendor-Mode Blueprint
874
+ - `cli/CLAUDE.md` — CLI internal documentation + vendor touchpoints table
875
+ - `cli/docs/commands.md` — CLI command reference
876
+ - `cli/docs/lt.config.md` — CLI config reference
877
+ - `cli/scripts/test-vendor-init.sh` — Backend vendor integration tests (4 scenarios × ~22 assertions)
878
+ - `cli/scripts/test-frontend-vendor-init.sh` — Frontend vendor integration tests (4 scenarios)
880
879
 
881
880
  ---
882
881
 
883
- ## Schnellreferenz — Die wichtigsten Commands
882
+ ## Quick Reference — The Most Important Commands
884
883
 
885
884
  ```bash
886
885
  # ═══════════════════════════════════════════════════════════════
887
- # PROJEKT-SETUP
886
+ # PROJECT SETUP
888
887
  # ═══════════════════════════════════════════════════════════════
889
888
 
890
- # Neues Projekt (beide im vendor mode)
889
+ # New project (both in vendor mode)
891
890
  lt fullstack init --name <n> --frontend nuxt --api-mode Rest \
892
891
  --framework-mode vendor --frontend-framework-mode vendor --noConfirm
893
892
 
894
- # Neues Projekt (npm mode, Standard)
893
+ # New project (npm mode, standard)
895
894
  lt fullstack init --name <n> --frontend nuxt --api-mode Rest --noConfirm
896
895
 
897
- # Status checken (zeigt beide Modi im Monorepo-Root)
896
+ # Check status (shows both modes at monorepo root)
898
897
  lt status
899
898
 
900
899
  # ═══════════════════════════════════════════════════════════════
901
- # KONVERTIERUNG — Fullstack (beide Subprojekte in einem Schritt)
900
+ # CONVERSION — Fullstack (both subprojects in one step)
902
901
  # ═══════════════════════════════════════════════════════════════
903
902
 
904
- # Beide Subprojekte: npm → vendor (vom Monorepo-Root)
903
+ # Both subprojects: npm → vendor (from monorepo root)
905
904
  lt fullstack convert-mode --to vendor --noConfirm
906
905
 
907
- # Beide Subprojekte: vendor → npm (Rückführung)
906
+ # Both subprojects: vendor → npm (rollback)
908
907
  lt fullstack convert-mode --to npm --noConfirm
909
908
 
910
- # Mit spezifischen Upstream-Versionen
909
+ # With specific upstream versions
911
910
  lt fullstack convert-mode --to vendor \
912
911
  --framework-upstream-branch 11.24.3 \
913
912
  --frontend-framework-upstream-branch 1.5.3 \
914
913
  --noConfirm
915
914
 
916
- # Nur Backend bzw. nur Frontend
915
+ # Only backend or only frontend
917
916
  lt fullstack convert-mode --to vendor --skip-frontend --noConfirm
918
917
  lt fullstack convert-mode --to vendor --skip-backend --noConfirm
919
918
 
920
- # Dry-run (Plan ohne Änderungen)
919
+ # Dry-run (plan without changes)
921
920
  lt fullstack convert-mode --to vendor --dry-run
922
921
 
923
922
  # ═══════════════════════════════════════════════════════════════
924
- # KONVERTIERUNG — Einzeln (in den jeweiligen Subprojekten)
923
+ # CONVERSION — Individual (in the respective subprojects)
925
924
  # ═══════════════════════════════════════════════════════════════
926
925
 
927
- # Backend: npm → vendor (mit Migrations via Claude Code)
926
+ # Backend: npm → vendor (with migrations via Claude Code)
928
927
  /lt-dev:backend:convert-to-vendor
929
928
 
930
- # Backend: npm → vendor (direkt via CLI)
929
+ # Backend: npm → vendor (directly via CLI)
931
930
  cd projects/api && lt server convert-mode --to vendor
932
931
 
933
- # Frontend: npm → vendor (mit Changelog via Claude Code)
932
+ # Frontend: npm → vendor (with changelog via Claude Code)
934
933
  /lt-dev:frontend:convert-to-vendor
935
934
 
936
- # Frontend: npm → vendor (direkt via CLI)
935
+ # Frontend: npm → vendor (directly via CLI)
937
936
  cd projects/app && lt frontend convert-mode --to vendor
938
937
 
939
- # Rückführung einzeln
938
+ # Rollback individually
940
939
  cd projects/api && lt server convert-mode --to npm
941
940
  cd projects/app && lt frontend convert-mode --to npm
942
941
 
@@ -944,30 +943,30 @@ cd projects/app && lt frontend convert-mode --to npm
944
943
  # UPDATES
945
944
  # ═══════════════════════════════════════════════════════════════
946
945
 
947
- # Comprehensive Fullstack Update (empfohlen, mode-aware)
946
+ # Comprehensive fullstack update (recommended, mode-aware)
948
947
  /lt-dev:fullstack:update-all
949
948
 
950
- # Nur Backend
949
+ # Backend only
951
950
  /lt-dev:backend:update-nest-server # npm mode
952
951
  /lt-dev:backend:update-nest-server-core # vendor mode
953
952
 
954
- # Nur Frontend
953
+ # Frontend only
955
954
  /lt-dev:frontend:update-nuxt-extensions-core # vendor mode
956
955
 
957
- # Nur Packages
956
+ # Packages only
958
957
  /lt-dev:maintenance:maintain
959
958
 
960
959
  # ═══════════════════════════════════════════════════════════════
961
960
  # UPSTREAM CONTRIBUTION
962
961
  # ═══════════════════════════════════════════════════════════════
963
962
 
964
- # Backend: Lokale Patches als PR vorbereiten
963
+ # Backend: prepare local patches as PR
965
964
  /lt-dev:backend:contribute-nest-server-core
966
965
 
967
- # Frontend: Lokale Patches als PR vorbereiten
966
+ # Frontend: prepare local patches as PR
968
967
  /lt-dev:frontend:contribute-nuxt-extensions-core
969
968
  ```
970
969
 
971
970
  ---
972
971
 
973
- *Diese Datei ist als lebende Dokumentation gedacht. Bei neuen Funktionen im lt-CLI oder lt-dev Plugin sollte sie aktualisiert werden.*
972
+ *This file is intended as living documentation. It should be updated when new features are added to the lt CLI or lt-dev plugin.*