pavel-molyanov
- 27 skills
- 0 followers
- 3 hours ago last updated
- ▌ Methodology · pavel-molyanovExplains the current AI-First development methodology: skill routing, Project Knowledge, user-spec planning and execution, evidence-gated reviews, feature finalization, and the Claude/Codex dual runtime. Use when: "изучи методологию", "как работает пайплайн", "как делать фичи", "как устроены скиллы", "how does the methodology work", "explain the workflow"
- ▌ Test Master · pavel-molyanov bundleGuides test selection, authoring, and quality review at the smallest reliable boundary. Use when: "напиши тесты", "как тестировать", "проанализируй тесты", "проверь качество тестов", "ревью тестов", "тестовая стратегия"
- ▌ Code Writing · pavel-molyanovGuides code implementation through proportional context reading, focused changes, verification, and fresh reviews. Use whenever code needs to be written — from a short ad-hoc edit to a full user-spec. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" Do NOT use for pure layout from Figma, Claude Design, screenshots, or an existing visual style ("сверстай", "подвинь блок", responsive) — use layout-writing instead. Direct mixed layout + business-logic work uses both layout-writing and code-writing. For creating a user-spec → user-spec-planning skill.
- ▌ Skill Master · pavel-molyanov bundleGuides skill creation and updates with specialized knowledge and workflows. Use when: "создай скилл", "измени скилл", "гайд по скиллам", "обнови скилл", "улучши скилл", "create skill", "update skill", "skill guide", "new skill", "how to write a skill"
- ▌ Prompt Master · pavel-molyanovCreates, improves, and reviews LLM prompts using concise, task-aware guidance. Use when: "напиши промпт", "улучши промпт", "prompt engineering", "проверь промпт"
- ▌ Code Reviewing · pavel-molyanovReviews code against the user request, project conventions, cross-file contracts, and applicable quality risks. Use when: "проверь код", "code review", "ревью кода", "review this code", "check code quality"
- ▌ Layout Writing · pavel-molyanov bundleReproduces and adjusts web layouts from Figma, Claude Design exports, screenshots, or an existing project style with high visual fidelity and proportional verification. Use when: "сверстай по Figma", "поправь вёрстку", "подвинь блок", "перенеси из Claude Design", "сделай адаптив", "добавь в том же стиле", "implement layout", "match Figma", "fix responsive layout". Use alongside code-writing for mixed layout and business-logic tasks; use code-writing alone for logic-only work. Blank-slate visual design is outside this skill.
- ▌ Layout Reviewing · pavel-molyanovReviews implemented web layouts for source fidelity, responsive behavior, evidence coverage, and project consistency. Use when: "проверь вёрстку", "ревью вёрстки", "проверь адаптив", "review layout", "check visual fidelity" Do NOT use for implementing or changing layouts — use layout-writing instead.
- ▌ Security Auditor · pavel-molyanovAnalyzes changed security boundaries against applicable OWASP risks and project contracts. Use after code-reviewer when authentication, authorization, untrusted input, secrets, sensitive data, database queries, file paths, rendering, or external APIs changed. Use when: "проверь безопасность", "security audit", "найди уязвимости", "check security" Do NOT use for: general code review (use code-reviewer), test quality review (use test-reviewer)
- ▌ Methodology 2 · pavel-molyanovExplains the current AI-First development methodology: skill routing, Project Knowledge, user-spec planning and execution, evidence-gated reviews, feature finalization, and the Claude/Codex dual runtime. Use when: "изучи методологию", "как работает пайплайн", "как делать фичи", "как устроены скиллы", "how does the methodology work", "explain the workflow"
- ▌ Test Master 2 · pavel-molyanov bundleGuides test selection, authoring, and quality review at the smallest reliable boundary. Use when: "напиши тесты", "как тестировать", "проанализируй тесты", "проверь качество тестов", "ревью тестов", "тестовая стратегия"
- ▌ User Spec Planning · pavel-molyanov bundleCreates user-spec.md through adaptive interview, codebase research, and three-lane validation. Use when: "сделай юзер спек", "проведи интервью для юзер спека", "создай юзерспек", "user spec", "detailed planning", "хочу продумать фичу", "опиши требования к фиче", "сделай описание фичи", "/new-user-spec"
- ▌ Code Writing 2 · pavel-molyanovGuides code implementation through proportional context reading, focused changes, verification, and fresh reviews. Use whenever code needs to be written — from a short ad-hoc edit to a full user-spec. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" Do NOT use for pure layout from Figma, Claude Design, screenshots, or an existing visual style ("сверстай", "подвинь блок", responsive) — use layout-writing instead. Direct mixed layout + business-logic work uses both layout-writing and code-writing. For creating a user-spec → user-spec-planning skill.
- ▌ Skill Master 2 · pavel-molyanov bundleGuides skill creation and updates with specialized knowledge and workflows. Use when: "создай скилл", "измени скилл", "гайд по скиллам", "обнови скилл", "улучши скилл", "create skill", "update skill", "skill guide", "new skill", "how to write a skill"
- ▌ Prompt Master 2 · pavel-molyanovCreates, improves, and reviews LLM prompts using concise, task-aware guidance. Use when: "напиши промпт", "улучши промпт", "prompt engineering", "проверь промпт"
- ▌ Infrastructure Setup · pavel-molyanov bundleProvides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг", "проверь инфраструктуру", "оцени деплой", "setup infrastructure", "review infrastructure" Do NOT use for: choosing or writing application tests without an infrastructure change.
- ▌ Code Reviewing 2 · pavel-molyanovReviews code against the user request, project conventions, cross-file contracts, and applicable quality risks. Use when: "проверь код", "code review", "ревью кода", "review this code", "check code quality"
- ▌ Layout Writing 2 · pavel-molyanov bundleReproduces and adjusts web layouts from Figma, Claude Design exports, screenshots, or an existing project style with high visual fidelity and proportional verification. Use when: "сверстай по Figma", "поправь вёрстку", "подвинь блок", "перенеси из Claude Design", "сделай адаптив", "добавь в том же стиле", "implement layout", "match Figma", "fix responsive layout". Use alongside code-writing for mixed layout and business-logic tasks; use code-writing alone for logic-only work. Blank-slate visual design is outside this skill.
- ▌ Documentation Writing · pavel-molyanov bundleCreates and maintains project documentation in .claude/skills/project-knowledge/: interview, initial Project Knowledge, audit, edit, consistency, and feature finalization. Use when: "заполни документацию проекта", "опиши проект", "создай Project Knowledge", "проведи интервью по проекту", "проверь документацию", "обнови документацию", "аудит документации", "plan a new project", "fill project documentation", "check docs", "audit documentation", "update docs" For reading docs or explaining concepts, read project-knowledge skill directly.
- ▌ Project Initialization · pavel-molyanov bundleInitializes a project from the standard dual-runtime template, preserves existing files, configures Git hooks, and creates or connects a private GitHub repository with main and dev branches. Use when: "инициализируй проект", "создай новый проект", "init project", "initialize project"
- ▌ Layout Reviewing 2 · pavel-molyanovReviews implemented web layouts for source fidelity, responsive behavior, evidence coverage, and project consistency. Use when: "проверь вёрстку", "ревью вёрстки", "проверь адаптив", "review layout", "check visual fidelity" Do NOT use for implementing or changing layouts — use layout-writing instead.
- ▌ Security Auditor 2 · pavel-molyanovAnalyzes changed security boundaries against applicable OWASP risks and project contracts. Use after code-reviewer when authentication, authorization, untrusted input, secrets, sensitive data, database queries, file paths, rendering, or external APIs changed. Use when: "проверь безопасность", "security audit", "найди уязвимости", "check security" Do NOT use for: general code review (use code-reviewer), test quality review (use test-reviewer)
- ▌ User Spec Planning 2 · pavel-molyanov bundleCreates user-spec.md through adaptive interview, codebase research, and three-lane validation. Use when: "сделай юзер спек", "проведи интервью для юзер спека", "создай юзерспек", "user spec", "detailed planning", "хочу продумать фичу", "опиши требования к фиче", "сделай описание фичи", "/new-user-spec"
- ▌ Infrastructure Setup 2 · pavel-molyanov bundleProvides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг", "проверь инфраструктуру", "оцени деплой", "setup infrastructure", "review infrastructure" Do NOT use for: choosing or writing application tests without an infrastructure change.
- ▌ Documentation Writing 2 · pavel-molyanov bundleCreates and maintains project documentation in .claude/skills/project-knowledge/: interview, initial Project Knowledge, audit, edit, consistency, and feature finalization. Use when: "заполни документацию проекта", "опиши проект", "создай Project Knowledge", "проведи интервью по проекту", "проверь документацию", "обнови документацию", "аудит документации", "plan a new project", "fill project documentation", "check docs", "audit documentation", "update docs" For reading docs or explaining concepts, read project-knowledge skill directly.
- ▌ Project Initialization 2 · pavel-molyanov bundleInitializes a project from the standard dual-runtime template, preserves existing files, configures Git hooks, and creates or connects a private GitHub repository with main and dev branches. Use when: "инициализируй проект", "создай новый проект", "init project", "initialize project"
- ▌ Project Knowledge · pavel-molyanov bundleUse when you need information about this project's architecture, tech stack, coding patterns, data model, deployment setup, git workflow, or UX guidelines. Contains comprehensive project documentation including design decisions, technical specifications, and development standards.