@levnikolaevich

ln-774-healthcheck-setup configures kubernetes health check endpoints (liveness, readiness, startup) for .net and python applications, auto-detecting dependencies from project manifests and generating probe configurations with validated timing parameters.

ln-721-frontend-restructure handles react project scaffolding and monolith-to-components migration via two distinct modes. scaffold generates minimal vite+typescript starter files. restructure applies ordered transformations (analyze, plan, execute, verify) to extract types, constants, hooks, and ui components into feature folders with updated imports.

ln-221-story-creator automates 9-section story document generation with INVEST validation, supporting both standalone and coordinator-managed flows via pluggable tracker providers.

ln-230-story-prioritizer applies RICE scoring to rank Stories by business value, market size, and competitive position. outputs a prioritized table for sprint planning after Stories are created by ln-220.

ln-770-crosscutting-setup orchestrates logging, error handling, cors, health checks, and api docs configuration across .net and python backends by detecting project stack, checking existing setup, conditionally invoking five specialist workers, and generating a unified entry point.

ln-522-manual-tester creates bash test scripts to verify story acceptance criteria against running code via curl (api) or puppeteer (ui), saving results persistently and reporting verdicts to trackers.

ln-112-project-core-creator generates 4 baseline documentation artifacts (requirements, architecture, tech stack, patterns catalog) from coordinator-provided context. operates within skill orchestration chain, performs auto-discovery and placeholder substitution, applies 16-question self-validation.

Scaffolds new or restructures existing projects to Clean Architecture. Use when setting up project structure.

Configures global exception handling middleware. Use when adding centralized error handling to .NET or Python backends.

Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.

Checks bootstrap initialization, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Use when auditing app lifecycle.

Generates .NET Clean Architecture backend structure from entity definitions. Use when bootstrapping .NET backend projects.

Checks layer boundary violations, transaction boundaries, session ownership, cross-layer consistency. Use when auditing architecture layers.

Sets up security scanning for secrets and dependency vulnerabilities. Use when adding security infrastructure to a project.

Scores each test by portfolio value and returns KEEP/DELETE/MERGE/REWRITE. Use when pruning test-suite cost.

Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user…

Identifies missing tests for unique critical local logic: money, auth, permissions, data integrity, algorithms, and domain rules. Use when auditing critical…

Configures ESLint, Prettier, Ruff, mypy, and .NET analyzers. Use when setting up linting and formatting for a project.

Checks outdated packages, unused deps, reinvented wheels, CVE/CVSS vulnerability scan. Use when auditing dependencies.

Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.

Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.

Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.

Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Use when Story needs a test task with prioritized scenarios.

Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts. Use when auditing API contracts.

Executes Story tasks in priority order (To Review, To Rework, Todo). Use when Story has planned tasks ready for implementation.

Configures environment variables and secrets protection. Use when setting up .env files and gitignore rules for a project.

Orchestrates test planning pipeline: research, manual testing, automated test planning. Use when Story needs comprehensive test coverage planning.

Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.

Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured…

Builds and launches Docker containers with health verification. Use when validating that containerized services start correctly.

Generates seed data from ORM schemas or entity definitions to any target format. Use when populating databases for development.

Analyzes single pattern implementation, calculates compliance/completeness/quality scores, identifies gaps. Use when auditing a specific pattern.

Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.

Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.

Audits physical architecture structure: modules, domains, layer layout, junk drawers, and framework placement. Use for structure drift.

Checks async races, thread safety, TOCTOU, deadlocks, blocking I/O, resource contention. Use when auditing concurrency safety.

Generates GitHub Actions CI workflow configuration. Use when adding continuous integration to a project.

Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.

Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build config issues. Use when auditing build health.

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Story-level quality gate with 4-level verdict (PASS/CONCERNS/FAIL/WAIVED) and Quality Score. Use when Story is ready for quality assessment.

Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.

Sets up linters, pre-commit hooks, and test infrastructure. Use when adding code quality tooling to a project.

Audits whether test results can be trusted: flakiness, isolation, real external dependencies, time/random/order dependency, and shared state. Use when auditing…

Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.

Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.

Configures structured JSON logging with Serilog (.NET) or structlog (Python). Use when adding logging to backend projects.

Detects tests proving platform behavior instead of local product behavior. Use when auditing product-behavior focus.

Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.

Checks structured logging, health checks, metrics collection, request tracing, log levels. Use when auditing observability.

Scans codebase for hardcoded secrets with severity classification and remediation guidance. Use when auditing a project for leaked credentials.

Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.

Removes platform-specific artifacts from Replit, StackBlitz, CodeSandbox, Glitch. Use when preparing exported projects for production.

Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.

Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.

Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.

Discovers custom modules replaceable by OSS, evaluates alternatives (stars, license, CVE), generates migration plan. Use when reducing custom code.

Builds dependency graph, detects cycles, validates boundary rules, calculates coupling metrics (Ca/Ce/I). Use when auditing dependency structure.

Use when coordinating story quality evaluation with mandatory research, worker summaries, agent review, regression evidence, and bounded refinement.

Auto-fixes low-risk tech debt (unused imports, dead code, commented-out code) with >=90% confidence. Use when audit findings need safe automated cleanup.

Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.

Checks DRY, KISS/YAGNI, error handling, DI patterns. Use when auditing code principles compliance.

Use when auditing persistence and runtime performance through the evaluation platform with mandatory research, coordinated data-layer workers, and structured…

Checks blocking IO in async, unnecessary allocations, sync sleep, string concat in loops, redundant copies. Use when auditing runtime performance.

Checks transaction scope, missing rollback handling, long-held transactions, trigger/notify interaction. Use when auditing transaction correctness.

Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.

Checks redundant fetches, N+1 loops, over-fetching, missing bulk operations, wrong caching scope. Use when auditing query efficiency.

Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.

Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.

Creates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.

Sets up test infrastructure with Vitest, xUnit, and pytest. Use when adding testing frameworks and sample tests to a project.

ln-731-docker-generator — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.

Executes test tasks (label 'tests') through Todo to To Review with risk-based limits. Use for test task execution. Not for implementation tasks.

ln-781-build-verifier — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

Audits E2E coverage for critical user-visible journeys and wasteful E2E tests. Use when reviewing E2E journey value.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

ln-742-precommit-setup — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

ln-773-cors-configurator — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

Checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Use when implementation tasks are Done and need quality scoring.

ln-401-task-executor — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

ln-301-task-creator — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.

Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.

Checks hardcoded secrets, SQL injection, XSS, insecure deps, input validation. Use when auditing security.

Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.

Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

ln-624-code-quality-auditor — an installable skill for AI agents, published by levnikolaevich/claude-code-skills.