Claude Skills by DmitriyYukhanov

Set up and orchestrate Claude Code agent teams - multiple Claude Code instances working together with shared tasks, inter-agent messaging, and centralized management. Use when the user wants to (1) create or start an agent team for parallel work, (2) configure agent team settings like display mode or teammate mode or permissions, (3) coordinate teammates for code review or debugging or feature development or research, (4) understand when to use agent teams vs subagents, (5) troubleshoot agent...

Slim or restructure an oversized CLAUDE.md into path-scoped .claude/rules/ files, verifying nothing was lost. Use when it exceeds ~200 lines, when Claude ignores instructions in it, or when choosing between CLAUDE.md, rules, skills and @import.

Sequential drive/validate/act collaboration between Claude and Codex. Claude analyzes, Codex validates each finding, both models must agree before action. Use when you want iterative improvement with bilateral consensus.

Parallel dual review between Claude and Codex. Both models review independently. Findings confirmed by reviewer agreement, cross-validation, or evidence research are auto-applied each round; only genuinely inconclusive disagreements surface for user decision. Use for reviewing existing work with independent perspectives.

Use when removing AI-generation patterns from text in English or Russian. Auto-detects language by Cyrillic ratio and applies the matching ruleset. Trigger phrases: "humanize this", "remove AI patterns", "make this sound human", "очеловечить текст", "убрать признаки нейросети", "сделай текст живым". Honors explicit overrides like "humanize as English" / "обработай как русский". For mixed-language text, asks which ruleset to apply.

Create implementation-ready PRD/spec bundles for new apps, products, services, platforms, mobile or desktop software, SaaS systems, or complex features. Use when the user asks for a detailed PRD, build-ready spec, spec bundle, spec packet, PRD + contracts + schema + test plan, backend or API spec, frontend or mobile app spec, feature requirements, technical product brief, or documentation that Claude Code or Codex can implement with minimal follow-up or one-shot implementation. Produce a deci...

Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card, then merges and cleans up once you approve the PR in-session. Triggers: "take task N", "work on issue #N", "build/fix X" when no issue exists yet, and — for the merge gate later — "...

Check what issue-to-pr needs and what would sharpen it, then hand over the exact install commands. Use when the user asks what issue-to-pr needs, or hits a Step 0 failure about gh auth or a missing scope. Verifies gh auth and its scopes, reports which companion skills are present and what each missing one would sharpen, and explains the optional config file. Prints commands for the user to run; installs nothing itself.

Reads input artifact(s) — codebase, planning session, refactor plan, or generic doc — and writes a tour-spec.json describing sections, embedded sources, cross-refs, quizzes, and external link maps. Use when the user wants a fresh learning guide built from source material; auto-hands-off to learning-guide:render. Trigger phrases — "create a learning guide for X", "make an interactive tour", "generate onboarding doc", "build a learning module".

Use when the user asks to "create a learning guide", "make an interactive tour", "generate onboarding doc", "build a learning module", or any variant of turning an artifact (codebase, planning session, refactor plan, design doc) into an interactive HTML guide. Dispatches to learning-guide:analyze for new tours or learning-guide:render for re-renders after spec edits. Also use when the user is uncertain which step they need.

Renders an existing tour-spec.json to a single-file interactive HTML guide via the bundled Node renderer. Use when the user has hand-edited a tour-spec.json, when learning-guide:analyze hands off after drafting, or when the user explicitly asks to "render the tour", "regenerate the HTML", or "update the embedded sources". Idempotent for generated artifacts; preserves user-edited README and tour-spec.json.

This skill should be used when the user asks to "set up LSP", "configure LSP", "install LSP", "enable LSP", "language server setup", "add LSP to project", "configure language server", "set up code intelligence", "validate LSP", "check LSP setup", "fix LSP", "LSP not working", or wants to enable or troubleshoot LSP-powered navigation (go-to-definition, find-references, hover, diagnostics) in Claude Code for a project.

Creates high-level Python architecture with protocols, test stubs, and module structure. Use when designing Python projects or features.

Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.

Python testing patterns with pytest including unit tests, integration tests, fixtures, mocking, and coverage. Use when writing Python tests.

Use when adding Telegram error notifications to any project. Guides through bot creation with @BotFather, chat/channel/forum-topic ID discovery, alert service implementation with deduplication and graceful failure, and framework-specific integration for Python (async/sync) and Node.js.

Set up Telegram voice message transcription — checks faster-whisper installation, downloads the Whisper model, and verifies the hook works end-to-end. Use when the user asks to "set up voice transcription", "configure whisper", "fix voice messages", or when the transcription hook reports that whisper is missing or the model isn't downloaded.

Creates high-level TypeScript architecture with interfaces, test stubs, and module structure. Use when designing TypeScript/JavaScript projects or features.

Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.

TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.

Use when designing Unity architecture, creating component hierarchies, defining interfaces, or generating test stubs and Mermaid diagrams for Unity projects

Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns

Start Unity C# development workflow with architecture, implementation, review, and testing phases

Use when running Unity from CLI for any purpose — builds, tests, method execution, asset imports. Handles Unity installation detection, batchmode execution, and log monitoring. Other unity-dev skills depend on this for CLI execution.

Run Unity Test Framework tests via CLI batchmode with auto-detection of Unity installation

Use when writing Unity tests, including EditMode tests, PlayMode tests, performance testing, and code coverage