cc-workspace 4.0.1 → 4.0.3

package/global-skills/dispatch-feature/references/spawn-templates.md

@@ -2,22 +2,17 @@
 
 Reference file for dispatch-feature. Loaded on-demand, not at skill activation.
 
-> **v4.0**: The constitution rule is scoped to orchestrator/ only. Teammates do NOT
-> receive the 12 universal principles automatically. Every spawn template below includes
-> a "Universal principles" section that you MUST fill with the full 12 principles from
-> `~/.claude/rules/constitution-en.md` (or the FR version from constitution.md).
+> Teammates do NOT receive the constitution automatically. Every spawn template
+> below includes a "Constitution" section that you MUST fill with all rules from
+> your workspace's `constitution.md`.
 
 ## Backend/API teammate spawn template
 
 ```
 You are teammate-[service]. Read the CLAUDE.md in your repo first.
 
-## Universal principles (non-negotiable)
-[paste all 12 universal principles from the constitution — they are NOT auto-injected
-into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
-
-## Project rules (non-negotiable)
-[paste project-specific rules from workspace constitution.md, translated to English]
+## Constitution (non-negotiable)
+[paste all rules from your workspace's constitution.md]
 
 ## API contract
 [paste the exact request/response shapes this service must implement]
@@ -28,7 +23,7 @@ into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
 
 ## Instructions
 1. Read the repo CLAUDE.md first — follow its conventions
-2. Implement the tasks above following the full constitution (12 principles above + project rules)
+2. Implement the tasks above following the full constitution (all rules above)
 3. Use the LSP tool for code navigation (go-to-definition, find-references)
 4. Run the existing test suite — report pass/fail
 5. List any dead code created or exposed by your changes
@@ -43,12 +38,8 @@ into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
 ```
 You are teammate-[service]. Read the CLAUDE.md in your repo first.
 
-## Universal principles (non-negotiable)
-[paste all 12 universal principles from the constitution — they are NOT auto-injected
-into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
-
-## Project rules (non-negotiable)
-[paste project-specific rules from workspace constitution.md, translated to English]
+## Constitution (non-negotiable)
+[paste all rules from your workspace's constitution.md]
 
 ## UX Standards (non-negotiable)
 [paste full content of frontend-ux-standards.md]
@@ -61,7 +52,7 @@ into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
 
 ## Instructions
 1. Read the repo CLAUDE.md first — follow its conventions
-2. Implement the tasks following the full constitution (12 principles + project rules) and UX standards
+2. Implement the tasks following the full constitution (all rules above) and UX standards
 3. Use the LSP tool for code navigation
 4. Every new component MUST handle 4 states: skeleton loader, empty+CTA, error+retry, success
 5. Run the existing test suite — report pass/fail
@@ -76,12 +67,8 @@ into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
 ```
 You are teammate-[service]. Read the CLAUDE.md in your repo first.
 
-## Universal principles (non-negotiable)
-[paste all 12 universal principles from the constitution — they are NOT auto-injected
-into teammates since v4.0. Copy them from ~/.claude/rules/constitution-en.md]
-
-## Project rules (non-negotiable)
-[paste project-specific rules from workspace constitution.md, translated to English]
+## Constitution (non-negotiable)
+[paste all rules from your workspace's constitution.md]
 
 ## Your tasks
 [paste tasks — typically: gateway routes, deployment configs, env vars]

package/global-skills/incident-debug/SKILL.md

@@ -4,7 +4,7 @@ description: >
   Debug incidents across a multi-service stack. Spawns parallel
   investigators per layer. Use when user reports a bug, says "erreur",
   "500", "bug", "debug", "ça marche pas", "investigate", or pastes
-  stack traces or error logs.
+  stack traces or error logs. Also French triggers: "erreur", "ça marche pas".
 argument-hint: "[error description or stack trace]"
 context: fork
 allowed-tools: Read, Write, Glob, Grep, Task, Teammate, SendMessage
@@ -83,4 +83,4 @@ Create `./plans/incident-{date}-{name}.md`:
 - Monitoring: [alert/metric]
 ```
 
-Ask: "Diagnostic posé. Dispatcher les fixes ?"
+Ask: "Diagnosis complete. Dispatch fixes?"

package/global-skills/merge-prep/SKILL.md

@@ -4,7 +4,7 @@ description: >
   Prepare branches for merge after QA passes. Checks for conflicts between
   teammate branches, generates PR summaries, lists review points.
   Use after qa-ruthless passes, or when user says "merge", "PR", "pull request",
-  "prépare le merge", "merge-prep", "ready to merge".
+  "prepare merge", "merge-prep", "ready to merge".
 argument-hint: "[feature-name]"
 context: fork
 disable-model-invocation: true
@@ -84,4 +84,4 @@ Write to `./plans/{feature-name}.md`:
 [list or "none — ready to merge"]
 ```
 
-Ask user: "Merge prep terminé. [N] services prêts. Procéder aux PRs ?"
+Ask user: "Merge prep complete. [N] services ready. Proceed with PRs?"

package/global-skills/qa-ruthless/SKILL.md

@@ -5,7 +5,7 @@ description: >
   a clean report is a failed review. Executes tests, hunts dead code,
   checks edge cases, validates UX standards compliance on frontend.
   Use after dispatch-feature completes, or when user says "QA", "review",
-  "teste", "qualité", "qa ruthless", "cherche les bugs".
+  "test", "quality", "qa ruthless", "find bugs".
 argument-hint: "[plan-name or 'all']"
 context: fork
 allowed-tools: Read, Write, Glob, Grep, Task, Teammate, SendMessage
@@ -22,9 +22,8 @@ A review with zero findings = YOU failed.
 2. Read `./plans/{feature-name}.md` for what was implemented
 3. Read `./constitution.md` (project-specific rules)
 
-> **v4.0**: The constitution rule is scoped to orchestrator/ only.
-> Teammates do NOT receive it automatically. You MUST include all 12 universal
-> principles + project-specific rules in every QA teammate spawn prompt.
+> Teammates do NOT receive the constitution automatically.
+> You MUST include all rules from constitution.md in every QA teammate spawn prompt.
 
 ## Rules
 
@@ -41,7 +40,7 @@ Spawn one teammate per service impacted. All run in parallel via Agent Teams.
 
 ### Backend/API QA teammate prompt
 
-Include in spawn prompt: **full constitution (12 universal principles + project-specific rules)**, plan context, then these steps:
+Include in spawn prompt: **full constitution (all rules from constitution.md)**, plan context, then these steps:
 1. Run test suite — report pass/fail with details
 2. Use the **LSP tool** (go-to-definition, find-references) to trace call chains
 3. **Constitution check**: multi-tenant scoping, secrets, rollback, test coverage
@@ -53,7 +52,7 @@ Include in spawn prompt: **full constitution (12 universal principles + project-
 
 ### Frontend QA teammate prompt
 
-Include in spawn prompt: **full constitution (12 universal principles + project-specific rules)**, plan context, UX standards, then these steps:
+Include in spawn prompt: **full constitution (all rules from constitution.md)**, plan context, UX standards, then these steps:
 1. Run tests — report pass/fail
 2. Use the **LSP tool** for tracing component dependencies and store usage
 3. **UX audit** on every new/modified component: 4 states (skeleton not spinner, empty+CTA, error+retry, smooth success), responsive, a11y, interactions (debounce, optimistic, confirmation), forms (inline validation, error messages, preserve data)
@@ -97,6 +96,6 @@ Write to `./plans/{feature-name}.md`:
 [list]
 ```
 
-Ask user: "QA a trouvé [N] problèmes dont [M] bloquants. Dispatcher les fixes ?"
+Ask user: "QA found [N] issues including [M] blockers. Dispatch fixes?"
 If yes, spawn teammates for 🔴, 🟣, and 🟡 items.
 After fixes, re-run QA on fixed files only.

package/global-skills/refresh-profiles/SKILL.md

@@ -3,7 +3,7 @@ name: refresh-profiles
 description: >
   Regenerate service-profiles.md by reading CLAUDE.md from all repos
   listed in workspace.md. Use when conventions changed, or user says
-  "refresh profiles", "mets à jour les profils", "relis les CLAUDE.md".
+  "refresh profiles", "update profiles", "re-read CLAUDE.md files".
 context: fork
 disable-model-invocation: true
 model: haiku

package/global-skills/templates/claude-md.template.md

@@ -2,10 +2,10 @@
 
 > [REPO_DESCRIPTION — one line]
 
-## Stack technique
+## Tech stack
 
-| Technologie | Version | Notes |
-|-------------|---------|-------|
+| Technology | Version | Notes |
+|------------|---------|-------|
 | [language] | [version] | |
 | [framework] | [version] | |
 | [database] | [version] | [usage] |
@@ -24,7 +24,7 @@
 
 <!-- Explain the layering or module organization -->
 
-## Regles critiques
+## Critical rules
 
 <!-- Numbered rules. Each rule has a short name and ✅/❌ examples.
      Keep only rules that an AI agent MUST know to avoid mistakes.
@@ -50,9 +50,9 @@
 
 <!-- Add more rules as needed. Typical count: 3-8 rules per repo. -->
 
-## Conventions de nommage
+## Naming conventions
 
-| Type | Pattern | Exemple |
+| Type | Pattern | Example |
 |------|---------|---------|
 | [files] | [pattern] | [example] |
 | [classes] | [pattern] | [example] |
@@ -63,12 +63,12 @@
 
 <!-- Test framework, how to run, patterns to follow -->
 
-**Lancer les tests :**
+**Run tests:**
 ```bash
 [test command]
 ```
 
-**Patterns :**
+**Patterns:**
 - [describe test organization]
 - [describe mocking strategy]
 - [minimum coverage if applicable]
@@ -77,30 +77,30 @@
 
 <!-- Two-column table: forbidden vs required. Keep it short and impactful. -->
 
-| Interdit | Faire plutot |
-|----------|--------------|
+| Forbidden | Do instead |
+|-----------|-----------|
 | [bad pattern] | [good pattern] |
 | [bad pattern] | [good pattern] |
 | [bad pattern] | [good pattern] |
 
-## Commandes
+## Commands
 
 <!-- Essential commands for dev workflow -->
 
-| Commande | Description |
-|----------|-------------|
+| Command | Description |
+|---------|-------------|
 | `[cmd]` | Build / compile |
 | `[cmd]` | Run tests |
 | `[cmd]` | Lint / format |
 | `[cmd]` | Start dev server |
 
-## Domaines existants
+## Existing domains
 
 <!-- List existing modules/domains/packages if the repo uses a modular architecture.
      Remove this section if not applicable. -->
 
-| Domaine | Chemin | Description |
-|---------|--------|-------------|
+| Domain | Path | Description |
+|--------|------|-------------|
 | [name] | [path] | [one-line description] |
 
 <!-- === OPTIONAL SECTIONS (add only if relevant) === -->
@@ -111,13 +111,13 @@
 <!-- ## Auth
      Describe authentication mechanism, tokens, middleware, guards. -->
 
-<!-- ## Checklist avant livraison
-     - [ ] Tests passent
+<!-- ## Pre-delivery checklist
+     - [ ] Tests pass
      - [ ] Lint clean
-     - [ ] Pas de code mort introduit
-     - [ ] Conventions respectees -->
+     - [ ] No dead code introduced
+     - [ ] Conventions followed -->
 
-<!-- ## Decisions architecturales
+<!-- ## Architectural decisions
      Document any ADRs (Architecture Decision Records) specific to this repo. -->
 
 ---

package/global-skills/templates/constitution.template.md

@@ -1,18 +1,42 @@
 # Constitution — [PROJECT_NAME]
 > Configured on: [DATE]
 
-> The 12 universal principles (security, UX, code, process) apply automatically.
-> This file contains ONLY project-specific rules, numbered from 13.
+Non-negotiable principles for this project. The orchestrator and every teammate
+must follow these rules without exception.
 
-## Project-specific rules
+<!-- Write YOUR engineering principles below. Number them starting at 1.
+     The workspace-init agent will help you fill this interactively.
 
-13. **[Rule name].** [Description — what, why, and when it applies]
-    <!-- Example: **Data precision.** Financial amounts stored as integers (cents). Never floats. -->
+     Common categories to consider:
+     - Security & data (multi-tenancy, secrets, auth)
+     - UX & quality (loading states, responsive, feedback)
+     - Code & architecture (dead code, tests, consistency)
+     - Process (planning, QA, reviews)
 
-14. **[Rule name].** [Description]
-    <!-- Example: **Multi-tenancy.** Every query, endpoint, and view scoped by tenant_id. No exceptions. -->
+     Example rules for inspiration:
 
-15. **[Rule name].** [Description]
-    <!-- Example: **Irreversible operations.** Any irreversible DB change requires feature flag. -->
+     1. **Multi-tenancy is sacred.** No query may return data from one tenant
+        to another. Every query, endpoint, and view is scoped by tenant.
+
+     2. **No hardcoded secrets.** Zero passwords, API keys, or tokens in code.
+        Everything goes through environment variables.
+
+     3. **4 mandatory states.** Every component that displays data must handle:
+        loading, empty, error, success. No blank screens, ever.
+
+     4. **No feature without tests.** Every new behavior has at minimum one test
+        proving it works and one test proving it handles errors.
+
+     5. **Consistency over preference.** Follow existing patterns in the repo,
+        even if you'd prefer it differently.
+-->
+
+## Rules
+
+1. **[Rule name].** [Description — what, why, and when it applies]
+
+2. **[Rule name].** [Description]
+
+3. **[Rule name].** [Description]
 
 <!-- Add more rules as needed. Keep each rule actionable and verifiable. -->

package/global-skills/templates/workspace.template.md

@@ -2,7 +2,7 @@
 > Configured on: [DATE]
 > Orchestrator v4.0
 
-## Projet
+## Project
 <!-- What does this project do? Who is it for? Scale? -->
 [UNCONFIGURED]
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-workspace",
-  "version": "4.0.1",
+  "version": "4.0.3",
   "description": "Claude Code multi-workspace orchestrator — skills, hooks, agents, and templates for multi-service projects",
   "bin": {
     "cc-workspace": "./bin/cli.js"
@@ -20,7 +20,7 @@
     "workspace",
     "monorepo"
   ],
-  "author": "Vincent",
+  "author": "VincVan",
   "license": "MIT",
   "engines": {
     "node": ">=18"

package/global-skills/constitution.md

@@ -1,58 +0,0 @@
-# Constitution
-
-Principes non négociables. S'appliquent à TOUS les projets, TOUS les teammates.
-L'orchestrateur et chaque teammate doivent respecter ces règles sans exception.
-
-## Sécurité & données
-
-1. **Le multi-tenant est sacré.** Aucune requête ne doit retourner des données
-   d'un tenant à un autre. Chaque query, chaque endpoint, chaque vue est scopée.
-   En cas de doute, le teammate refuse d'implémenter et escalade à l'orchestrateur.
-
-2. **Pas de secrets en dur.** Zéro mot de passe, clé API, token dans le code.
-   Tout passe par des variables d'environnement.
-
-3. **Rollback toujours possible.** Chaque migration est réversible. Chaque
-   déploiement peut être annulé. Si une feature ne peut pas être rollback,
-   elle doit être derrière un feature flag.
-
-## UX & qualité
-
-4. **Feedback en moins de 200ms.** Toute action utilisateur déclenche un
-   retour visuel immédiat (spinner, skeleton, optimistic update). L'utilisateur
-   ne doit jamais douter que son clic a été pris en compte.
-
-5. **Les 4 états obligatoires.** Chaque composant qui affiche des données
-   doit gérer : loading, empty, error, success. Pas d'écran blanc, jamais.
-
-6. **Mobile-first.** Le responsive n'est pas un nice-to-have. On design
-   d'abord pour mobile, puis on enrichit pour desktop.
-
-7. **Mieux vaut simple et solide.** Une feature simple qui fonctionne
-   parfaitement vaut mieux qu'une feature complète qui casse. Couper le
-   scope plutôt que livrer du fragile.
-
-## Code & architecture
-
-8. **Pas de code mort.** Chaque implémentation nettoie ce qu'elle rend obsolète.
-   Le code mort est une dette qui s'accumule en silence.
-
-9. **Pas de feature sans test.** Chaque nouveau comportement a au minimum
-   un test qui prouve qu'il marche et un test qui prouve qu'il gère l'erreur.
-
-10. **La cohérence prime sur la préférence.** Suivre les patterns existants
-    du repo, même si on préférerait faire autrement. L'uniformité du codebase
-    est plus importante que l'élégance locale.
-
-## Processus
-
-11. **Planifier avant de coder.** Aucun teammate ne commence sans plan validé.
-    Le plan est écrit, tracé en markdown, et survit aux sessions.
-
-12. **Le QA est hostile.** Un QA qui ne trouve rien a échoué. La complaisance
-    est l'ennemi de la qualité.
-
----
-
-> Les règles spécifiques à un projet (ex: précision des données, contraintes
-> de persona IA) sont dans le `constitution.md` du workspace concerné.

package/global-skills/rules/constitution-en.md

@@ -1,67 +0,0 @@
----
-description: Non-negotiable engineering principles for all agents, teammates, and subagents
-globs: ["workspace.md", "constitution.md", "plans/**", "templates/**"]
----
-
-# Constitution
-
-Non-negotiable principles. Apply to ALL projects, ALL teammates.
-The orchestrator and every teammate must follow these rules without exception.
-
-## Security & data
-
-1. **Multi-tenancy is sacred.** No query may return data from one tenant to
-   another. Every query, endpoint, and view is scoped by tenant. When in doubt,
-   the teammate refuses to implement and escalates to the orchestrator.
-
-2. **No hardcoded secrets.** Zero passwords, API keys, or tokens in code.
-   Everything goes through environment variables.
-
-3. **Rollback always possible.** Every migration is reversible. Every deployment
-   can be rolled back. If a feature cannot be rolled back, it must be behind
-   a feature flag.
-
-## UX & quality
-
-4. **Feedback under 200ms.** Every user action triggers immediate visual feedback
-   (spinner, skeleton, optimistic update). The user must never doubt their click
-   was registered.
-
-5. **4 mandatory states.** Every component that displays data must handle:
-   loading, empty, error, success. No blank screens, ever.
-
-6. **Mobile-first.** Responsive is not a nice-to-have. Design for mobile first,
-   then enrich for desktop.
-
-7. **Simple and solid beats complex and fragile.** A simple feature that works
-   perfectly is worth more than a complete feature that breaks. Cut scope rather
-   than ship fragile code.
-
-## Code & architecture
-
-8. **No dead code.** Every implementation cleans up what it makes obsolete.
-   Dead code is debt that accumulates silently.
-
-9. **No feature without tests.** Every new behavior has at minimum one test
-   proving it works and one test proving it handles errors.
-
-10. **Consistency over preference.** Follow existing patterns in the repo, even
-    if you'd prefer to do it differently. Codebase uniformity matters more than
-    local elegance.
-
-## Process
-
-11. **Plan before coding.** No teammate starts without a validated plan. The plan
-    is written in markdown, tracked, and survives sessions.
-
-12. **QA is hostile.** A QA that finds nothing has failed. Complacency is the
-    enemy of quality.
-
----
-
-> **v4.0 change**: This rule is now scoped to orchestrator/ files only.
-> It is no longer auto-injected into ALL sessions globally.
->
-> Consequence: teammates do NOT receive these principles automatically.
-> The orchestrator MUST include all 12 universal principles + project rules
-> in every teammate spawn prompt.