Transform verbose session transcripts, raw codebases, or complex implementation logs into ultra-condensed, high-density, emojified developer cheat sheets.
1. 🎯 Quick Start Dashboard
flowchart LR A[<b>INPUT SESSION</b><br/>• Chat logs<br/>• Code bases<br/>• Build logs] --> B[<b>CLEANSING</b><br/>• Strip chat<br/>• No filler<br/>• Facts only] B --> C[<b>REFLECTION</b><br/>• Extract API<br/>• Map CLI<br/>• Gotchas] C --> D[<b>CONDENSATION</b><br/>• Layout tables<br/>• Emoji anchors<br/>• Compact code]
2. 🧼 Cleansing
- 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.
3. 🧠 Reflection
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) |
4. ⚡ Condensation
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()} |
5. 🎨 Formatting
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 |
6. 🔍 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.