pavel-molyanov
18 verified skills3,960 total stars
code-reviewing
Code review methodology and quality standards for comprehensive code analysis. Use to understand WHAT and HOW to review code: 11 review dimensions, process, quality standards. Use when: "проверь код", "code review", "ревью кода", "review this code", "check code quality"
development220
methodology
AI-First development methodology: spec-driven pipeline, project structure, skills/agents ecosystem, quality gates. Use when: "изучи методологию", "изучи глобальную папку", "как работает методология", "how does the methodology work", "explain the workflow" For infrastructure tasks, use infrastructure-setup or deploy-pipeline skills.
development220
skill-tester
Test skills end-to-end: design test cases, run with/without skill, grade results, test description triggering accuracy, produce improvement report. Use when: "протестируй скилл", "запусти тесты для скилла", "проверь скилл", "run skill tests", "test this skill", "skill eval", "оцени скилл", "придумай тесты для скилла", "создай сценарии тестирования"
testing220
task-decomposition
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec"
tools220
test-master
Testing methodology: when to write which tests, how to ensure test quality, test pyramid strategy. Use when: "напиши тесты", "как тестировать", "проанализируй тесты", "проверь качество тестов", "ревью тестов", "тестовая стратегия"
testing220
code-writing
Universal quality coding process: plan, TDD, reviews. Use whenever code needs to be written — ad-hoc or as part of a task. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" For planning tasks → tech-spec-planning skill. For specs → user-spec-planning skill.
development220
infrastructure-setup
Sets up dev infrastructure for new projects: framework init, folder structure, Docker, pre-commit hooks (gitleaks), testing infrastructure, .gitignore. Use when: "настрой инфраструктуру", "подготовь проект", "настрой тесты", "настрой проверки при коммите", "настрой проверки при пуше", "setup infrastructure"
development220
skill-master
Guide for creating/updating skills with specialized knowledge and workflows. Use when: "создай скилл", "измени скилл", "гайд по скиллам", "обнови скилл", "улучши скилл", "create skill", "update skill", "skill guide", "new skill", "how to write a skill"
testing220
feature-execution
Orchestrate feature delivery as team lead: spawn agents by wave, manage review cycles (max 3 rounds), commit per wave. Use when: "выполни фичу", "do feature", "execute feature", "запусти фичу", "выполни все задачи", "execute all tasks"
data-ai220
documentation-writing
Maintain project documentation in .claude/skills/project-knowledge/: audit, edit, check consistency, track status. Use when: "проверь документацию", "обнови документацию", "аудит документации", "check docs", "audit documentation", "update docs", "проверь базу знаний проекта" For creating documentation from scratch use project-planning skill. For reading docs or explaining concepts, read project-knowledge skill directly.
testing220
tech-spec-planning
Creates tech-spec.md with architecture, decisions, testing strategy, and implementation plan. Use when: "сделай техспек", "составь техспек", "техническая спецификация", "tech spec", "создай тз", "составь тз", "new-tech-spec", "/new-tech-spec" Requires existing user-spec.md as input (create with user-spec-planning skill first if missing).
testing220
security-auditor
Comprehensive security analysis against OWASP Top 10 standards. Use after code-reviewer for code handling: authentication, user input, database queries, external APIs. AUTOMATIC TRIGGER - Invoke when user says ANY of: "проверь безопасность", "security audit", "найди уязвимости", "check security" Do NOT use for: general code review (use code-reviewer), testing (use test-reviewer)
development220
deploy-pipeline
Sets up CI/CD pipelines, deployment configuration, and automated deploy workflows. GitHub Actions, platform-specific deploy (Vercel, Railway, Fly.io, AWS, VPS), secrets management in CI. Use when: "подготовь деплой", "настрой автодеплой", "настрой CI/CD", "setup deploy", "configure deployment", "настрой пайплайн"
testing220
user-spec-planning
Creates user-spec.md through adaptive interview with codebase scanning and dual validation. Use when: "сделай юзер спек", "проведи интервью для юзер спека", "создай юзерспек", "user spec", "detailed planning", "хочу продумать фичу", "опиши требования к фиче", "сделай описание фичи", "/new-user-spec" For tech planning use tech-spec-planning. For project planning use project-planning.
development220
pre-deploy-qa
Pre-deploy acceptance testing methodology: run test suite (unit/integration/E2E), verify acceptance criteria from user-spec and tech-spec. Does not require live environment. Use when: "приёмочное тестирование", "pre-deploy qa", "проверь перед деплоем", "run tests and check AC", "запусти qa", "проверь acceptance criteria", "тестирование фичи", "qa", "проверь фичу"
testing220
project-planning
Plan new projects: adaptive interview, tech decisions, fill all project documentation (project-knowledge) in one session. Use when: "сделай описание проекта", "запиши описание проекта в документацию", "проведи со мной интервью для описания проекта", "заполни документацию проекта", "начни планирование проекта", "давай опишем проект", "plan a new project", "fill project documentation"
testing220
post-deploy-qa
Post-deploy verification: execute AVP from tech-spec on live environment, verify all acceptance criteria (user-spec + tech-spec), pick up deferred criteria from pre-deploy QA report. Uses MCP tools (Telegram MCP, Playwright, curl, bash). Use when: "пост-деплой проверка", "post-deploy verification", "проверь после деплоя", "MCP verification", "верификация на живом окружении", "проверь деплой", "запусти AVP", "agent verification plan"
tools220
prompt-master
Guide for writing effective prompts for LLMs. Use when: "напиши промпт", "улучши промпт", "prompt engineering", "проверь промпт"
documentation220