Code smell detector for Ruby

Design, implement, and review Kotlin and Android APIs. Use when working on .kt files, Kotlin nullability, sealed classes/interfaces, coroutines, Android threading, Java interop, or Kotlin-backed React Native Nitro Module implementations.

Design, implement, and review modern C++ APIs and native implementation code. Use when working on .cpp, .hpp, CMake, RAII ownership, std::variant, callbacks, async work, platform bridges, or C++-backed React Native Nitro Module implementations.

Audit a repository for architectural decay, AI-generated code smells, stale compatibility paths, dead abstractions, boundary violations, and cleanup candidates without modifying files. Use when the user asks to review code quality, find bad code, inspect AI-generated code, identify refactoring or cleanup opportunities, detect legacy leftovers, or produce a cleanup backlog that requires human confirmation before implementation.

16-dimension test suite audit with depth control (quick/standard/deep), gap matrix, and health scoring. Covers coverage, quality, mocking, data management, CI/CD, performance, mutation testing, and modern patterns. Use when evaluating test suite quality, identifying testing gaps, or assessing test infrastructure health.

Steward the vanillagreencom/kendex issue queue (Linear team KEN is the poll surface; GitHub stays the PR/code surface) on a self-paced loop: watch open PRs, poll, triage (dedupe; close non-kendex issues and repost project-local ones to their owning repo; fix genuine defects in kendex's skills/agents/hooks/pi-extensions or the Rust CLI), run each fix through the orch skill, merge, propagate via kendex refresh, then reschedule. A thin wrapper: fix cycles belong to orch, PR mechanics to the github skill, PR monitoring to review-gate's pr-watch, Linear ops to the linear skill — this skill carries only the kendex-specific stewardship knowledge. Use when asked to monitor kendex's issues continuously or to run one fix-and-propagate cycle.

Use when generating, planning, authoring, or recording an Epic Web / Epic React style workshop, exercise, tip, or video. Applies Kent C. Dodds' "How to be an Epic Instructor" principles to workshop design, exercise structure, recording, and material delivery, and encodes Epic Web's exercise-comment emoji conventions. Used to generate workshops following https://www.epicweb.dev/get-started. Triggers on "create a workshop", "generate a workshop", "design an exercise", "record a workshop video", "Epic workshop", "Epic Web", "Epic React", or `/epic-workshop`.

Runs a realistic mock interview in chat — builds an interviewer persona from the intel file, asks one question at a time with pressure follow-up chains, then scores the candidate on structured delivery, evidence density, role fit, follow-up resilience and recitation-smell, writing a report to the workspace. Use when the user wants practice, says 模拟面试 / 陪我练一下 / 当一回面试官 / 压力面 / mock interview, or when an interview is within 48 hours and the script is ready. Do NOT use for writing answers (interview-script) or reviewing a real past interview (debrief).