johnkozaris

@johnkozaris source repo

13 skills
0 followers
11 hours ago last updated

▌
Seam Probe · johnkozaris bundle
This skill should be used when testing or debugging an embedded-runtime boundary exposed through a dynamically loaded C-ABI library or Unix-domain socket, including requests to inspect exports, exercise FFI callbacks, send framed messages, reproduce seam crashes or hangs, fuzz a boundary, or correlate probe output with runtime logs. Not for ordinary APIs, HTTP/WebSocket services, static libraries, or generated bindings.

0
installs
▌
Esp32 Expert · johnkozaris bundle
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review this ESP32 FreeRTOS code", "my Arduino ESP32 sketch reboots", "why does ESP32 I2C time out", "optimize ESP32 memory", or "check this ESP32 firmware before deployment". Not for generic C++, ESP8266, or non-ESP32 targets.

0
installs
▌
Swiftui Expert · johnkozaris bundle
This skill should be used when SwiftUI work requires judgment about Observation and state ownership, view identity or lifecycle, navigation, app-target concurrency, persistence, Apple-platform behavior, accessibility, performance, or architecture. Trigger on "review this SwiftUI screen", "why isn't this view updating", "should this have a ViewModel", "fix this SwiftUI navigation", "why does this list scroll badly", "fix this main-actor warning in my app target", "review my Mac app", or "which persistence approach fits". Not for server-side Swift or routine Swift syntax. Pair it with an available platform validator when running-app evidence matters.

0
installs
▌
Code Cleanup · johnkozaris
This skill should be used when the user asks to clean up or simplify a codebase; find dead code, dead features, orphaned files, stale configuration, or unused dependencies; detect duplicate or split-brain implementations, authorities, caches, parsers, validation, or lifecycles; finish a partial migration; remove speculative abstractions or misleading comments; or perform an exhaustive every-file cleanup audit. Also trigger when cleaning AI-generated code, agent trajectory residue, hallucinated dependencies, or a passing patch that is larger than the behavior requires. Not for formatting-only cleanup, feature development, or a generic code review with no cleanup intent.

0
installs
▌
Validate Ws · johnkozaris bundle
Run a bounded, protocol-aware WebSocket probe with an OIDC bearer token

0
installs
▌
Validate API · johnkozaris bundle
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable

0
installs
▌
Get Dev Token · johnkozaris bundle
Acquire a development OIDC access token through the project's token command or the bundled macOS PKCE script

0
installs
▌
Peekaboo · johnkozaris bundle
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a UI workflow. Tasks about source, configuration, data, logs, processes, or app APIs do not need this skill unless their result must be verified in the interface. Not for Electron/web apps or iOS simulators.

0
installs
▌
Validate Mobile · johnkozaris
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence

0
installs
▌
Backend Architecture · johnkozaris bundle
This skill should be used for consequential backend architecture decisions: module or service boundaries; modular monoliths versus independent services; service extraction and data migration; data ownership and consistency; synchronous, event-driven, actor/stateful, or pipeline designs; failure isolation, backpressure, deployment topology; or deciding where orchestration and invariants belong. Trigger on requests to review or design a backend, split a service, choose a queue or communication shape, or restructure a backend that is difficult to change. Not for routine implementation, syntax questions, isolated bug fixes, or generic code review.

0
installs
▌
Validate Macos App · johnkozaris
Validate requested or discovered states in a native macOS app while preserving prior app state

0
installs
▌
Mobile Flows Maestro · johnkozaris bundle
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory or flow YAML with appId. Not for XCUITest, Appium, web, desktop, backend, or unit tests.

0
installs
▌
Electron Playwright Validator · johnkozaris bundle
This skill should be used when a user asks to launch, inspect, automate, test, validate, or debug an Electron desktop UI through Playwright/CDP, including blank renderers, runtime import failures, accessibility snapshots, layout defects, click-through flows, or post-change checks. Not for native macOS or mobile apps, browser-only pages, or unit-level IPC tests. The target project must provide Electron and Playwright.

0
installs

13 published skills