smykla-skalski

Staff-engineer-level code review that goes beyond correctness to evaluate architectural alignment, system-level implications, failure modes, performance, scalability, backward compatibility, observability, security, and cross-team impact. Use when reviewing a PR (URL or diff), analyzing code changes for architectural fitness, or when the user asks for a thorough/staff-level/senior review of code changes. Triggers on "review this PR", "review these changes", "staff review", "thorough code review", sharing a GitHub PR URL for review, or asking about the architectural impact of changes.

Produce a daily AI news digest and reuse the source workflow under `claude/ai-daily-digest`. Use when the user wants a curated AI briefing or roundup in Codex.

List, reply to, resolve, unresolve, and create GitHub PR review comment threads using gh CLI scripts.

Clean stale local branches and worktrees by reusing the source workflow under `claude/git-clean-gone`. Use when merged or abandoned work leaves gone branches behind.

Stage selected git hunks non-interactively by reusing the source workflow under `claude/git-stage-hunk`. Use when only part of a file should be committed.

Review Go code using the source material under `claude/go-code-review`. Use when the user wants a focused Go review grounded in known failure patterns.

Rewrite text to sound less formulaic by reusing the source workflow under `claude/humanize`. Use when the user wants writing to sound more natural in Codex.

Draft and refine KubeCon CFPs by reusing the source workflow under `claude/kubecon-cfp`. Use when the user wants to assess or improve a KubeCon proposal in Codex.

Record macOS screen with verification, retry logic, and format conversion for Discord, GitHub, JetBrains. Integrates with window-controller for window discovery.

Find text in images using EasyOCR, returning click coordinates. Works on any image (screenshots, UI captures, etc.) without requiring accessibility permissions. Useful for UI automation, finding buttons/labels in screenshots, and extracting text positions.

Find and switch to macOS Spaces/Desktops by application name. Use when asked to find which Space an app is on, switch to a Space containing a specific app (like GoLand, IntelliJ, VS Code), navigate between Mission Control Spaces, or detect full-screen application windows across desktops.

Capture macOS screenshots with verification and retry logic. Integrates with window-controller for window discovery.

Find, activate, and screenshot macOS windows across Spaces. Filter by app name, window title, process path, or command line. Useful for automating window workflows, capturing screenshots for documentation, and distinguishing between production and sandbox/dev instances (e.g., JetBrains IDEs).

Complete guide for investigating and implementing web browser automation. Use when you need to automate browser interactions but don't know the DOM structure, element IDs, or what tools to use. Covers investigation methodology, selector discovery, tool selection, debugging techniques, and common pitfalls for any web automation scenario.

Programmatic control of Chrome and Firefox browsers via CDP (Chrome DevTools Protocol) and Marionette. Connect to running browser instances for tab management, navigation, DOM interaction, form filling, JavaScript execution, and screenshots. Useful for browser automation, web scraping, and testing.

SwiftUI API usage rules for the Harness Monitor macOS app. Covers state wrappers (@State/@Binding/@Observable/@Bindable), view composition (structs over free functions, @ViewBuilder, modifier branches, ForEach identity), Picker/selection identity, button styles (.glass/.glassProminent, no .plain, ButtonStyle conformance, AccentColor), drag-and-drop (.draggable/.dropDestination, DragSession.Phase), navigation, lists, animations, layout, keyboard/focus, window management, commands, and anti-patterns. Invoke when writing or reviewing SwiftUI view structs, view state, selection controls, buttons, drag-drop interactions, navigation, or any SwiftUI-specific API usage in apps/harness-monitor/Sources.

SwiftUI/macOS UX rules covering accessibility (VoiceOver, Dynamic Type, contrast, target sizes), visual design (typography, 8pt spacing, color, dark mode, motion timing), interaction patterns (feedback, loading states, destructive actions, forms, truncation, notifications), and performance targets (60fps, launch time, scroll, memory). Invoke when writing or reviewing SwiftUI views, forms, lists, or any visible UI surface in apps/harness-monitor.

SwiftUI and Harness Monitor performance rules. Covers no DateFormatter/JSONEncoder/NumberFormatter allocation in view body, cached @MainActor formatters, no .repeatForever on always-visible views, no persisted state in .inspector/.searchable on first frame, no mirror-state loops for store-backed selection, no geometry feedback loops during animation, OSSignposter contract (io.harnessmonitor/perf/<scenario>), perf test env vars (HARNESS_MONITOR_KEEP_ANIMATIONS), and isolated worktree requirements for `mise run monitor:audit`. Invoke when writing or reviewing performance-sensitive SwiftUI code, animations, formatters, startup flow, persisted layout state, XCTest perf tests, or running Instruments audits in apps/harness-monitor.

macOS and iOS platform conventions plus XCUITest reliability rules. Covers menu bar ordering, window chrome (traffic lights, corner radius, minimum size), toolbar placements, sidebar width, Settings scene, dock/notifications, standard keyboard shortcuts (Cmd+N/O/S/W/Q/Z/F/,/M), iOS tab bar and safe areas, gestures, and XCUITest patterns (three-layer animation suppression, .firstMatch required, coordinate taps for non-hittable elements, single-launch test design, dragUp scroll helper, no Section-level accessibilityIdentifier). Invoke when writing or reviewing macOS window/menu/toolbar/settings code, platform-convention questions, iOS surfaces, or XCUITest tests in HarnessMonitorUITests.

Investigates JetBrains IntelliJ Platform theme properties by searching source code. Use when user asks about UI theming, icon colors, tab spacing, component styling, or needs to find what properties are themeable vs hardcoded in IntelliJ-based IDEs.