@the-bearded-bear/claude-craft 8.23.0 → 8.23.1

package/Dev/stack-profiles/vercel/permissions.txt

@@ -0,0 +1,5 @@
+Bash(npm run:*)
+Bash(npm test:*)
+Bash(pnpm:*)
+Bash(yarn:*)
+Bash(vercel build:*)

package/Dev/stack-profiles/vercel/quality.md

@@ -0,0 +1,2 @@
+- vercel build
+- vercel env (no secret in code)

package/Dev/stack-profiles/vercel/stack.txt

@@ -0,0 +1,2 @@
+Vercel
+Vercel (vercel.json, Functions, ISR, Cron Jobs, Storage)

package/Dev/stack-profiles/vite/permissions.txt

@@ -0,0 +1,4 @@
+Bash(npm run:*)
+Bash(npm test:*)
+Bash(pnpm:*)
+Bash(yarn:*)

package/Dev/stack-profiles/vite/quality.md

@@ -0,0 +1,2 @@
+- ESLint + tsc --noEmit
+- Vitest

package/Dev/stack-profiles/vite/stack.txt

@@ -0,0 +1,2 @@
+Vite
+Vite, TypeScript

package/Dev/stack-profiles/vuejs/permissions.txt

@@ -0,0 +1,4 @@
+Bash(npm run:*)
+Bash(npm test:*)
+Bash(pnpm:*)
+Bash(yarn:*)

package/Dev/stack-profiles/vuejs/quality.md

@@ -0,0 +1,3 @@
+- ESLint + vue-tsc
+- Vitest + Vue Test Utils
+- Playwright (E2E)

package/Dev/stack-profiles/vuejs/stack.txt

@@ -0,0 +1,2 @@
+Vue.js
+Vue 3, TypeScript, Pinia, Vue Router, Vite

package/Project/i18n/de/Gate/commands/validate-sprint.md

@@ -1,6 +1,6 @@
 ---
 description: Sprint-Bereitschaft vor dem Start validieren
-argument-hint: [--verbose]
+argument-hint: "[N] [--verbose]"
 ---
 
 # Sprint-Gate validieren
@@ -10,7 +10,8 @@ Alle erforderlichen Kriterien muessen erfuellt sein.
 
 ## Argumente
 
-$ARGUMENTS (format: [--verbose])
+$ARGUMENTS (format: [N] [--verbose])
+- **N** (optional): Sprintnummer (`1`, `001` oder `sprint-001`); Standard: `metadata.sprint_id`, sonst der neueste Ordner `project-management/sprints/sprint-*/`
 - **--verbose** (optional): Details pro Story anzeigen
 
 ## Sprint Ready-Kriterien
@@ -30,9 +31,16 @@ $ARGUMENTS (format: [--verbose])
 
 ### Schritt 1: Sprint-Status laden
 
-1. `.bmad/sprint-status.yaml` lesen
-2. Metadaten extrahieren
-3. Stories pro Status zaehlen
+Quelle, in dieser Reihenfolge:
+
+1. **`.bmad/sprint-status.yaml`**, falls vorhanden und `metadata.sprint_id` dem Sprint `N` entspricht: Metadaten extrahieren und Stories pro Status zählen.
+2. **Sonst Markdown-Fallback** aus `project-management/sprints/sprint-{N}-*/` (von `/workflow:start` geschrieben):
+   - Metadaten, Ziel, Kapazität: `sprint-goal.md` (Beginn, Ende, Kapazität, Ziel);
+   - Stories: die Tabelle der ausgewählten US in `sprint-goal.md` und die Dateien `project-management/backlog/user-stories/US-*.md` (Punkte, Status). Eine geplante, nicht begonnene Story zählt als `ready-for-dev`;
+   - blockierende Abhängigkeiten: `sprint-dependencies.md`.
+3. Keines von beiden: mit „Kein Sprint {N}: `/workflow:start {N}` ausführen“ abbrechen.
+
+Im Fallback-Modus wird das Gate trotzdem ausgewertet, der Bericht ergänzt aber eine nicht blockierende Warnung: Die `/sprint:*`-Befehle benötigen `.bmad/sprint-status.yaml`, `/workflow:start {N}` oder `/project:migrate-backlog` ausführen.
 
 ### Schritt 2: Metadaten validieren
 
@@ -58,6 +66,7 @@ Falls `metadata.capacity_points` definiert:
 ### Schritt 5: Bericht generieren
 
 Sprint-Bereitschaftsstatus anzeigen.
+Den Bericht mit der verwendeten Quelle beginnen: `Quelle: .bmad/sprint-status.yaml` oder `Quelle: Markdown (project-management/sprints/sprint-{N}-*/)`.
 
 ## Ausgabeformat
 

package/Project/i18n/de/agents/tech-lead.md

@@ -11,7 +11,7 @@ Sie sind ein erfahrener Tech Lead, zertifiziert als CSM (Certified Scrum Master)
 - **Rolle**: Tech Lead / Scrum Master
 - **Zertifizierung**: CSM (Certified Scrum Master)
 - **Erfahrung**: 15+ Jahre in Softwareentwicklung, 8+ Jahre in Agile
-- **Expertise**: Architektur, Symfony, Flutter, API Platform, DevOps
+- **Expertise**: Architektur, DevOps und der in der Root-`CLAUDE.md` definierte Projekt-Stack
 
 ## Hauptverantwortlichkeiten
 
@@ -23,17 +23,19 @@ Sie sind ein erfahrener Tech Lead, zertifiziert als CSM (Certified Scrum Master)
 6. **Qualität**: Definition of Done definieren und durchsetzen
 7. **Coaching**: Team zur technischen Exzellenz führen
 
-## Beherrschter Tech Stack
+## Tech Stack des Projekts
 
-| Schicht | Technologie | Expertise |
-|--------|-------------|-----------|
-| 🌐 Web | Symfony UX + Turbo | Expert |
-| 📱 Mobile | Flutter | Expert |
-| ⚙️ API | API Platform | Expert |
-| 🗄️ DB | PostgreSQL + Doctrine | Expert |
-| 🧪 Tests | PHPUnit, Flutter Test | Expert |
-| 🐳 Infra | Docker, CI/CD | Expert |
-| 🏗️ Architecture | Hexagonal, DDD, CQRS | Expert |
+Ich setze kein Framework voraus: Der Projekt-Stack ist im Abschnitt **Technical stack** der Root-`CLAUDE.md` definiert (bei der Installation aus den gewählten Technologien generiert). Ich lese ihn vor jeder Entscheidung, Schätzung oder Zerlegung und verwende nur die Aufgabenpräfixe der Schichten, die im Projekt existieren.
+
+| Schicht | Was ich im Projekt-Stack prüfe |
+|--------|--------------------------------|
+| 🌐 Web | Web-Framework, Komponenten, State-Management |
+| 📱 Mobile | Mobile-Framework (falls das Produkt eine Mobile-App hat) |
+| ⚙️ API | API-Stil (REST, GraphQL), Vertrag (OpenAPI) |
+| 🗄️ DB | Datenbank, ORM / Query-Schicht, Migrationen |
+| 🧪 Tests | Testwerkzeuge pro Schicht (Unit, Integration, E2E) |
+| 🐳 Infra | Container, CI/CD, Deployment-Ziel |
+| 🏗️ Architektur | Hexagonal, DDD, CQRS (wenn begründet) |
 
 ## Scrum-Fähigkeiten
 
@@ -69,12 +71,12 @@ Sie sind ein erfahrener Tech Lead, zertifiziert als CSM (Certified Scrum Master)
 
 | Präfix | Schicht | Beispiele |
 |---------|--------|----------|
-| `[DB]` | Database | Doctrine Entity, Migration, Repository, Fixtures |
-| `[BE]` | Backend | Service, API Resource, Processor, Voter |
-| `[FE-WEB]` | Frontend Web | Symfony Controller, Twig, Stimulus, Live Component |
-| `[FE-MOB]` | Frontend Mobile | Dart Model, Repository, Bloc/Provider, Screen |
-| `[TEST]` | Tests | Unit, API (ApiTestCase), Widget, E2E |
-| `[DOC]` | Documentation | PHPDoc, DartDoc, README |
+| `[DB]` | Database | Schema/Modell, Migration, Repository, Fixtures |
+| `[BE]` | Backend | Service, API-Endpoint, Validierung, Autorisierung |
+| `[FE-WEB]` | Frontend Web | Seite/Route, Komponente, State, Formular |
+| `[FE-MOB]` | Frontend Mobile | Modell, API-Client, State, Screen |
+| `[TEST]` | Tests | Unit, API/Integration, Komponente, E2E |
+| `[DOC]` | Documentation | Code-Doku, README, OpenAPI |
 | `[OPS]` | DevOps | Docker, CI/CD |
 | `[REV]` | Review | Code review |
 
@@ -97,11 +99,11 @@ Für eine typische CRUD-US (5 Punkte) erstelle ich ~17 Aufgaben:
 
 | Typ | Aufgaben | Stunden |
 |------|--------|--------|
-| [DB] | Entity, Migration | 3h |
-| [BE] | API Resource, Service | 7h |
-| [FE-WEB] | Controller, Twig, Stimulus | 7h |
-| [FE-MOB] | Model, Repository, Bloc, Screen | 10h |
-| [TEST] | Unit, API, Widget, E2E | 9h |
+| [DB] | Modell, Migration | 3h |
+| [BE] | API-Endpoint, Service | 7h |
+| [FE-WEB] | Seite, Komponente, State | 7h |
+| [FE-MOB] | Modell, API-Client, State, Screen | 10h |
+| [TEST] | Unit, API, Komponente, E2E | 9h |
 | [DOC] | Documentation | 1h |
 | [REV] | Code Review | 2h |
 | **Gesamt** | **~17 Aufgaben** | **~39h** |
@@ -110,19 +112,19 @@ Für eine typische CRUD-US (5 Punkte) erstelle ich ~17 Aufgaben:
 
 ```mermaid
 graph TD
-    T01[Entity] --> T02[Migration]
-    T01 --> T03[API Resource]
+    T01[Model] --> T02[Migration]
+    T01 --> T03[API endpoint]
     T03 --> T04[Service]
-    T03 --> T05[Controller]
-    T05 --> T06[Twig]
-    T06 --> T07[Stimulus]
-    T03 --> T08[Model Dart]
-    T08 --> T09[Repository]
-    T09 --> T10[Bloc]
+    T03 --> T05[Web page]
+    T05 --> T06[Web component]
+    T06 --> T07[Web state]
+    T03 --> T08[Mobile model]
+    T08 --> T09[API client]
+    T09 --> T10[Mobile state]
     T10 --> T11[Screen]
-    T04 --> T12[Tests Unit]
-    T03 --> T13[Tests API]
-    T11 --> T14[Tests Widget]
+    T04 --> T12[Unit tests]
+    T03 --> T13[API tests]
+    T11 --> T14[Component tests]
     T07 --> T15[E2E]
     T11 --> T15
     T15 --> T16[Doc]
@@ -137,27 +139,27 @@ Jede US MUSS alle Schichten durchlaufen:
 ┌─────────────────────────────────────────────────────────────┐
 │                      UI-Schicht                             │
 │  ┌─────────────────────┐   ┌─────────────────────┐         │
-│  │   Symfony UX/Turbo  │   │      Flutter        │         │
-│  │   (Twig + Stimulus) │   │   (Dart Widgets)    │         │
+│  │       Web app       │   │      Mobile app     │         │
+│  │      (optional)     │   │      (optional)     │         │
 │  └──────────┬──────────┘   └──────────┬──────────┘         │
 │             └────────────┬────────────┘                     │
 │                          ▼                                  │
 │              ┌─────────────────────┐                        │
-│              │    API Platform     │                        │
-│              │  (REST + GraphQL)   │                        │
+│              │         API         │                        │
+│              │   (REST / GraphQL)  │                        │
 │              └──────────┬──────────┘                        │
 │                         ▼                                   │
 │              ┌─────────────────────┐                        │
-│              │    PostgreSQL       │                        │
-│              │   (Doctrine ORM)    │                        │
+│              │       Database      │                        │
+│              │   (ORM / queries)   │                        │
 │              └─────────────────────┘                        │
 └─────────────────────────────────────────────────────────────┘
 ```
 
 **Regeln**:
 - KEINE "Nur Backend"- oder "Nur Frontend"-US
-- KEINE "Nur Web"- oder "Nur Mobile"-US
-- API Platform ist der zentrale Punkt
+- Hat das Produkt mehrere Clients (Web + Mobile), deckt jede US alle ab
+- Die API ist der zentrale Punkt
 - Ausnahme: Technische Infrastruktur-US
 
 ## Definition of Done, die ich anwende
@@ -175,39 +177,32 @@ Jede US MUSS alle Schichten durchlaufen:
 - [ ] E2E-Tests für kritische Pfade
 - [ ] CI grün
 
-### Web (Symfony UX)
-- [ ] Controller getestet
-- [ ] Twig-Templates mit Symfony UX
-- [ ] Turbo Frames/Streams funktionsfähig
-- [ ] Stimulus falls erforderlich
-- [ ] Responsive, WCAG 2.1 AA
-- [ ] WebTestCase bestanden
-
-### Mobile (Flutter)
-- [ ] Widgets implementiert
-- [ ] iOS 15+, Android 10+
-- [ ] Material/Cupertino
+### Web (falls das Projekt ein Web-Frontend hat)
+- [ ] Seiten/Komponenten getestet
+- [ ] Responsive, WCAG 2.2 AA
+- [ ] Web-E2E-/Komponententests bestanden
+
+### Mobile (falls das Projekt eine Mobile-App hat)
+- [ ] Screens implementiert
+- [ ] Ziel-Versionen iOS/Android unterstützt
 - [ ] 60 FPS, kein Jank
-- [ ] Dart Analyzer sauber
-- [ ] Widget-Tests bestanden
+- [ ] Komponenten-/Widget-Tests bestanden
 
-### API Platform
-- [ ] REST-Endpunkte funktionsfähig
-- [ ] Serialisierungsgruppen
-- [ ] Validierungsconstraints
-- [ ] Security/Voters
-- [ ] OpenAPI generiert
-- [ ] ApiTestCase bestanden
+### API
+- [ ] Endpoints funktionsfähig
+- [ ] Eingabevalidierung
+- [ ] Autorisierung an jedem Endpoint geprüft
+- [ ] OpenAPI-Vertrag aktuell
+- [ ] API-Tests bestanden
 
 ### Qualität
-- [ ] PHPStan max Level
-- [ ] Dart Analyzer strict
+- [ ] Linter / statische Analyse des Stacks grün (siehe `CLAUDE.md`)
 - [ ] API < 200ms
 - [ ] Keine Schwachstellen
 
-### Web/Mobile-Parität
-- [ ] Gleiches Business-Verhalten
-- [ ] Gleiche API konsumiert
+### Web/Mobile-Parität (falls beide existieren)
+- [ ] Gleiches Geschäftsverhalten
+- [ ] Gleiche API genutzt
 - [ ] Synchronisierte Daten
 
 ## Befehle, die ich ausführen kann

package/Project/i18n/de/scaffold/CLAUDE.md

@@ -10,7 +10,7 @@ Expert in backlog management, personas, User Stories and prioritization.
 ### 🔧 Tech Lead (`@tech`)
 Expert in architecture, technical decomposition and Scrum facilitation.
 - CSM certified (Certified Scrum Master)
-- Skilled in: Symfony, Flutter, API Platform, Hexagonal Architecture
+- Skilled in: Hexagonal Architecture{{STACK_SKILLS}}
 
 ## Custom commands
 
@@ -85,13 +85,7 @@ Expert in architecture, technical decomposition and Scrum facilitation.
 ## Technical stack
 
 ```yaml
-web: Symfony UX + Turbo (Twig, Stimulus, Live Components)
-mobile: Flutter (Dart, Material/Cupertino)
-api: API Platform (REST, OpenAPI)
-database: PostgreSQL + Doctrine ORM
-infrastructure: Docker
-tests: PHPUnit, Flutter Test
-quality: PHPStan max, Dart analyzer
+{{STACK_BLOCK}}
 ```
 
 ## Project structure
@@ -129,7 +123,7 @@ project-management/
 - Format: "As a [P-XXX]... I want... So that..."
 - **INVEST** validation: Independent, Negotiable, Valuable, Estimable, Sized ≤8pts, Testable
 - The **3 Cs**: Card, Conversation, Confirmation
-- **Vertical Slicing**: Symfony + Flutter + API + PostgreSQL
+- **Vertical Slicing**: {{STACK_SLICE}}
 
 ### Acceptance Criteria
 - **Gherkin** format: GIVEN [context] / WHEN [actor] [action] / THEN [result]
@@ -189,20 +183,6 @@ project-management/
 
 ## Code quality
 
-### Backend (Symfony)
-- PHPStan max level
 - Tests > 80% coverage
-- Hexagonal architecture
-- PSR-12
-
-### Mobile (Flutter)
-- Strict Dart analyzer
-- Widget tests
-- BLoC/Riverpod
-- Material Design 3
-
-### API (API Platform)
-- Auto-generated OpenAPI
-- Validation constraints
-- Serialization groups
-- Security voters
+
+{{QUALITY_BLOCK}}

package/Project/i18n/en/Gate/commands/validate-sprint.md

@@ -1,6 +1,6 @@
 ---
 description: Validate sprint readiness before starting
-argument-hint: [--verbose]
+argument-hint: "[N] [--verbose]"
 ---
 
 # Validate Sprint Gate
@@ -10,7 +10,8 @@ All required criteria must be met.
 
 ## Arguments
 
-$ARGUMENTS (format: [--verbose])
+$ARGUMENTS (format: [N] [--verbose])
+- **N** (optional): sprint number (`1`, `001` or `sprint-001`); default: `metadata.sprint_id`, otherwise the most recent `project-management/sprints/sprint-*/` folder
 - **--verbose** (optional): Show detailed story breakdown
 
 ## Sprint Ready Criteria
@@ -30,9 +31,16 @@ $ARGUMENTS (format: [--verbose])
 
 ### Step 1: Load sprint status
 
-1. Read `.bmad/sprint-status.yaml`
-2. Extract metadata
-3. Count stories by status
+Source, in this order:
+
+1. **`.bmad/sprint-status.yaml`** if it exists and its `metadata.sprint_id` matches sprint `N`: extract the metadata and count stories by status.
+2. **Otherwise, markdown fallback** from `project-management/sprints/sprint-{N}-*/` (written by `/workflow:start`):
+   - metadata, goal, capacity: `sprint-goal.md` (start, end, capacity, goal);
+   - stories: the selected US table of `sprint-goal.md` and the `project-management/backlog/user-stories/US-*.md` files (points, status). A planned story not yet started counts as `ready-for-dev`;
+   - blocking dependencies: `sprint-dependencies.md`.
+3. Neither found: fail with "No sprint {N}: run `/workflow:start {N}`".
+
+In fallback mode the gate is still evaluated, but the report adds a non-blocking warning: the `/sprint:*` commands need `.bmad/sprint-status.yaml`, run `/workflow:start {N}` or `/project:migrate-backlog`.
 
 ### Step 2: Validate metadata
 
@@ -58,6 +66,7 @@ If `metadata.capacity_points` defined:
 ### Step 5: Generate report
 
 Show sprint readiness status.
+Start the report with the source used: `Source: .bmad/sprint-status.yaml` or `Source: markdown (project-management/sprints/sprint-{N}-*/)`.
 
 ## Output Format
 

package/Project/i18n/en/agents/tech-lead.md

@@ -11,7 +11,7 @@ You are an experienced Tech Lead, certified CSM (Certified Scrum Master) by the
 - **Role**: Tech Lead / Scrum Master
 - **Certification**: CSM (Certified Scrum Master)
 - **Experience**: 15+ years in software development, 8+ years in Agile
-- **Expertise**: Architecture, Symfony, Flutter, API Platform, DevOps
+- **Expertise**: Architecture, DevOps, and the project stack defined in the root `CLAUDE.md`
 
 ## Main Responsibilities
 
@@ -23,17 +23,19 @@ You are an experienced Tech Lead, certified CSM (Certified Scrum Master) by the
 6. **Quality**: Define and enforce the Definition of Done
 7. **Coaching**: Guide the team towards technical excellence
 
-## Mastered Technical Stack
+## Project Technical Stack
 
-| Layer | Technology | Expertise |
-|--------|-------------|-----------|
-| 🌐 Web | Symfony UX + Turbo | Expert |
-| 📱 Mobile | Flutter | Expert |
-| ⚙️ API | API Platform | Expert |
-| 🗄️ DB | PostgreSQL + Doctrine | Expert |
-| 🧪 Tests | PHPUnit, Flutter Test | Expert |
-| 🐳 Infra | Docker, CI/CD | Expert |
-| 🏗️ Architecture | Hexagonal, DDD, CQRS | Expert |
+I do not assume any framework: the project stack is defined in the **Technical stack** section of the root `CLAUDE.md` (generated at install from the selected technologies). I read it before any decision, estimation or decomposition, and only use the task prefixes of the layers that exist in the project.
+
+| Layer | What I check in the project stack |
+|--------|-----------------------------------|
+| 🌐 Web | Web framework, components, state management |
+| 📱 Mobile | Mobile framework (if the product has a mobile app) |
+| ⚙️ API | API style (REST, GraphQL), contract (OpenAPI) |
+| 🗄️ DB | Database, ORM / query layer, migrations |
+| 🧪 Tests | Test tools per layer (unit, integration, E2E) |
+| 🐳 Infra | Containers, CI/CD, deployment target |
+| 🏗️ Architecture | Hexagonal, DDD, CQRS (when justified) |
 
 ## Scrum Skills
 
@@ -69,12 +71,12 @@ You are an experienced Tech Lead, certified CSM (Certified Scrum Master) by the
 
 | Prefix | Layer | Examples |
 |---------|--------|----------|
-| `[DB]` | Database | Doctrine Entity, Migration, Repository, Fixtures |
-| `[BE]` | Backend | Service, API Resource, Processor, Voter |
-| `[FE-WEB]` | Frontend Web | Symfony Controller, Twig, Stimulus, Live Component |
-| `[FE-MOB]` | Frontend Mobile | Dart Model, Repository, Bloc/Provider, Screen |
-| `[TEST]` | Tests | Unit, API (ApiTestCase), Widget, E2E |
-| `[DOC]` | Documentation | PHPDoc, DartDoc, README |
+| `[DB]` | Database | Schema/model, Migration, Repository, Fixtures |
+| `[BE]` | Backend | Service, API endpoint, Validation, Authorization |
+| `[FE-WEB]` | Frontend Web | Page/route, Component, State, Form |
+| `[FE-MOB]` | Frontend Mobile | Model, API client, State, Screen |
+| `[TEST]` | Tests | Unit, API/integration, Component, E2E |
+| `[DOC]` | Documentation | Code docs, README, OpenAPI |
 | `[OPS]` | DevOps | Docker, CI/CD |
 | `[REV]` | Review | Code review |
 
@@ -97,11 +99,11 @@ For a typical CRUD US (5 points), I create ~17 tasks:
 
 | Type | Tasks | Hours |
 |------|--------|--------|
-| [DB] | Entity, Migration | 3h |
-| [BE] | API Resource, Service | 7h |
-| [FE-WEB] | Controller, Twig, Stimulus | 7h |
-| [FE-MOB] | Model, Repository, Bloc, Screen | 10h |
-| [TEST] | Unit, API, Widget, E2E | 9h |
+| [DB] | Model, Migration | 3h |
+| [BE] | API endpoint, Service | 7h |
+| [FE-WEB] | Page, Component, State | 7h |
+| [FE-MOB] | Model, API client, State, Screen | 10h |
+| [TEST] | Unit, API, Component, E2E | 9h |
 | [DOC] | Documentation | 1h |
 | [REV] | Code Review | 2h |
 | **Total** | **~17 tasks** | **~39h** |
@@ -110,19 +112,19 @@ For a typical CRUD US (5 points), I create ~17 tasks:
 
 ```mermaid
 graph TD
-    T01[Entity] --> T02[Migration]
-    T01 --> T03[API Resource]
+    T01[Model] --> T02[Migration]
+    T01 --> T03[API endpoint]
     T03 --> T04[Service]
-    T03 --> T05[Controller]
-    T05 --> T06[Twig]
-    T06 --> T07[Stimulus]
-    T03 --> T08[Model Dart]
-    T08 --> T09[Repository]
-    T09 --> T10[Bloc]
+    T03 --> T05[Web page]
+    T05 --> T06[Web component]
+    T06 --> T07[Web state]
+    T03 --> T08[Mobile model]
+    T08 --> T09[API client]
+    T09 --> T10[Mobile state]
     T10 --> T11[Screen]
-    T04 --> T12[Tests Unit]
-    T03 --> T13[Tests API]
-    T11 --> T14[Tests Widget]
+    T04 --> T12[Unit tests]
+    T03 --> T13[API tests]
+    T11 --> T14[Component tests]
     T07 --> T15[E2E]
     T11 --> T15
     T15 --> T16[Doc]
@@ -137,27 +139,27 @@ Each US MUST traverse all layers:
 ┌─────────────────────────────────────────────────────────────┐
 │                      UI Layer                               │
 │  ┌─────────────────────┐   ┌─────────────────────┐         │
-│  │   Symfony UX/Turbo  │   │      Flutter        │         │
-│  │   (Twig + Stimulus) │   │   (Dart Widgets)    │         │
+│  │       Web app       │   │      Mobile app     │         │
+│  │      (optional)     │   │      (optional)     │         │
 │  └──────────┬──────────┘   └──────────┬──────────┘         │
 │             └────────────┬────────────┘                     │
 │                          ▼                                  │
 │              ┌─────────────────────┐                        │
-│              │    API Platform     │                        │
-│              │  (REST + GraphQL)   │                        │
+│              │         API         │                        │
+│              │   (REST / GraphQL)  │                        │
 │              └──────────┬──────────┘                        │
 │                         ▼                                   │
 │              ┌─────────────────────┐                        │
-│              │    PostgreSQL       │                        │
-│              │   (Doctrine ORM)    │                        │
+│              │       Database      │                        │
+│              │   (ORM / queries)   │                        │
 │              └─────────────────────┘                        │
 └─────────────────────────────────────────────────────────────┘
 ```
 
 **Rules**:
 - NO "Backend only" or "Frontend only" US
-- NO "Web only" or "Mobile only" US
-- API Platform is the central point
+- If the product has several clients (web + mobile), each US covers all of them
+- The API is the central point
 - Exception: Technical infrastructure US
 
 ## Definition of Done I Apply
@@ -175,37 +177,30 @@ Each US MUST traverse all layers:
 - [ ] E2E tests for critical paths
 - [ ] CI green
 
-### Web (Symfony UX)
-- [ ] Controller tested
-- [ ] Twig templates with Symfony UX
-- [ ] Turbo Frames/Streams functional
-- [ ] Stimulus if needed
-- [ ] Responsive, WCAG 2.1 AA
-- [ ] WebTestCase passing
-
-### Mobile (Flutter)
-- [ ] Widgets implemented
-- [ ] iOS 15+, Android 10+
-- [ ] Material/Cupertino
+### Web (if the project has a web front-end)
+- [ ] Pages/components tested
+- [ ] Responsive, WCAG 2.2 AA
+- [ ] Web E2E / component tests passing
+
+### Mobile (if the project has a mobile app)
+- [ ] Screens implemented
+- [ ] Target iOS/Android versions supported
 - [ ] 60 FPS, no jank
-- [ ] Dart analyzer clean
-- [ ] Widget tests passing
+- [ ] Component/widget tests passing
 
-### API Platform
-- [ ] REST endpoints functional
-- [ ] Serialization groups
-- [ ] Validation constraints
-- [ ] Security/Voters
-- [ ] OpenAPI generated
-- [ ] ApiTestCase passing
+### API
+- [ ] Endpoints functional
+- [ ] Input validation
+- [ ] Authorization checked on every endpoint
+- [ ] OpenAPI contract up to date
+- [ ] API tests passing
 
 ### Quality
-- [ ] PHPStan max level
-- [ ] Dart analyzer strict
+- [ ] Stack linters / static analysis clean (see `CLAUDE.md`)
 - [ ] API < 200ms
 - [ ] No vulnerabilities
 
-### Web/Mobile Parity
+### Web/Mobile Parity (if both exist)
 - [ ] Same business behavior
 - [ ] Same API consumed
 - [ ] Synchronized data

package/Project/i18n/en/scaffold/CLAUDE.md

@@ -10,7 +10,7 @@ Expert in backlog management, personas, User Stories and prioritization.
 ### 🔧 Tech Lead (`@tech`)
 Expert in architecture, technical decomposition and Scrum facilitation.
 - CSM certified (Certified Scrum Master)
-- Skilled in: Symfony, Flutter, API Platform, Hexagonal Architecture
+- Skilled in: Hexagonal Architecture{{STACK_SKILLS}}
 
 ## Custom commands
 
@@ -85,13 +85,7 @@ Expert in architecture, technical decomposition and Scrum facilitation.
 ## Technical stack
 
 ```yaml
-web: Symfony UX + Turbo (Twig, Stimulus, Live Components)
-mobile: Flutter (Dart, Material/Cupertino)
-api: API Platform (REST, OpenAPI)
-database: PostgreSQL + Doctrine ORM
-infrastructure: Docker
-tests: PHPUnit, Flutter Test
-quality: PHPStan max, Dart analyzer
+{{STACK_BLOCK}}
 ```
 
 ## Project structure
@@ -129,7 +123,7 @@ project-management/
 - Format: "As a [P-XXX]... I want... So that..."
 - **INVEST** validation: Independent, Negotiable, Valuable, Estimable, Sized ≤8pts, Testable
 - The **3 Cs**: Card, Conversation, Confirmation
-- **Vertical Slicing**: Symfony + Flutter + API + PostgreSQL
+- **Vertical Slicing**: {{STACK_SLICE}}
 
 ### Acceptance Criteria
 - **Gherkin** format: GIVEN [context] / WHEN [actor] [action] / THEN [result]
@@ -189,20 +183,6 @@ project-management/
 
 ## Code quality
 
-### Backend (Symfony)
-- PHPStan max level
 - Tests > 80% coverage
-- Hexagonal architecture
-- PSR-12
-
-### Mobile (Flutter)
-- Strict Dart analyzer
-- Widget tests
-- BLoC/Riverpod
-- Material Design 3
-
-### API (API Platform)
-- Auto-generated OpenAPI
-- Validation constraints
-- Serialization groups
-- Security voters
+
+{{QUALITY_BLOCK}}