changed orchetrators into skills, cleared skills, applied frontmatter
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: analyze
|
||||
description: Analyze code or a codebase deeply before any modification
|
||||
argument-hint: <code, file, or area to analyze>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/analyzer.md
|
||||
|
||||
Execute the ANALYZER agent on the following target:
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: architect
|
||||
description: Conçoit l'architecture d'un système ou d'une feature. Produit un plan structuré avant toute implémentation.
|
||||
argument-hint: <système ou feature à architecturer>
|
||||
disable-model-invocation: true
|
||||
---
|
||||
|
||||
Charge et applique strictement :
|
||||
- .claude/agents/designer.md
|
||||
|
||||
Exécute le DESIGNER sur la demande suivante :
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: debug
|
||||
description: Find root cause and fix an issue precisely
|
||||
argument-hint: <issue description or failing code>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/debugger.md
|
||||
|
||||
Execute the DEBUGGER agent on the following issue:
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: implement
|
||||
description: Implement a feature cleanly following project conventions
|
||||
argument-hint: <feature or change to implement>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/implementer.md
|
||||
|
||||
Execute the IMPLEMENTER agent on the following request:
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
name: init-project
|
||||
description: Initialise un projet complet from scratch. Structure, stack, fichiers de base, conventions. Orchestration complète avec validation utilisateur.
|
||||
argument-hint: <description ou idée de projet>
|
||||
disable-model-invocation: true
|
||||
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
# ORCHESTRATEUR : INIT PROJECT
|
||||
|
||||
Charge et applique strictement :
|
||||
- .claude/agents/analyzer.md
|
||||
- .claude/agents/designer.md
|
||||
- .claude/agents/implementer.md
|
||||
- .claude/agents/reviewer.md
|
||||
- .claude/agents/tester.md
|
||||
|
||||
---
|
||||
|
||||
## PROJET
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
---
|
||||
|
||||
## WORKFLOW
|
||||
|
||||
### 1. ANALYZER
|
||||
Comprendre :
|
||||
- Type de projet (web app, API, lib, CLI, etc.)
|
||||
- Contraintes et préférences de stack
|
||||
- Repo existant (si applicable)
|
||||
- Décisions critiques manquantes
|
||||
|
||||
### 2. DESIGNER
|
||||
Définir :
|
||||
- Architecture
|
||||
- Stack technique
|
||||
- Structure des dossiers
|
||||
- Modules clés
|
||||
- Conventions du projet
|
||||
|
||||
### 3. VALIDATION GATE — STOP OBLIGATOIRE
|
||||
Présenter :
|
||||
- Stack choisie
|
||||
- Architecture
|
||||
- Structure des dossiers
|
||||
|
||||
Demander approbation explicite.
|
||||
**NE PAS CONTINUER sans réponse.**
|
||||
|
||||
SI changements → retour au DESIGNER
|
||||
|
||||
SI approuvé → continuer
|
||||
|
||||
### 4. IMPLEMENTER
|
||||
Créer :
|
||||
- Structure des dossiers
|
||||
- Fichiers de config (build, lint, format)
|
||||
- CLAUDE.md du projet (depuis templates/project-CLAUDE.md)
|
||||
- README.md
|
||||
- Code de base (entry point, modules principaux)
|
||||
- Structure de tests
|
||||
|
||||
### 5. REVIEWER
|
||||
Valider :
|
||||
- Cohérence de la structure
|
||||
- Scalabilité
|
||||
- Mauvaises décisions initiales
|
||||
|
||||
### 6. FIX LOOP — max 3 itérations
|
||||
|
||||
SI CRITICAL issues :
|
||||
- Appeler IMPLEMENTER avec les corrections
|
||||
- Appeler REVIEWER
|
||||
- Incrémenter le compteur
|
||||
|
||||
SI compteur > 3 :
|
||||
- STOP
|
||||
- Escalader à l'utilisateur
|
||||
|
||||
SI seulement IMPORTANT ou MINOR :
|
||||
- Continuer mais lister dans l'output final
|
||||
|
||||
### 7. TESTER
|
||||
Définir :
|
||||
- Comment valider le setup initial
|
||||
- Premiers scénarios de test
|
||||
|
||||
---
|
||||
|
||||
## OUTPUT FINAL
|
||||
|
||||
- Structure du projet créée
|
||||
- Instructions de setup
|
||||
- Code initial
|
||||
- Prochaines étapes recommandées
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: refactor
|
||||
description: Improve code quality without changing behavior
|
||||
argument-hint: <file, function, or module to refactor>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/refactorer.md
|
||||
|
||||
Execute the REFACTORER agent on the following target:
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: review
|
||||
description: Strict code review with severity-graded issues
|
||||
argument-hint: <file, function, or code to review>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/reviewer.md
|
||||
|
||||
Execute the REVIEWER agent on the following code:
|
||||
|
||||
$ARGUMENTS
|
||||
@@ -1,17 +1,85 @@
|
||||
---
|
||||
name: ship-feature
|
||||
description: Ship a feature end-to-end via multi-agent orchestrator
|
||||
description: Implémente une feature end-to-end via orchestration multi-agents. Analyse → Design → Validation → Implémentation → Review → Tests.
|
||||
argument-hint: <description de la feature à implémenter>
|
||||
disable-model-invocation: true
|
||||
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
Load and follow strictly these agent files:
|
||||
- .claude/agents/ship-feature.md
|
||||
# ORCHESTRATEUR : SHIP FEATURE
|
||||
|
||||
Charge et applique strictement :
|
||||
- .claude/agents/analyzer.md
|
||||
- .claude/agents/designer.md
|
||||
- .claude/agents/implementer.md
|
||||
- .claude/agents/reviewer.md
|
||||
- .claude/agents/tester.md
|
||||
|
||||
Execute the orchestrator defined in .claude/agents/ship-feature.md with the following request:
|
||||
---
|
||||
|
||||
## FEATURE
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
---
|
||||
|
||||
## WORKFLOW
|
||||
|
||||
### 1. ANALYZER
|
||||
Analyser le contexte existant pertinent à la feature.
|
||||
|
||||
### 2. DESIGNER
|
||||
Concevoir la solution sur la base de l'analyse.
|
||||
|
||||
### 3. VALIDATION GATE — STOP OBLIGATOIRE
|
||||
- Présenter le design clairement à l'utilisateur
|
||||
- Demander une approbation explicite
|
||||
- **NE PAS CONTINUER sans réponse**
|
||||
|
||||
SI changements demandés :
|
||||
- Appeler DESIGNER avec le feedback
|
||||
- Répéter la validation
|
||||
|
||||
SI approuvé → continuer
|
||||
|
||||
### 4. IMPLEMENTER
|
||||
Implémenter selon le design validé.
|
||||
|
||||
### 5. REVIEWER
|
||||
Review stricte du code produit.
|
||||
|
||||
### 6. FIX LOOP — max 3 itérations
|
||||
|
||||
SI CRITICAL issues :
|
||||
- Appeler IMPLEMENTER avec les corrections
|
||||
- Appeler REVIEWER
|
||||
- Incrémenter le compteur
|
||||
|
||||
SI compteur > 3 :
|
||||
- STOP
|
||||
- Escalader à l'utilisateur avec les issues bloquantes
|
||||
|
||||
SI seulement IMPORTANT ou MINOR :
|
||||
- Continuer mais les lister dans l'output final
|
||||
|
||||
### 7. TESTER
|
||||
Générer et exécuter les tests de la feature.
|
||||
|
||||
---
|
||||
|
||||
## RULES
|
||||
|
||||
- Ne jamais sauter l'analyse
|
||||
- Ne jamais sauter la validation
|
||||
- Ne jamais implémenter sans approbation
|
||||
- Garder les agents isolés dans leurs responsabilités
|
||||
- Appliquer les normes CLAUDE.md strictement
|
||||
|
||||
---
|
||||
|
||||
## OUTPUT FINAL
|
||||
|
||||
- Design validé
|
||||
- Implémentation finale
|
||||
- Résumé de la review
|
||||
- Plan de tests et résultats
|
||||
|
||||
Reference in New Issue
Block a user