Drive a UI flow with chrome-devtools, capture a screenshot per step, then render a self-contained HTML report (report.html) showing each step with status pills, full console log, and full network log per step. Use when: (1) User asks to "QA this flow", "walk through X with screenshots", "verify [feature] end-to-end with a report" (2) User wants screenshot-backed evidence that a multi-step UI flow worked (3) User wants a single artifact they can attach to a PR or share as proof of a manual walkthrough Do NOT use for one-off "open this page and check console", for automated regression testing (a Playwright/Cypress suite is the right tool), or for single-screenshot bug repros. Triggers: "QA this flow", "qa flow report", "walk through X with screenshots", "verify end-to-end with a report", "screenshot-backed evidence", "manual QA report"
Rewrite glazy, eye-glazing generated content into a tight, scannable, bullet-tight engineering voice. Use when the user says "unglaze", "ungloss this", "punch this up", "tighten this", "less glazy", "eyes glaze", "make my eyes not glaze", "cut the fluff", "rewrite punchier", "make it sharper", "less corporate", "de-fluff", "less LLM-flavored". Also auto-triggers on dissatisfaction signals like "ugh too long", "tldr this", "this is boring", "too much". Applies to PR review output, research summaries, design docs, plans, proposals, and any human-readable artifact the agent produced or the user shared. Out of scope: meeting transcripts (handled by message-in-a-bottle / uncork).
Comprehensive PR review using 7 specialized review protocols covering code quality, test coverage, error handling, type design, comment accuracy, code simplification, and component coupling. Use when reviewing PRs, preparing code for merge, or auditing specific aspects of code changes. Triggers: "review PR", "review my PR", "PR review", "review pull request", "check test coverage", "review error handling", "analyze types", "check comments", "simplify code", "code review", "pre-merge review", "check coupling", "review coupling", "orthogonality review".
Transcribe audio and video files using Audetic whisper service. Use when: (1) User wants to transcribe an audio or video file (2) User has a recording and needs a text transcript (3) User wants transcript analysis (gaps, speech rate, silence detection) (4) User wants to transcribe all media files in a directory Triggers: "transcribe", "transcription", "transcript", "speech to text", "audio to text", "transcribe audio", "transcribe video", "transcribe recording"
Conversational video editing: transcribe, plan edits using transcript analysis, and render. Use when: (1) User wants to edit a video by reviewing its transcript (2) User asks to trim, cut, or rearrange video segments (3) User wants to create a highlight reel or narrative cut from a longer video (4) User mentions EDL, transcript analysis, or video editing workflow (5) User wants to remove filler, dead air, or silence from a video (6) User wants to combine multiple clips into one video Triggers: "edit video", "transcribe video", "trim video", "cut video", "EDL", "video editing", "remove filler", "combine videos", "stitch clips", "multiple clips", "add captions", "shorts captions", "burn captions"
Apply proven marketing principles for compelling copy, campaigns, and brand positioning. Use when writing marketing copy, taglines, product descriptions, campaign concepts, brand messaging, landing pages, or any customer-facing content. Triggers: "marketing copy", "tagline", "campaign", "brand voice", "product messaging", "landing page copy", "value proposition", "brand positioning", "launch announcement", "promotional content".
Testing Trophy philosophy for JS/TS. Use when: writing tests, deciding what/how to test, reviewing tests, choosing unit/integration/E2E, mocking decisions. Triggers: "write tests", "what should I test", "test this component", "review my tests", "testing strategy", "mock this", "test setup".
Concrete, testable heuristics for writing and reviewing orthogonal (decoupled) code. Use when: (1) Writing new modules and wanting to ensure independence from day one (2) Reviewing PRs or existing code for coupling problems (3) Refactoring tightly-coupled systems toward better separation (4) Discussions mention orthogonality, coupling, decoupling, SOLID, Law of Demeter, or connascence (5) Evaluating whether a design change will increase or decrease coupling (6) Deciding how to split responsibilities between modules Complements the `system-design` skill (deep modules, information hiding, complexity). This skill focuses specifically on component independence. Draws from The Pragmatic Programmer, SOLID principles, Law of Demeter, Connascence theory, and UNIX philosophy.