Add new tiles, images, and videos to the portfolio work page grid. Use when the user says "add a tile", "add an image", "add a video", "new work item", "add this to the grid", "wire up this image", "wire up this video", "add work tile", or drops new assets into public/work/. ALWAYS asks the user for layout type, naming, hover state, and grid position before making changes. Handles both image-only and video tiles with poster extraction and format optimization. Do NOT use for modifying existing tiles, changing the grid system itself, or editing the Tile component.
Writes original blog posts and essays with genuine human voice, using voice presets and AI-tell detection to eliminate machine-sounding prose. Use when the user says "write a blog post", "blog about", "write an essay", "draft a post about", "draft a blog post on", or "blog post on". Supports multiple voice presets (Paul Graham, Naval, Zinsser, default) and a multi-phase workflow with reconstruction passes. Do NOT use for copywriting, marketing copy, social media posts, technical documentation, or rewriting/humanizing existing content.
Dutch freelance (zzp) bookkeeping automation for Tellow. Use when the user asks to "reconcile transactions", "find missing invoices", "download receipts", "upload invoices to Tellow", "do my BTW quarter", "handle bookkeeping", or "manage my bonnetjes". Do NOT use for personal finance, non-Dutch tax systems, or non-Tellow bookkeeping software. Requires browser control (claude-in-chrome MCP) to login to Tellow and vendor platforms via Google OAuth.
Transforms AI-generated content into natural, human-sounding writing by eliminating AI patterns, banned phrases, and robotic structure. Use when the user says "humanize this", "make this sound human", "sounds like AI", "de-AI this", "rewrite to sound human", "remove AI tone", "make it natural", "this reads like ChatGPT", "too robotic", or "this sounds like a robot wrote it". Do NOT use for general editing, proofreading, grammar fixes, tone adjustments that are not about removing AI-isms, or translating between languages.
Applies React and Next.js performance optimization patterns when writing or reviewing code. Use when the user says "optimize this React code", "review for performance", "make this component faster", "reduce bundle size", "fix waterfalls", "Next.js performance", or "apply React best practices". Do NOT use for general React questions like "how does useState work", scaffolding new projects, or non-performance refactoring. Do NOT use for Vue, Angular, or Svelte code.
Personal accountability reflection combining WHOOP health data with coaching psychology. Use when user says "reflect", "check in", "how am I doing", "weekly reflect", "daily check-in", "wellbeing review", "health check", or wants to review their productivity, patterns, and physical state against biometric data. Do NOT use for general health questions, fitness advice, WHOOP setup help, or code review. Only use when the user wants a structured personal reflection session.
Interactive guide for creating new Claude Code skills. Walks the user through use case definition, frontmatter generation, instruction writing, and validation. Use when user says "create a skill", "build a skill", "write a skill", "new skill for", "skill for [topic]", "help me make a skill", or "I want to build a skill". Do NOT use when user asks "what skills do I have", "list skills", or general coding questions unrelated to skill authoring.
Systematic debugging methodology that enforces root cause analysis before fixing. Use when the user says "debug this", "why is this failing", "fix this bug", "this test is broken", "investigate this error", "track down this issue", "something is wrong with", or "figure out why this crashes". Do NOT use for writing new features, general code review, refactoring, or questions about how code works without an active bug.