Create publication-quality technical infographics from any source — tweets, articles, architectures, or ideas. Use this skill whenever the user wants to visually break down a technical concept, map a system architecture, turn a tweet or thread into a shareable diagram, create editorial-style pipeline or flow visualizations, illustrate feedback loops or compounding mechanisms, or produce visuals for a newsletter or blog. Trigger on phrases like "visualize this", "diagram this", "break this down visually", "map this architecture", "make an infographic", "turn this tweet into a visual", "show me how this system works", "create a visual for my newsletter", or any request to produce a designed technical visual rather than a generic flowchart. Also trigger when the user shares a URL, screenshot, or paste of technical content and asks for analysis — the visual IS the analysis. Also trigger for gap analysis when a user shares a codebase or project and asks "what is missing", "how does this compare to X", or "show me
Make Claude Code sessions compound — every session builds on the last instead of starting from scratch. Implements Karpathy's LLM Wiki pattern for software engineering. Use this skill when starting a new project, onboarding to an existing codebase, or any time the user says "set up my project", "add project memory", "create CLAUDE.md", "help me structure this project", "I keep re-explaining things to Claude", "my sessions don't remember anything", "ingest this document", or "run a health check". Also trigger when the user asks about session efficiency, token usage, or wants to improve their Claude Code workflow. This skill creates and maintains a three-layer knowledge system — raw sources, an interlinked wiki, and a schema that governs it all — plus metrics to prove it works.