dev-general

Analyze recent Claude Code sessions to find repetitive tasks that should become reusable skills. Use when the user says "find skills", "what should be skills", "analyze my sessions", "repetitive tasks", "skill candidates", "mine my sessions", "what am I doing repeatedly", "skill opportunities", "automation opportunities", or wants to discover patterns in their Claude Code usage that could be automated. Also use proactively when a user has been doing the same kind of work across multiple sessions.

Sticky teaching-mode toggle for multi-step coding work. When active, break the work into discrete steps and after each one — before moving to the next — explain in plain language what was done and *why*, then wait for "next" / "go" / "continue" before the next edit. Trigger when the user says "teach me as you go", "teach me while you work", "teach me as we go", "explain as you go", "explain what you're doing", "walk me through", "make each change one step at a time", "step by step and explain", "explain the changes to me simply", or similar phrasing that asks for explanation interleaved with implementation. The user is a senior Drupal/JS dev — explanations should focus on the non-obvious *why* (framework idioms, hidden constraints, gotchas, patterns recurring in this codebase), not on what the code literally does. Stay in mode until the user says "stop teaching", "speed up", "just do it", "go ahead and finish", "no more explanations", or similar skip-ahead phrasing.