VerifiedGit
v1.0.0

dotnet-backend-expert

by @johnkozaris0 pulls
URLopenbooklet.com/s/dotnet-backend-expert
Pinnedopenbooklet.com/s/dotnet-backend-expert@1.0.0
APIGET /api/v1/skills/dotnet-backend-expert

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, SignalR hubs, TypeScript/React client integration shape, pragmatic Rust interop, application services, AppHost-aware project structure, EF Core and database boundaries, dependency injection lifetimes, OOP and SOLID quality, concurrency, and distributed-architecture tradeoffs. Use when the user asks "critique my .NET backend", "review this service", "should this be singleton or scoped", "structure my solution", "review my SignalR hub", "review my AppHost", "is this clean architecture", "should I use repositories", "fix my DbContext usage", "design my REST endpoints", "review my concurrency", or "should this be microservices".

10 skills from this repojohnkozaris/jko-claude-plugins
dotnet-backend-expertviewing
Browser Automation with dev-browserplugins/dev-browser/skills/browser-automation/SKILL.md

dev-browser is a CLI that controls browsers using sandboxed JavaScript scripts. Scripts run in a QuickJS WASM sandbox (not Node.js) with Playwright Page API access plus dev-browser extensions (notably `snapshotForAI()`). Pages persist between script runs via named handles, enabling incremental multi

Claude Code plugin marketplace — Rust, ESP32 C++, Python backend, SwiftUI, dead code detectionplugins/claude-mastery/commands/mastery-skill.md
dead-code-expertplugins/dead-code/skills/dead-code-expert/SKILL.md

This skill should be used when the user wants to find, audit, or remove dead code, unused imports, unused functions, unused variables, duplicate implementations, or simplify a codebase. Works across all programming languages. Relevant when the user says "find dead code", "remove dead code", "remove unused imports", "find duplicate code", "simplify this codebase", "find unused functions", "find unused code", "remove commented out code", "what code is unused", "find orphaned files", "detect duplicate implementations", "find unreachable code", "clean up this codebase", or "audit for unused code".

electron-playwright-validatorplugins/electron-playwright-validator/skills/electron-playwright-validator/SKILL.md

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 screenshot", "does the app render", "test the electron UI", "launch the app and check", "verify the app works", "is the app broken", or "debug a runtime error".

esp32-expertplugins/esp32-cpp/skills/esp32-expert/SKILL.md

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", "optimize memory usage", "debug I2C issue", "set up PlatformIO project", "review my CMakeLists", "search datasheet for this chip", "why is my task crashing", "configure deep sleep", or "help with ESP-IDF component structure".

python-backend-expertplugins/python-backend/skills/python-backend-expert/SKILL.md

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 controller", "fix my SQLAlchemy query", "structure my project", "is this SOLID", "review my repository", "optimize my API", "design my service layer", "help with dependency injection", "set up a Litestar project", "set up a FastAPI project", "create a repository pattern", "fix my async code", "review my database models", or "fix N+1 query".

seam-probeplugins/seam-probe/skills/seam-probe/SKILL.md

`seam-probe` is a **generic** NDJSON probe for embedded-runtime seams. It ships **zero** app-specific knowledge. Everything app-specific is expressed in a small JSON **manifest** that the user (or you) writes and hands to the binary.

swiftui-expertplugins/swiftui/skills/swiftui-expert/SKILL.md

This skill should be used when the user is building, reviewing, or debugging SwiftUI views and apps. Detects iOS and Swift version from the project. Covers creating views, state management with @Observable, NavigationStack routing, animations, accessibility, performance optimization, Liquid Glass adoption, design systems, and clean code architecture. Use when the user asks things like "create a SwiftUI list view", "my @State isn't updating", "add navigation to my app", "make this accessible", "optimize SwiftUI performance", "add Liquid Glass to my toolbar", "fix my Swift concurrency warning", "set up SwiftData models", "critique my SwiftUI code", "fix my SwiftUI layout", "create a custom ViewModifier", or "add Dark Mode support".

Web Interact — Browser Automationplugins/web-interact/skills/browser-automation/SKILL.md

web-interact is a browser automation plugin powered by the `web-interact` CLI. Scripts run in a QuickJS WASM sandbox with Playwright Page API access plus CDP-based element discovery and interaction. Pages persist between script runs via named handles, enabling incremental multi-step workflows.

Auto-indexed from johnkozaris/jko-claude-plugins

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0