mahidalhan

PROACTIVE skill - Claude invokes automatically when user messages exhibit anti-patterns. Detects recursive nesting, scope creep, buried asks, assumed context, stream dumps, imprecise descriptions. Disable with "coach off" or "raw mode".

USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions.

Explains code, algorithms, system design using ASCII diagrams. Trigger phrases - "explain visually", "I don't get it", "show me", "ascii diagram", "help me understand". Produces diagram-first explanations ending with TL;DR tables.

USE WHEN: user requests generative art, algorithmic art, procedural visuals, flow fields, particle systems, creative coding, or says "create art", "generative", "p5.js". DO NOT USE WHEN: static images, traditional graphics, or non-generative visual work is requested. Creates original algorithmic art—never copies existing artists' work.

USE WHEN: analyzing existing architectures, evaluating architectural decisions, identifying technical debt, planning refactoring, assessing whether patterns are justified, onboarding to complex codebases, reviewing PRs with architectural changes. DO NOT USE WHEN: simple code questions, bug fixes, feature implementation, or tasks not requiring architectural analysis. For complex architectural analysis, trigger deep thinking with "think harder" or "ultrathink" to enable thorough first-principles reasoning.

USE WHEN: visualizing algorithms, data structures, architecture, control flow with ASCII art, or when terminal-friendly diagrams are needed. DO NOT USE WHEN: Mermaid diagrams are better suited, rich graphics are available, or simple text explanation suffices.

USE WHEN: needing real code examples from GitHub, finding API usage patterns, looking up framework setup, verifying library implementations, eliminating hallucinations with working code. DO NOT USE WHEN: working on proprietary code, questions about the current codebase, or when local context is sufficient. Requires Exa API key configured in environment.

USE WHEN: user asks "explain", "teach me", "how does X work", "help me understand", or wants to learn concepts from first principles with interactive comprehension checks. DO NOT USE WHEN: user wants quick answers, code implementation, or already understands the concept and just needs a reminder.

Use when output is below demand, WIP accumulates, work centers compete for investment, product mix changes the constraint, or management must compare overtime, debottlenecking, outsourcing, and capex options.

Use when a released factory plan needs repeated checkpoints, plan-versus-actual review, blocker ownership, exception escalation, or a concise daily control room across production, sales, material, labor, quality, and cash.

Use when orders, forecasts, ship dates, routings, lead times, WIP, and capacity must be converted into a feasible production plan or when an existing plan no longer matches shop-floor reality.

Use when a factory owner asks where capital is tied up, why ROIC is weak, which operating levers could raise profit or capital turns, or what 30-90 day improvement portfolio to prioritize.

Use when a production plan, customer promise, purchase decision, or stage release depends on material quantity, grade, specification, quality clearance, supplier timing, or an approved substitute.

Use when defects, scrap, rework, customer claims, inspection holds, yield loss, or repeat quality failures are reducing margin, consuming capacity, or threatening shipment release.

Use when accepting, reprioritizing, repricing, deferring, or changing a customer order requires a joint view of demand, contribution margin, material, finite capacity, lead time, and delivery risk.

Use when a factory needs product, order, or customer cost and margin truth; a quote or price must be checked; actual cost differs from standard; or material, labor, overhead, freight, scrap, and claims must be reconciled.