Transform verbose session transcripts, raw codebases, or complex implementation logs into ultra-condensed, high-density, emojified developer cheat sheets.
🎯 Quick Start Dashboard
graph LR %% Direction direction LR %% Styles and Classes classDef default fill:#f9f9f9,stroke:#333,stroke-width:1px,color:#333; classDef stepHeader fill:#e1f5fe,stroke:#0288d1,stroke-width:2px,color:#01579b,font-weight:bold; classDef listNode fill:#ffffff,stroke:#ccc,stroke-width:1px,color:#555,font-size:13px; %% Subgraph: Step 1 subgraph Step1 [ ] direction TB S1["INPUT SESSION"] ::: stepHeader L1["• Chat logs<br>• Code bases<br>• Build logs"] ::: listNode S1 --> L1 end %% Subgraph: Step 2 subgraph Step2 [ ] direction TB S2["🧼 CLEANSING"] ::: stepHeader L2["• Strip chat<br>• No filler<br>• Facts only"] ::: listNode S2 --> L2 end %% Subgraph: Step 3 subgraph Step3 [ ] direction TB S3["🧠 REFLECTION"] ::: stepHeader L3["• Extract API<br>• Map CLI<br>• Gotchas"] ::: listNode S3 --> L3 end %% Subgraph: Step 4 subgraph Step4 [ ] direction TB S4["⚡ CONDENSATION"] ::: stepHeader L4["• Layout tables<br>• Emoji anchors<br>• Compact code"] ::: listNode S4 --> L4 end %% Flow connections between steps Step1 --> Step2 Step2 --> Step3 Step3 --> Step4 %% Styling adjustments for subgraphs to make them borderless style Step1 fill:none,stroke:none style Step2 fill:none,stroke:none style Step3 fill:none,stroke:none style Step4 fill:none,stroke:none
🧼 1. Cleansing (Noise Stripping)
- Conversational pleasantries: Strip “Hello”, “Sure”, “Let me help you with”, “As you can see”, and meta-dialogue.
- Context scaffolding: Remove long paragraphs explaining why a tool or library is designed a certain way; keep only the direct application.
- Unused boilerplate: Delete generic setups or verbose explanation blocks.
🧠 2. Reflection (Feature Extraction)
Extract these core elements and group them by developer intent:
| Focus | Elements to Extract | Representation |
|---|---|---|
| API Contracts | Function signatures, parameters, types, interfaces | Concise TS/Python interface blocks |
| CLI Commands | Installation, build, run, test commands | Actionable inline code lines |
| Configuration | Environment variables, config files (vite.config.ts, etc.) | Key-value settings tables |
| Architectural Invariants | File paths, structure, folder layout | Directory trees (find-like) |
⚡ 3. Condensation (Density Maximization)
Pack maximum information in minimum space. Prefer structural density over paragraphs.
Gotchas & Caveats
- 🚨 Warning: Never suppress compiler/linter warnings to bypass test suites.
- 🚨 Trap: Avoid using global state variables across SSR boundaries in Svelte 5.
- 🚨 Rule: All path variables in plugins must be absolute.
Side-by-Side Comparatives
| Svelte 4 (Stores/Slots) | Svelte 5 (Runes/Snippets) |
|---|---|
let count = writable(0) | let count = $state(0) |
let doubled = derived(count, $c => $c * 2) | let doubled = $derived(count * 2) |
<slot /> | {@render children()} |
🎨 4. Formatting (Emoji Key)
Use emojis consistently as visual anchors for rapid scanning:
| Emoji | Category | Use Case |
|---|---|---|
| 🚀 | Quick Start | Getting started quickly, installation commands, initial setups |
| 🔧 | Configuration | Settings, config files, env files, tuning parameters |
| 📦 | Dependencies | Installation lists, imports, package definitions |
| 💡 | Best Practices | Code patterns, optimization tips, recommended layouts |
| 🚨 | Gotchas / Alerts | Critical warnings, traps, common error causes |
| 🔍 | Verification | Tests, lint commands, assertions, validation checklists |
🔍 Self-Verification Checklist
Before saving, verify the cheat sheet against these rules:
- No paragraph exceeds 2 sentences.
- All commands are copy-pasteable and grouped.
- File paths are exact and absolute where required.
- No fluff words (e.g. “basically”, “essentially”, “just”, “simply”).
- Formatted correctly with appropriate markdown syntax.