📦 CS2Vault Cheat Sheet

Core Directive: Automate the conversion of verbose developer sessions into ultra-condensed Quartz-compatible wiki vaults using ultrathink loops.

┌────────────────────────────────────────────────────────┐
│               🧠 ULTRATHINK SYNTHESIS LOOP             │
│ Raw Session Logs ──> [Cleanse] ──> [Condense] ──> Spec │
└──────────────────────────┬─────────────────────────────┘
                           ▼
┌────────────────────────────────────────────────────────┐
│               🗂️ QUARTZ VAULT PIPELINE                 │
│ Processed MD ──> [Frontmatter] ──> [Wiki Links] ──> Pub│
└────────────────────────────────────────────────────────┘

---

🏗️ Core Architecture & Workflows

🧼 1. THE PIPELINE (Session to Vault)

• 🚀 Ingestion: Raw logs/transcripts are cleansed of conversational fluff.
• 🧠 Extraction: Invariants, schemas, configurations, and core CLI commands are isolated.
• ⚡ Condensation: High-density markdown layouts (side-by-side lists, tables) are generated.
• 🎨 Formatting: Emojis serve as structural landmarks for quick scanning.

🗂️ 2. QUARTZ VAULT STRUCTURE

• 📦 Folder Hierarchy: Nested structure under /content/ directory with index.md navigation nodes.
• 🏷️ Frontmatter: Standardized YAML headers mapping title, tags, and description.
• 🔗 Wiki Linking: Cross-linking cheat sheets using double-bracket [[Wiki Links]] syntax.
• 🚀 Static Generation: Quartz builds markdown files into highly-optimized static HTML/JS pages.

🧠 3. ULTRATHINK WORKFLOWS

• 📝 YAML Planning: Every generation begins with a mandatory ultra-condensed YAML reasoning block.
• 🕵️ Verification: Continuous validation of code snippets and configuration syntax.
• 🔄 Refinement Loop: Multi-agent swarms run check/edit loops before final publication.
• 🚨 Safety Invariant: Deprecated features or unsupported APIs are flagged with clear warning callouts.

---

🚀 Quick Start / CLI Commands

This guide provides the step-by-step CLI commands to execute the cs2vault pipeline. Use this workflow to cleanse raw developer logs, orchestrate agentic validation waves, and publish verified Quartz wikis.

🔧 1. Cleanse (Noise Stripping)

Strip chat conversational fluff, extract performance metrics, and format standardized commit logs.

# Cleanse raw logs and output structured markdown
cs2vault cleanse ./raw-session.log --output ./content/04-Projects/clean-session.md

• Noise Removal: Eliminates pleasantries and general setups to keep only absolute developer facts.
• Log Compression: Compresses git history into standard [EMOJI] [SCOPE]: [ACTION] - [METRIC_DELTA] format.
• Metrics Extraction: Compresses latency and footprint measurements into high-density markdown tables.

🧠 2. Ultrathink (Agentic Mapping)

Orchestrate multi-agent validation loops to map wiki nodes and enforce strict architectural constraints.

# Execute agentic validation waves and map node linkages
cs2vault ultrathink ./content/04-Projects/clean-session.md --vault-dir ./content

• Wiki Linkage: Injects bidirectional wiki backlinks [[node-name]] across relevant files.
• Node Assignment: Resolves directory bindings targeting specific folders (e.g., /content/01-Core-Architecture/).
• Invariant Preservation: Identifies and documents compiler, bundler, and database constraints.

⚡ 3. Quartz Bind (Verify & Publish)

Inject Quartz frontmatter, compile metadata indices, and run link verification.

# Bind markdown files, generate AI indices, and compile Quartz
cs2vault bind --generate-llms && npx quartz build

• Frontmatter Injection: Prepends strict YAML frontmatter containing mandatory titles and tags.
• AI Indexing: Compiles a unified llms.txt file by executing generate-llmstxt.js.
• Link Verification: Runs npx quartz build locally to guarantee zero broken references.

---

💡 Best Practices

• Cleansing Automation: Always run log cleansing pipelines prior to agent analysis. Retain only metric deltas and path mappings.
• Verification Builds: Execute npx quartz build locally to validate references. Fix all broken bidirectional [[links]] immediately.
• Metric Standardization: Format all analytical data into unified comparative markdown tables. Keep headers clean and data high-density.
• Frontmatter Integrity: Inject complete metadata schemas (title and tags) into every document. Do not omit titles.

Action	Target Format	Key Metric / Verification
Commit Logs	[EMOJI] [SCOPE]: [ACTION] - [METRIC_DELTA]	0 downtime / p99 latency / % change
Release Notes	Markdown dashboard with analytical highlights table	Build Speed / Avg Latency / Bundle Size
Wiki Bindings	Absolute node directories (e.g. /content/01-Core-Architecture/)	Bidirectional [[backlinks]] integrity

---

🚨 Gotchas & Traps

• 🚨 No Placeholders/Mock Data: Never ship TODO markers, stub descriptions, or empty fields in production wiki content.
• 🚨 Missing Frontmatter: Page rendering breaks if Quartz frontmatter lacks mandatory title, tags, or description YAML metadata.
• 🚨 Unverified Backlinks: Run local validation builds (npx quartz build) before finalizing to prevent broken internal backlinks.
• 🚨 Raw Log Overflow: Exceeding local log limits causes evaluation timeouts. Always slice log files using direct offset/limit range selectors.
• 🚨 Stale Tag Rejections: Edits using outdated snapshot tags cause immediate code rejection. Re-read files to refresh tags before writing.