@neikyun/ciel 6.4.1 → 6.4.3
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.
package/assets/CLAUDE.md
CHANGED
|
@@ -6,11 +6,32 @@ This file is Claude Code's project-level instruction. **It is not advisory — t
|
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Visibilite — regle dure (VIOLATION = CRITICAL)
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
11
|
+
**Le pipeline est ta checklist mentale, pas un journal public.**
|
|
12
|
+
|
|
13
|
+
| Dans le THINKING (interne) | Dans la SORTIE VISIBLE |
|
|
14
|
+
|---------------------------|----------------------|
|
|
15
|
+
| Classification de profondeur | Resultat final |
|
|
16
|
+
| Etapes du pipeline (DOCS, QUOI, DIVERGE...) | Informations pertinentes pour l'utilisateur |
|
|
17
|
+
| Transitions d'etapes (in_progress > completed) | Diffs, preuves, erreurs, reponses |
|
|
18
|
+
| TaskCreate/TaskUpdate | Jamais — c'est ta machinerie interne |
|
|
19
|
+
|
|
20
|
+
**INTERDIT en sortie visible** :
|
|
21
|
+
- Tableaux d'etapes de pipeline ("| Etape | Statut |")
|
|
22
|
+
- Annonces de progression ("DOCS termine", "Passons a QUOI", "Maintenant FAIRE")
|
|
23
|
+
- Listes numerotees des etapes completees
|
|
24
|
+
- "Pipeline X/Y etapes complete"
|
|
25
|
+
- "GATE DISPATCH effectue"
|
|
26
|
+
- "[CIEL]" ou "[CIEL Depth:]" dans le texte visible
|
|
27
|
+
- Comptes-rendus META visibles (les 10 items restent en thinking)
|
|
28
|
+
|
|
29
|
+
**PERMIS en sortie visible** :
|
|
30
|
+
- Resultats, reponses, diffs, logs
|
|
31
|
+
- "PR mergee", "Workflow declenche", "VERSION mis a jour"
|
|
32
|
+
- Questions a l'utilisateur (AskUserQuestion)
|
|
33
|
+
|
|
34
|
+
**TaskCreate/TaskUpdate** : cree-les pour ton tracking interne, sans les narrer. L'utilisateur ne voit pas tes transitions de taches.
|
|
14
35
|
|
|
15
36
|
---
|
|
16
37
|
|
|
@@ -27,6 +48,7 @@ pipeline state in your reasoning. Output only what the user needs to see.
|
|
|
27
48
|
|
|
28
49
|
## Rules (immutable — do NOT skip)
|
|
29
50
|
|
|
51
|
+
0. **Visibilite** — pipeline 100% dans le thinking. Sortie visible = resultats uniquement. Pas de tableaux, pas d'annonces d'etapes, pas de "DOCS termine". L'utilisateur voit les resultats, jamais la machinerie.
|
|
30
52
|
1. **Pipeline interne** — classify depth and track step internally. Concise output.
|
|
31
53
|
2. **Pipeline** — follow the 16-step table below. Complete ALL steps for your depth. No shortcuts.
|
|
32
54
|
3. **TODO list** — use `TaskCreate` at the start of each task (one task per pipeline step). Mark each step `in_progress` before starting it, `completed` when done.
|
|
@@ -126,6 +148,7 @@ These are the most frequently skipped pipeline steps. Do NOT fall into these tra
|
|
|
126
148
|
| **No PROUVER** | Claiming done without evidence | Show BEFORE/AFTER evidence (logs, curl, screenshot) |
|
|
127
149
|
| **No MEMOIRE** | Losing state between sessions | Save `.ciel/map.json` + `.ciel/memory.json` at task end |
|
|
128
150
|
| **No META** | Skipping reflection | Always run META (10 items) — it closes the feedback loop |
|
|
151
|
+
| **Pipeline visible** | Displaying pipeline steps, tables, or progress to the user | Pipeline lives in thinking ONLY. User sees results, never the machinery. |
|
|
129
152
|
|
|
130
153
|
**Self-check**: After each step, ask yourself: "Did I just skip a pipeline step?" If yes, go back and do it.
|
|
131
154
|
|
|
@@ -7,9 +7,19 @@ description: Deep-reasoning orchestrator for coding tasks. Classifies task depth
|
|
|
7
7
|
|
|
8
8
|
Principe : **"Understand before generating. Verify before claiming done."**
|
|
9
9
|
|
|
10
|
+
## VISIBILITE — regle dure
|
|
11
|
+
|
|
12
|
+
**Le pipeline est ta checklist mentale, pas un journal public.**
|
|
13
|
+
|
|
14
|
+
- **THINKING (interne)** : profondeur, etapes, transitions, META, tracking
|
|
15
|
+
- **SORTIE VISIBLE** : resultats, reponses, diffs, preuves — jamais la machinerie
|
|
16
|
+
|
|
17
|
+
**INTERDIT en visible** : tableaux d'etapes, "DOCS termine", "Passons a FAIRE", "[CIEL]", comptes-rendus META
|
|
18
|
+
**PERMIS en visible** : "PR mergee", logs, diffs, reponses aux questions
|
|
19
|
+
|
|
10
20
|
## Regles (immutables)
|
|
11
21
|
|
|
12
|
-
1. **Pipeline interne** —
|
|
22
|
+
1. **Pipeline interne** — les 16 etapes existent UNIQUEMENT dans ton raisonnement. Sortie visible = resultats, jamais le tracking. Pas de "DOCS termine", pas de tableaux d'etapes, pas de "Passons a QUOI". Le pipeline est ta checklist mentale, pas un journal public.
|
|
13
23
|
2. **Pipeline** — suis les 16 etapes dans l'ordre
|
|
14
24
|
3. **TODO list** — cree une todo list au debut de chaque tache avec `todowrite` (OpenCode) ou `TaskCreate` (Claude Code). Marque chaque etape `in_progress` avant de commencer et `completed` a la fin.
|
|
15
25
|
4. **ASK** — utilise `question` tool SEULEMENT si ambigu. Si le contexte est suffisant, decide et avance sans demander.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@neikyun/ciel",
|
|
3
|
-
"version": "6.4.
|
|
3
|
+
"version": "6.4.3",
|
|
4
4
|
"description": "Ciel — Deep-reasoning pipeline for LLM-assisted development. OpenCode plugin + multi-platform CLI (OpenCode, Claude Code, more).",
|
|
5
5
|
"main": "./dist/plugin/index.js",
|
|
6
6
|
"types": "./dist/plugin/index.d.ts",
|