Claude Skills by johnkozaris

Use this skill when validating a backend API or WebSocket endpoint end-to-end, including acquiring an OIDC bearer token for authenticated calls. Trigger whenever the user asks to test/validate/smoke-check a backend, write a Hurl test, hit a WebSocket, acquire an access token, exercise an OIDC flow, debug a 401, or verify an endpoint works with real auth. Applies to projects that use Hurl for HTTP tests, websocat for WebSocket probes, and oauth2c or curl-based flows for token acquisition (Auth...

Help me create a new Claude Code skill following best practices. Interview me using the AskUserQuestion tool to understand: 1. What category does this skill fall into? (Library/API Reference, Product Verification, Data Fetching, Business Process, Code Scaffolding, Code Quality, CI/CD, Runbook, Infrastructure Operations) 2. What problem does this skill solve? 3. What triggers should activate this skill? (specific phrases, situations, contexts) 4. What tools or commands does the skill need? 5. ...

This skill should be activated when the user wants to build an agent, design tools for an agent, write skills, structure a CLAUDE.md, optimize prompt caching, set up worktrees, use subagents, design verification loops, write hooks, structure a project for Claude Code, or improve their Claude Code workflow. Relevant when the user says "how should I structure this", "write a skill for", "design this agent", "optimize for caching", "set up verification", "use subagents", "parallel development", ...

This skill should be used when the user wants to find, audit, or remove dead code, unused imports, unused functions, unused variables, duplicate implementations, parallel/split-brain implementations across architectural boundaries, dead assets/configuration/infrastructure, or simplify a codebase. Works across all programming languages and stacks (SwiftUI, Rust, TypeScript/React, .NET, Python, C++, Go, Java). Relevant when the user says "find dead code", "remove dead code", "remove unused impo...

This skill should be used when the user is writing, reviewing, debugging, or architecting pure .NET backend code for Kestrel-hosted services. It provides expert critique for REST endpoints, real-time transports (SignalR, raw WebSockets, Server-Sent Events), TypeScript/React client integration shape, pragmatic Rust interop, application services, project structure, EF Core and database boundaries, dependency injection lifetimes, OOP and SOLID quality, concurrency, and distributed-architecture t...

Validate Electron desktop app UI using Playwright automation via the e-cli tool. Use when testing Electron app UI, validating after code changes, checking if tabs render, clicking through UI flows, taking screenshots for visual review, or debugging runtime import errors that typecheck doesn't catch. Works with any Electron project that has @playwright/test and electron in devDependencies. Use when the user asks "validate the electron app", "check the UI", "click through the app", "take a scre...

This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO), build systems (CMake/platformio.ini), power management, OTA updates, and embedded C++ best practices. Use when the user asks "review my ESP32 code", "fix FreeRTOS crash", "optimi...

Use this skill when writing or running Maestro flows for iOS or Android apps, driving the Maestro MCP server, diagnosing flaky mobile UI tests, or onboarding a new team to mobile e2e testing. Trigger whenever the user mentions Maestro, mobile testing, iOS Simulator flows, Android emulator flows, "test my app", YAML test flows, GraalJS test scripting, assertVisible / tapOn / launchApp, deep links from tests, or "why is my Maestro test flaky". Applies to Swift/SwiftUI, React Native, Flutter, Ko...

Drive, observe, and critique any running macOS app end-to-end via Peekaboo — the macOS-native equivalent of Playwright + visual-regression review for SwiftUI/AppKit. Use proactively whenever the user mentions UI, screens, screenshots, the app's appearance, layout, spacing, alignment, copy/labels, sidebar, panels, settings, theme, accessibility identifiers, clicking, typing, menus, file pickers, responsive sizing, or animations — or says any of: 'verify it works', 'see what it looks like', 'sh...

This skill should be used when the user is writing, reviewing, debugging, or architecting Python backend code using Litestar or FastAPI with SQLAlchemy or Advanced Alchemy. Provides expert critique covering SOLID principles, hexagonal architecture, repository/service patterns, dependency injection, async correctness, ORM usage, API design, anti-pattern detection, and modern Python patterns for mature production backends. Use when the user asks "critique my Python backend", "review this contro...

This skill should be used when the user is writing, reviewing, debugging, or architecting Rust code. Detects edition and toolchain from the project. Provides expert critique covering ownership, error handling, unsafe review, async correctness, trait design, type system patterns, performance, SOLID principles, and Cargo/workspace practices. Use when the user asks "critique my Rust code", "review this module", "fix borrow checker error", "is this unsafe sound", "design error types", "optimize t...

Use this skill to test, validate, fuzz, or debug a process boundary ("seam") that exposes itself as an FFI dynamic library or a Unix-domain socket — for example probing a Rust runtime hosted in a Swift or Electron app via its C ABI, or sending crafted length-prefixed frames to a daemon's UDS endpoint. The skill teaches how to drive the probe from the CLI, capture both the probe's NDJSON output AND the system- under-test's stderr/logs, and triage failures by correlating the two streams. Reach ...

This skill should be used when the user is building, reviewing, or debugging SwiftUI/Swift code for iOS, macOS, or visionOS apps. It detects the project's iOS and Swift version and covers MV architecture (no per-screen ViewModels by default), @Observable state, NavigationStack typed routes, view lifecycle, Approachable Concurrency, persistence with SwiftData / Core Data / SQLiteData / GRDB, design tokens, selective Liquid Glass adoption, iOS native capabilities (App Intents, Widgets, Live Act...

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 ...

Acquire a development OIDC access token through the project's token command or the bundled macOS PKCE script

Run the project's Hurl scenarios with an OIDC access token passed as a secret variable

Run a bounded, protocol-aware WebSocket probe with an OIDC bearer token

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, hallucinate...

Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence

Validate requested or discovered states in a native macOS app while preserving prior app state