con un clic
molyanov-ai-dev
molyanov-ai-dev contiene 51 skills recopiladas de pavel-molyanov, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
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.
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.
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.
Converted Codex workflow from Claude slash command `decompose-tech-spec-coarse`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `decompose-tech-spec`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `do-feature`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `do-task`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `done`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `init-project-knowledge`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `new-tech-spec-coarse`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `new-tech-spec`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `new-user-spec`. Use when the user asks to run the equivalent command or describes this workflow.
Converted Codex workflow from Claude slash command `write-code`. Use when the user asks to run the equivalent command or describes this workflow.
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.
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"
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"
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"
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", "проверь фичу"
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"
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", "оцени скилл", "придумай тесты для скилла", "создай сценарии тестирования"
Decompose approved coarse tech-spec into task files with parallel creation and validation. Coarse variant: each Implementation Task in tech-spec produces one task file covering one skill's cohesive scope. Use when: "разбей на задачи coarse", "декомпозиция крупно", "разбей задачи крупно", "крупная декомпозиция задач", "decompose tech-spec coarse", "skill-scoped tasks", "one task per skill", "task decomposition coarse", "/decompose-tech-spec-coarse"
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec"
Creates tech-spec.md with architecture, decisions, testing strategy, and coarse implementation plan. Coarse variant: groups related work into skill-scoped tasks instead of atomic ones. Fewer tasks, each covers one skill's cohesive scope in the feature. Use when: "сделай техспек coarse", "составь техспек крупно", "техспек крупными задачами", "подготовь техспек крупно", "группировка задач по скиллам", "tech spec coarse", "new-tech-spec-coarse", "/new-tech-spec-coarse", "крупная декомпозиция", "one task per skill", "skill-scoped tasks", "group related work" Requires existing user-spec.md as input (create with user-spec-planning skill first if missing).
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).
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.
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"
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", "проверь фичу"
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"
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", "оцени скилл", "придумай тесты для скилла", "создай сценарии тестирования"
Decompose approved coarse tech-spec into task files with parallel creation and validation. Coarse variant: each Implementation Task in tech-spec produces one task file covering one skill's cohesive scope. Use when: "разбей на задачи coarse", "декомпозиция крупно", "разбей задачи крупно", "крупная декомпозиция задач", "decompose tech-spec coarse", "skill-scoped tasks", "one task per skill", "task decomposition coarse", "/decompose-tech-spec-coarse"
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec"
Creates tech-spec.md with architecture, decisions, testing strategy, and coarse implementation plan. Coarse variant: groups related work into skill-scoped tasks instead of atomic ones. Fewer tasks, each covers one skill's cohesive scope in the feature. Use when: "сделай техспек coarse", "составь техспек крупно", "техспек крупными задачами", "подготовь техспек крупно", "группировка задач по скиллам", "tech spec coarse", "new-tech-spec-coarse", "/new-tech-spec-coarse", "крупная декомпозиция", "one task per skill", "skill-scoped tasks", "group related work" Requires existing user-spec.md as input (create with user-spec-planning skill first if missing).
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).
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.
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"
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.
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", "настрой пайплайн"
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"
Sets up dev infrastructure for new projects: framework init, folder structure, Docker, pre-commit hooks (gitleaks), testing infrastructure, .gitignore. Use when: "настрой инфраструктуру", "подготовь проект", "настрой тесты", "настрой проверки при коммите", "настрой проверки при пуше", "setup infrastructure"
Guide for writing effective prompts for LLMs. Use when: "напиши промпт", "улучши промпт", "prompt engineering", "проверь промпт"