Wire TOKEN_OPTIMIZER into orchestrator activation, add /graphstack command UX, and vendor graphify-out (cache ignored).

Keeps onboarding friction low while aligning rules with GRAPH_REPORT + TOKEN_OPTIMIZER; CI and installer enforce the command stub.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: MertCapkin

.cursor/commands/graphstack.md

@@ -0,0 +1,5 @@
+# GraphStack — start Orchestrator
+
+1. Execute **Activation** in `orchestrator/ORCHESTRATOR.md` exactly as written (including step **1a**).
+2. Greet using the scripted format from that section.
+3. Wait for user input (`Activation` wait step). If the user already embedded their goal in the same message as this command, proceed with that goal immediately after greeting.

.cursor/rules/graphstack.mdc

@@ -8,25 +8,39 @@ alwaysApply: true
 ## 🎯 Default Mode: Orchestrated
 
 Unless the user explicitly activates a single role, always run as the **Orchestrator**.
-Read `orchestrator/ORCHESTRATOR.md` on first message of every session.
+
+**Frictionless startup (Cursor):** This project’s `.cursor/rules/graphstack.mdc` is
+`alwaysApply: true`, so Composer/Agent already ships with GraphStack rules in every
+new chat. The user does **not** need to paste `Read orchestrator/ORCHESTRATOR.md …`
+every time.
+Your obligation is identical to **executing**
+`orchestrator/ORCHESTRATOR.md` → **Activation** (including parallel **1a** reads)
+on your first substantive turn, before acting on substantive work.
+
+**Optional shortcut:** The `/graphstack` Cursor command (project slash menu) expands
+explicit Orchestrator-bootstrap instructions.
 
 These rules are ALWAYS active in this project. Follow them in every response.
 
 ## 🧠 Rule 1: Graph First (Most Important)
 
-Before reading ANY file, check if `graphify-out/GRAPH_REPORT.md` exists.
+**Session bootstrap wins:** Activation step **1a** in `orchestrator/ORCHESTRATOR.md`
+defines the first-read batch (`TOKEN_OPTIMIZER` + `GRAPH_REPORT` when present, once).
+After bootstrap completes, use graph-first discipline below.
 
-If it exists:
-- Read `graphify-out/GRAPH_REPORT.md` FIRST
-- Use `graphify-out/graph.json` to answer structural questions (dependencies, call paths, module relationships)
-- Only open raw files when the graph is insufficient
+When a graph exists, answer structural questions from the graph before opening raw sources:
+- `graphify-out/GRAPH_REPORT.md` and, when needed, `graphify-out/graph.json`
+- Open implementation files only when the graph cannot answer
 
-If it does not exist:
-- Suggest running `/graphify .` before proceeding
-- Offer to continue without graph context if user confirms
+When no graph exists, suggest `/graphify .`; if proceeding without confirmation,
+state risks explicitly.
 
 ## ⚡ Rule 2: Token Discipline
 
+The **full** decision tree (tiers 1–4, parallel-read protocol, output compression)
+lives in `orchestrator/TOKEN_OPTIMIZER.md`. The Orchestrator loads it once at session
+activation — follow both that file **and** the abbreviated reminders below:
+
 ```
 Is the answer in the graph?        → Use graph, skip raw file read
 Is this tool call speculative?     → Cancel it, ask user first

.github/workflows/ci.yml

@@ -63,6 +63,7 @@ jobs:
               "orchestrator/ORCHESTRATOR.md",
               "orchestrator/TOKEN_OPTIMIZER.md",
               ".cursor/rules/graphstack.mdc",
+              ".cursor/commands/graphstack.md",
               "handoff/BRIEF.md",
               "handoff/REVIEW.md",
               "handoff/BOOTSTRAP.md",

.gitignore

@@ -35,6 +35,9 @@ npm-debug.log*
 # ── GraphStack-specific ───────────────────────────────────
 
 # graphify-out: COMMIT this in your projects (it's the knowledge graph)
+# Local AST cache is machine-specific and must not be versioned:
+graphify-out/cache/
+
 # But exclude the visual HTML in CI if it's large:
 # graphify-out/graph.html
 

CONTRIBUTING.md

@@ -49,6 +49,11 @@ The `demo/` folder shows GraphStack in action on a Node.js auth service. More de
 Used GraphStack on a real project? Measured token savings? Wrote about it?
 Open a PR adding a `docs/case-studies/` entry or link to your post in the README.
 
+### 6. Cursor slash-command bootstrap snippets
+
+Markdown files inside `.cursor/commands/` register under Cursor Composer’s **`/`** slash menu.
+When you introduce a copy change, restart Cursor once locally (and mention that in README) so teammates see the refreshed entry. Keep installers + CI manifests in sync via `installer.py`'s `FILE_COPIES` and `.github/workflows/ci.yml`.
+
 ---
 
 ## Pull Request Guidelines

README.md

@@ -136,15 +136,35 @@ Run this once. After that, use `/graphify --update` — it only re-scans changed
 
 ### Step 4 — Start working
 
-Open a **new Cursor chat** and paste one of these:
+The repo ships two ways to bootstrap the orchestrator — pick whichever feels natural.
+
+#### A) Easiest — new chat only (recommended)
+
+Because `.cursor/rules/graphstack.mdc` is **`alwaysApply: true`**, every new Composer / Agent
+session already carries GraphStack’s binding rules. Simply open chat and describe your goal in
+natural language (`Add …`, `Fix …`). The assistant’s first turn must still **execute**
+`orchestrator/ORCHESTRATOR.md → Activation** (parallel `TOKEN_OPTIMIZER` + `GRAPH_REPORT`),
+but **you don’t paste** `Read orchestrator/...` anymore.
+
+#### B) Slash command `/graphstack` (explicit nudge)
+
+In Cursor Chat/Composer press `/` → choose **`graphstack`**. That injects the Bootstrap command
+stored in `.cursor/commands/graphstack.md` (helps when you want deterministic orchestrator wording
+or onboarding teammates).
+
+*If `/graphstack` doesn't appear immediately, restart Cursor once so it rescans `.cursor/commands/`.*
+
+#### C) Classic explicit prompt (fallback / other tools)
 
 **Existing codebase:**
+
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 [Describe what you want to build or fix]
 ```
 
 **New project from scratch:**
+
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 This is a new project with no existing codebase.
@@ -196,8 +216,13 @@ Problems:
 Step 1 — once:
   /graphify .  →  graphify-out/GRAPH_REPORT.md + graph.json
 
-Step 2 — every session (one prompt):
-  "Read orchestrator/ORCHESTRATOR.md. Add rate limiting to login."
+Step 2 — every session (minimal typing):
+  Open Composer + describe the task (rules already activate GraphStack automatically),
+  optionally type `/graphstack` once for an explicit orchestrator preamble,
+  or paste the legacy `Read orchestrator/ORCHESTRATOR.md …` snippet if working outside Cursor.
+
+Example natural-language kickoff:
+  "Add rate limiting to login."
 
   [ARCHITECT]   reads graph (not raw files) → scopes change → writes BRIEF.md
        ↓ auto
@@ -219,8 +244,12 @@ Step 2 — every session (one prompt):
 No code yet? GraphStack handles that too.
 
 ```
-"Read orchestrator/ORCHESTRATOR.md.
- New project: REST API for task management. TypeScript, Express, PostgreSQL."
+Composer (Cursor):
+  Describe the product + tech stack naturally (alwaysApply rules bootstrap GraphStack),
+  optionally `/graphstack` beforehand to inject the scripted opener.
+
+Bootstrap example:
+"/graphstack then: New project REST API for task mgmt — TS, Express, PostgreSQL."
 
   [BOOTSTRAPPER]  analyzes idea → decomposes into modules → orders by dependency
                   → writes BOOTSTRAP.md (the memory across all cycles)
@@ -270,6 +299,7 @@ GraphStack's savings come from three mechanisms:
 ```
 your-project/
 ├── .cursor/rules/graphstack.mdc          ← always-active rules (Cursor auto-loads)
+├── .cursor/commands/graphstack.md        ← `/graphstack` Cursor slash-command bootstrapper
 ├── orchestrator/
 │   ├── ORCHESTRATOR.md                   ← state machine: all transitions
 │   └── TOKEN_OPTIMIZER.md                ← token budget rules for all roles
@@ -402,12 +432,17 @@ The post-commit hook enforces the same rules automatically. You never need to th
 | Git-native task board | ✅ GNAP | ❌ | ❌ | ❌ |
 | Session resumability | ✅ STATE.md | ❌ | ❌ | ❌ |
 | Token optimization rules | ✅ explicit | ❌ | ❌ | ✅ partial |
+| Cursor `/graphstack` slash bootstrap | ✅ | ❌ | ❌ | ❌ |
 | Setup complexity | Low | Low | High | Low |
 
 ---
 
 ## Resuming a Session
 
+Default (Cursor Composer with GraphStack repo open): reopen chat and paste a short cue such as `"Resume GraphStack STATE.md"` or select `/graphstack` followed by `"Resume"` — Activation still runs tokens + graph loaders automatically.
+
+Classic explicit prompt:
+
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 Resume from last session.
@@ -419,21 +454,23 @@ Orchestrator reads `handoff/STATE.md` and `handoff/board/doing/` and picks up ex
 
 ## All Prompts
 
-### Standard session
+**Quick path:** describe work directly (rules + optional `/graphstack`). Legacy blocks remain for deterministic copy/paste workflows or non‑Cursor tooling.
+
+### Standard session *(legacy explicit)*
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 [What you want to build or fix — any language]
 ```
 
-### New project from scratch
+### New project from scratch *(legacy explicit)*
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 This is a new project with no existing codebase.
 I want to build [describe your idea].
 Tech stack: [language, framework, database].
 ```
 
-### Resume a previous session
+### Resume a previous session *(legacy explicit)*
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 Resume from last session.

docs/CURSOR_PROMPTS.md

@@ -32,6 +32,7 @@ Bu komut şunları yapar:
 - `orchestrator/` → Orchestrator ve Token Optimizer
 - `handoff/` + `scripts/` → board ve state dosyaları
 - `scripts/graphstack/` → Python helper paketi (bash ve PowerShell shim'leri buna delege eder)
+- `.cursor/commands/graphstack.md` → Slash menüsünde `/graphstack` komutu
 
 ### Adım 2 — Graphify'ı yükle ve grafiği oluştur
 
@@ -51,60 +52,79 @@ Büyük projelerde 1-2 dakika sürebilir, sonrası anında.
 
 ### Adım 3 — Başla
 
-Yeni bir Cursor chat'i aç ve aşağıdaki promptlardan birini kullan.
+**Önerilen (en az sürtünme):** Cursor'da projeyle birlikte yeni Composer/Agent aç —
+`graphstack.mdc` `alwaysApply: true` olduğu için Kurallar zaten yüklü. Direkt olarak
+hedefini yaz (**Türkçe veya İngilizce**). Asistanın ilk işi olarak yine Orchestrator Activation
+(okuma + TOKEN_OPTIMIZER + graf) çalıştırması gerekir; senin her seferinde
+`Read orchestrator/...` kopyalamana gerek yok.
 
-> **Not:** `.cursor/rules/graphstack.mdc` dosyası Cursor tarafından otomatik yüklenir.
-> Kurallar her chat'te aktif — ek bir şey yapman gerekmiyor.
+**Slash komutu (istersen daha net başlatmak için):** Sohbete `/` yaz → **`graphstack`**
+dosyası `.cursor/commands/graphstack.md` içeriğini enjekte eder (`/graphstack` çıkmıyorsa
+Cursor'ı yeniden başlat).
 
----
-
-## ⚡ Normal Kullanım — Tek Prompt
+**İsteğe bağlı klasik satır *(başka editör ya da garanti için):*** aşağıdaki blok hâlen geçerlidir.
 
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
-[Ne yapmak istediğini buraya yaz — Türkçe veya İngilizce]
+[Hedefini yaz]
 ```
 
-**Örnekler:**
+> **Not:** `.cursor/rules/graphstack.mdc` her oturumda otomatik yüklenir; bu satır fazladan garanti için.
+
+---
+
+## ⚡ Örnek hedef yazıları (klasik bloğu atlarsan bile)
+
+Orchestrator yine graf + handoff yüklemesini yapmak zorunda; senden sadece amaç gerek:
+
 ```
-Read orchestrator/ORCHESTRATOR.md and follow it exactly.
-Add email verification to the registration flow.
+Kayıtta e-posta doğrulaması eklemek istiyorum.
 ```
 ```
-Read orchestrator/ORCHESTRATOR.md and follow it exactly.
-Login endpoint çok yavaş, performans sorununu bul ve düzelt.
+Login endpoint çok yavaş — performansı bul ve düzelt.
+```
+```
+Resume from last session.
 ```
 
-Orchestrator Architect → Builder → Reviewer → QA → Ship döngüsünü otomatik yönetir.
+Architect → Builder → Reviewer → QA → Ship zinciri kullanıcı etkileşimi olmadan yürür.
 
 ---
 
 ## 🚀 Sıfırdan Yeni Proje (Bootstrap Modu)
 
-Henüz hiç kod yoksa:
+Henüz kod yoksa **sırf hedef yazman yeter**: `alwaysApply` kuralları etkin.
+İstersen garanti olarak `/graphstack` komutunun ardından açıklamayı yaz.
 
 ```
-Read orchestrator/ORCHESTRATOR.md and follow it exactly.
-This is a new project with no existing codebase.
-[Projeyi tanımla: ne yapıyor, kime yönelik, hangi teknoloji]
+Boş bir repo için REST API yazıyorum: kullanıcılar proje oluşturup görev atayabilecek.
+TypeScript + Node + Express + PostgreSQL istiyorum. İlk fazda önce authentication.
 ```
 
-**Örnek:**
+**Klasik tam blok (yedek)**
+
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
-This is a new project. I want to build a REST API for task management.
-Users can create projects, add tasks, assign them, track progress.
-Tech stack: TypeScript, Node.js, Express, PostgreSQL.
+This is a new project with no existing codebase.
+[Projeyi tanımla: amaç, kullanıcı, teknoloji]
 ```
 
 Bootstrapper tüm modülleri planlar, bağımlılık sırasını belirler,
-her döngü için brief yazar. Her döngü sonrası grafı gerçek koddan günceller.
+her döngü için brief yazar; her döngü sonunda güncellenmiş graf gerekli.
 
 ---
 
 ## 🔄 Oturum Devam Ettirme
 
-Cursor'ı kapatıp yeniden açtıysan:
+Cursor'ı yeniden açtıktan sonra sadece:
+
+```
+Önceki GraphStack oturumundan devam et.
+STATE.md ile board'daki yapılacaklara uy.
+```
+
+Gerekli güvence için hâlen şu blok kullanılabilir:
+
 ```
 Read orchestrator/ORCHESTRATOR.md and follow it exactly.
 Resume from last session.
@@ -187,7 +207,8 @@ python -m graphstack board log
 
 ## 💡 İpuçları
 
-- Her Orchestrator döngüsü için **yeni bir Cursor chat** aç — context temiz kalır
+- Her Orchestrator döngüsünde mümkünse **yeni bir Cursor chat** aç — context temiz kalır
+- Cursor slash menüsünde **`/graphstack`** kullanarak Orchestrator açılışını netleştir
 - `.cursor/rules/graphstack.mdc` otomatik yüklenir, elle okutman gerekmiyor
 - Grafı büyük değişikliklerden sonra güncelle: `/graphify --update`
 - `handoff/STATE.md` dosyasını silme — oturum geçmişin orada

graphify-out/.graphify_root

@@ -0,0 +1 @@
+C:\Users\elife\Desktop\Mert_Proje\graphstack