From 08a53cac78acefdc8a9dc7a8168a76f05699cda6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9C=D0=B0=D0=BA=D1=81=D0=B8=D0=BC=20=D0=98=D0=B2=D0=B0?= =?UTF-8?q?=D0=BD=D0=BE=D0=B2?= Date: Sat, 14 Nov 2026 20:17:29 +0200 Subject: [PATCH 01/16] feat: publish interview AI skills and per-topic installation UI --- README.md | 25 ++ package.json | 10 +- scripts/check-skills.mjs | 38 ++ skills/ai/SKILL.md | 38 ++ skills/angular/SKILL.md | 38 ++ skills/architecture/SKILL.md | 38 ++ skills/career-teamwork/SKILL.md | 38 ++ skills/catalog.json | 340 ++++++++++++++++ skills/computer-science/SKILL.md | 38 ++ skills/css/SKILL.md | 38 ++ skills/databases-sql/SKILL.md | 38 ++ skills/development-process/SKILL.md | 38 ++ skills/docker/SKILL.md | 38 ++ .../frontend-architecture-patterns/SKILL.md | 38 ++ skills/git/SKILL.md | 38 ++ skills/html/SKILL.md | 38 ++ skills/infrastructure/SKILL.md | 38 ++ skills/integrations/SKILL.md | 38 ++ skills/javascript/SKILL.md | 38 ++ skills/linux/SKILL.md | 38 ++ skills/nodejs/SKILL.md | 38 ++ skills/operating-systems/SKILL.md | 38 ++ skills/qa/SKILL.md | 38 ++ skills/react/SKILL.md | 38 ++ skills/state-management/SKILL.md | 38 ++ skills/system-analysis/SKILL.md | 38 ++ skills/system-design/SKILL.md | 38 ++ skills/typescript/SKILL.md | 38 ++ skills/ui-ux/SKILL.md | 38 ++ skills/web-protocols/SKILL.md | 38 ++ src/components/SkillHero.astro | 57 +++ src/components/SkillInstall.astro | 54 +++ src/data/skills.ts | 8 + src/layouts/Layout.astro | 6 + src/pages/index.astro | 4 + src/pages/skills/index.astro | 56 +++ src/styles/global.css | 1 + src/styles/skills.css | 378 ++++++++++++++++++ 38 files changed, 1962 insertions(+), 3 deletions(-) create mode 100644 scripts/check-skills.mjs create mode 100644 skills/ai/SKILL.md create mode 100644 skills/angular/SKILL.md create mode 100644 skills/architecture/SKILL.md create mode 100644 skills/career-teamwork/SKILL.md create mode 100644 skills/catalog.json create mode 100644 skills/computer-science/SKILL.md create mode 100644 skills/css/SKILL.md create mode 100644 skills/databases-sql/SKILL.md create mode 100644 skills/development-process/SKILL.md create mode 100644 skills/docker/SKILL.md create mode 100644 skills/frontend-architecture-patterns/SKILL.md create mode 100644 skills/git/SKILL.md create mode 100644 skills/html/SKILL.md create mode 100644 skills/infrastructure/SKILL.md create mode 100644 skills/integrations/SKILL.md create mode 100644 skills/javascript/SKILL.md create mode 100644 skills/linux/SKILL.md create mode 100644 skills/nodejs/SKILL.md create mode 100644 skills/operating-systems/SKILL.md create mode 100644 skills/qa/SKILL.md create mode 100644 skills/react/SKILL.md create mode 100644 skills/state-management/SKILL.md create mode 100644 skills/system-analysis/SKILL.md create mode 100644 skills/system-design/SKILL.md create mode 100644 skills/typescript/SKILL.md create mode 100644 skills/ui-ux/SKILL.md create mode 100644 skills/web-protocols/SKILL.md create mode 100644 src/components/SkillHero.astro create mode 100644 src/components/SkillInstall.astro create mode 100644 src/data/skills.ts create mode 100644 src/pages/skills/index.astro create mode 100644 src/styles/skills.css diff --git a/README.md b/README.md index 66528b88..5a0f0709 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,31 @@ Вопросы и практические задания для подготовки разработчиков к собеседованиям: инженерные основы, Frontend, Backend, архитектура, инфраструктура, командная работа и карьера. +## AI Skills для подготовки к собеседованиям + +Кроме справочника, в репозитории есть [каталог AI Skills](https://angular-ru.github.io/interview/skills/). +Каждый раздел вопросов доступен как отдельный скилл для AI-агентов: он проводит пробное интервью по теме, проверяет +ответы, объясняет ошибки и адаптирует сложность под Junior, Middle или Senior. + +Установить все тематические скиллы: + +```bash +npx skills@latest add Angular-RU/angular-ru-interview-questions +``` + +Или только Angular: + +```bash +npx skills@latest add Angular-RU/angular-ru-interview-questions --skill angular +``` + +Скиллы находятся в [`skills/`](skills/). Они дают инструкции для проведения интервью и список тем, +а полные вопросы и ответы остаются в [`src/pages/`](src/pages/). Работа с материалами справочника +требует доступа к сайту или исходникам; без доступа агент использует собственные знания и не должен +утверждать, что проверил первоисточник. + +`npm run skills:check` проверяет соответствие разделов сайта и устанавливаемых скиллов. + ## Основы и инструменты ### Архитектура компьютера [Computer Science logo](public/logos/computer-science.svg) diff --git a/package.json b/package.json index 4522fc1f..23a4e1a8 100644 --- a/package.json +++ b/package.json @@ -7,7 +7,10 @@ "bugs": { "url": "https://github.com/Angular-RU/angular-ru-interview-questions/issues" }, - "workspaces": ["apps/*/*", "apps/*/*/*"], + "workspaces": [ + "apps/*/*", + "apps/*/*/*" + ], "repository": { "type": "git", "url": "git+https://github.com/Angular-RU/angular-ru-interview-questions.git" @@ -18,14 +21,15 @@ "scripts": { "predev": "npm run prebuild", "dev": "astro dev", - "prebuild": "npm run build:public --workspaces --if-present", + "prebuild": "npm run skills:check && npm run build:public --workspaces --if-present", "build": "astro build", "postbuild": "pagefind --site dist --exclude-selectors \".sidebar-navigation, .site-search\"", "preview": "astro preview", "debug": "npm run build && astro preview --host 127.0.0.1 --port 4321", "astro": "astro", "format": "prettier \"!package-lock.json\" . --ignore-path .gitignore --write", - "format:check": "prettier \"!package-lock.json\" . --ignore-path .gitignore --check" + "format:check": "prettier \"!package-lock.json\" . --ignore-path .gitignore --check", + "skills:check": "node scripts/check-skills.mjs" }, "devDependencies": { "@astrojs/markdown-remark": "7.3.5", diff --git a/scripts/check-skills.mjs b/scripts/check-skills.mjs new file mode 100644 index 00000000..63e7478c --- /dev/null +++ b/scripts/check-skills.mjs @@ -0,0 +1,38 @@ +import assert from 'node:assert/strict'; +import {existsSync, readFileSync, readdirSync, statSync} from 'node:fs'; +import {join} from 'node:path'; + +const root = new URL('../', import.meta.url).pathname; +const catalog = JSON.parse(readFileSync(join(root, 'skills/catalog.json'), 'utf8')); +const slugs = new Set(); + +for (const skill of catalog) { + assert.match(skill.slug, /^[a-z0-9]+(?:-[a-z0-9]+)*$/); + assert(!slugs.has(skill.slug), `Duplicate skill: ${skill.slug}`); + slugs.add(skill.slug); + assert(skill.title && skill.description && skill.category); + assert(skill.topics.length >= 3, `Missing topic coverage: ${skill.slug}`); + + const pagePath = join(root, 'src/pages', skill.slug, 'index.md'); + assert(existsSync(pagePath), `Missing topic page: ${skill.slug}`); + assert.match(readFileSync(pagePath, 'utf8'), /kind:\s*questions/); + + const path = join(root, 'skills', skill.slug, 'SKILL.md'); + assert(existsSync(path), `Missing SKILL.md: ${skill.slug}`); + const content = readFileSync(path, 'utf8'); + assert(content.startsWith(`---\nname: ${skill.slug}\ndescription: `), `Invalid frontmatter: ${skill.slug}`); + assert(content.includes(`/interview/${skill.slug}/`), `Missing handbook link: ${skill.slug}`); +} + +const pageSlugs = readdirSync(join(root, 'src/pages')) + .filter((entry) => existsSync(join(root, 'src/pages', entry, 'index.md'))) + .filter((entry) => /kind:\s*questions/.test(readFileSync(join(root, 'src/pages', entry, 'index.md'), 'utf8'))) + .sort(); +assert.deepEqual([...slugs].sort(), pageSlugs, 'Catalog must match all question pages'); + +const skillDirs = readdirSync(join(root, 'skills')) + .filter((entry) => statSync(join(root, 'skills', entry)).isDirectory()) + .sort(); +assert.deepEqual(skillDirs, [...slugs].sort(), 'Skill directories must match catalog'); + +console.log(`Validated ${catalog.length} installable skills and question pages.`); diff --git a/skills/ai/SKILL.md b/skills/ai/SKILL.md new file mode 100644 index 00000000..28723465 --- /dev/null +++ b/skills/ai/SKILL.md @@ -0,0 +1,38 @@ +--- +name: ai +description: "Conduct a AI technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for AI-assisted development, агенты, промптинг, оценка качества AI-кода и безопасное применение моделей." +--- + +# AI — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **AI**. + +## Topics to cover + +- AI-assisted development +- проверка AI-генерируемого кода +- AI-агенты и MCP +- prompt engineering +- тестирование AI-результатов + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [AI interview handbook](https://angular-ru.github.io/interview/ai/) as a **reference when it is accessible**. The editable source is [src/pages/ai/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ai/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по AI." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по AI." diff --git a/skills/angular/SKILL.md b/skills/angular/SKILL.md new file mode 100644 index 00000000..875c06db --- /dev/null +++ b/skills/angular/SKILL.md @@ -0,0 +1,38 @@ +--- +name: angular +description: "Conduct a Angular technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Components, dependency injection, templates, signals, RxJS, routing, forms и SSR." +--- + +# Angular — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Angular**. + +## Topics to cover + +- standalone components и templates +- dependency injection и providers +- signals и change detection +- RxJS и асинхронные потоки +- routing, forms и SSR + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Angular interview handbook](https://angular-ru.github.io/interview/angular/) as a **reference when it is accessible**. The editable source is [src/pages/angular/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/angular/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Angular." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Angular." diff --git a/skills/architecture/SKILL.md b/skills/architecture/SKILL.md new file mode 100644 index 00000000..8fdaa780 --- /dev/null +++ b/skills/architecture/SKILL.md @@ -0,0 +1,38 @@ +--- +name: architecture +description: "Conduct a Распределенные системы technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Микросервисы, надежность, согласованность данных и масштабирование." +--- + +# Распределенные системы — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Распределенные системы**. + +## Topics to cover + +- монолит и микросервисы +- CAP, consistency и availability +- асинхронная коммуникация +- fault tolerance и retries +- масштабирование и наблюдаемость + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Распределенные системы interview handbook](https://angular-ru.github.io/interview/architecture/) as a **reference when it is accessible**. The editable source is [src/pages/architecture/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/architecture/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Распределенные системы." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Распределенные системы." diff --git a/skills/career-teamwork/SKILL.md b/skills/career-teamwork/SKILL.md new file mode 100644 index 00000000..8ec7ed79 --- /dev/null +++ b/skills/career-teamwork/SKILL.md @@ -0,0 +1,38 @@ +--- +name: career-teamwork +description: "Conduct a Карьера в команде technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Soft skills, командное взаимодействие, коммуникация и технические интервью." +--- + +# Карьера в команде — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Карьера в команде**. + +## Topics to cover + +- собеседования и самопрезентация +- коммуникация в команде +- конфликты и обратная связь +- лидерство и наставничество +- карьерный рост + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Карьера в команде interview handbook](https://angular-ru.github.io/interview/career-teamwork/) as a **reference when it is accessible**. The editable source is [src/pages/career-teamwork/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/career-teamwork/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Карьера в команде." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Карьера в команде." diff --git a/skills/catalog.json b/skills/catalog.json new file mode 100644 index 00000000..3c48c6e3 --- /dev/null +++ b/skills/catalog.json @@ -0,0 +1,340 @@ +[ + { + "slug": "ai", + "title": "AI", + "category": "Основы и инструменты", + "description": "AI-assisted development, агенты, промптинг, оценка качества AI-кода и безопасное применение моделей.", + "topics": [ + "AI-assisted development", + "проверка AI-генерируемого кода", + "AI-агенты и MCP", + "prompt engineering", + "тестирование AI-результатов" + ] + }, + { + "slug": "angular", + "title": "Angular", + "category": "Frontend", + "description": "Components, dependency injection, templates, signals, RxJS, routing, forms и SSR.", + "topics": [ + "standalone components и templates", + "dependency injection и providers", + "signals и change detection", + "RxJS и асинхронные потоки", + "routing, forms и SSR" + ] + }, + { + "slug": "architecture", + "title": "Распределенные системы", + "category": "Backend", + "description": "Микросервисы, надежность, согласованность данных и масштабирование.", + "topics": [ + "монолит и микросервисы", + "CAP, consistency и availability", + "асинхронная коммуникация", + "fault tolerance и retries", + "масштабирование и наблюдаемость" + ] + }, + { + "slug": "career-teamwork", + "title": "Карьера в команде", + "category": "Карьера", + "description": "Soft skills, командное взаимодействие, коммуникация и технические интервью.", + "topics": [ + "собеседования и самопрезентация", + "коммуникация в команде", + "конфликты и обратная связь", + "лидерство и наставничество", + "карьерный рост" + ] + }, + { + "slug": "computer-science", + "title": "Архитектура компьютера", + "category": "Основы и инструменты", + "description": "Процессоры, память, машинные инструкции и основы устройства компьютера.", + "topics": [ + "CPU и инструкции", + "иерархия памяти и кэши", + "RAM и адресация", + "параллелизм и выполнение", + "системные ограничения" + ] + }, + { + "slug": "css", + "title": "CSS", + "category": "Frontend", + "description": "Layout, Flexbox, Grid, каскад, адаптивность, rendering и performance.", + "topics": [ + "cascade и specificity", + "Flexbox и Grid", + "responsive layout", + "CSS architecture", + "rendering и performance" + ] + }, + { + "slug": "databases-sql", + "title": "Базы данных", + "category": "Backend", + "description": "SQL, проектирование схем, индексы, транзакции и производительность запросов.", + "topics": [ + "проектирование реляционной схемы", + "JOIN, GROUP BY и подзапросы", + "индексы и планы запросов", + "транзакции и изоляция", + "оптимизация SQL" + ] + }, + { + "slug": "development-process", + "title": "Процессы разработки", + "category": "Карьера", + "description": "Scrum, Kanban, планирование, декомпозиция и взаимодействие с аналитиками.", + "topics": [ + "Agile, Scrum и Kanban", + "оценка и декомпозиция задач", + "планирование и приоритизация", + "определение готовности", + "сотрудничество аналитиков и разработчиков" + ] + }, + { + "slug": "docker", + "title": "Docker", + "category": "Инфраструктура", + "description": "Образы, контейнеры, Dockerfile, Compose и практический запуск приложений.", + "topics": [ + "images vs containers", + "Dockerfile и слои", + "volumes и networks", + "Docker Compose", + "безопасность и оптимизация образов" + ] + }, + { + "slug": "frontend-architecture-patterns", + "title": "Организация кода", + "category": "Frontend", + "description": "Модульные границы, зависимости, архитектурные паттерны и организация frontend-кода.", + "topics": [ + "границы модулей", + "layering и dependency direction", + "архитектурные паттерны", + "feature organization", + "trade-offs и рефакторинг" + ] + }, + { + "slug": "git", + "title": "Git", + "category": "Основы и инструменты", + "description": "История изменений, ветвление, rebase, merge, pull requests и командная работа.", + "topics": [ + "commits и branches", + "merge vs rebase", + "cherry-pick и revert", + "разрешение конфликтов", + "pull request workflow" + ] + }, + { + "slug": "html", + "title": "HTML", + "category": "Frontend", + "description": "Семантика, формы, доступность, metadata, SEO и структура документов.", + "topics": [ + "semantic HTML", + "forms и validation", + "accessibility и ARIA", + "SEO и metadata", + "SVG и media" + ] + }, + { + "slug": "infrastructure", + "title": "DevOps", + "category": "Инфраструктура", + "description": "CI/CD, deployment, delivery pipelines, feature flags и эксплуатация.", + "topics": [ + "CI/CD pipelines", + "build и artifacts", + "deployment и rollback", + "feature flags", + "monitoring и reliability" + ] + }, + { + "slug": "integrations", + "title": "Интеграции", + "category": "Backend", + "description": "REST, SOAP, очереди, брокеры сообщений и интеграционные паттерны.", + "topics": [ + "REST API", + "SOAP и контрактные интеграции", + "message queues", + "синхронные и асинхронные взаимодействия", + "идемпотентность и retries" + ] + }, + { + "slug": "javascript", + "title": "JavaScript", + "category": "Frontend", + "description": "Язык, асинхронность, Event Loop, DOM, fetch и runtime браузера.", + "topics": [ + "types, references и memory", + "closures и prototypes", + "promises и async/await", + "Event Loop", + "DOM, fetch и browser APIs" + ] + }, + { + "slug": "linux", + "title": "Linux / Unix", + "category": "Основы и инструменты", + "description": "Shell, файлы, права, процессы, сеть и рабочее окружение Unix.", + "topics": [ + "shell commands", + "permissions и filesystem", + "processes и signals", + "network diagnostics", + "pipes и shell scripts" + ] + }, + { + "slug": "nodejs", + "title": "Node.js", + "category": "Backend", + "description": "Node runtime, npm, HTTP, networking, tooling и observability.", + "topics": [ + "Node.js runtime", + "event loop и async I/O", + "npm scripts", + "HTTP servers", + "diagnostics и observability" + ] + }, + { + "slug": "operating-systems", + "title": "Операционные системы", + "category": "Основы и инструменты", + "description": "Процессы, потоки, память, файловые системы и сетевые основы.", + "topics": [ + "processes vs threads", + "scheduling", + "virtual memory", + "filesystems", + "I/O и networking" + ] + }, + { + "slug": "qa", + "title": "QA", + "category": "Инфраструктура", + "description": "Стратегия тестирования, unit/integration/e2e, метрики качества и анализ дефектов.", + "topics": [ + "testing pyramid", + "unit, integration и e2e", + "test design и edge cases", + "regression и flaky tests", + "quality metrics" + ] + }, + { + "slug": "react", + "title": "React", + "category": "Frontend", + "description": "Components, hooks, state, rendering, routing, forms и экосистема React.", + "topics": [ + "components и JSX", + "hooks и effects", + "state и rendering", + "forms и data fetching", + "React architecture" + ] + }, + { + "slug": "state-management", + "title": "State Management", + "category": "Frontend", + "description": "Client/server/URL state, кэширование, нормализация и state managers.", + "topics": [ + "local vs shared state", + "server state и caching", + "URL state и forms", + "normalization", + "reactivity и state managers" + ] + }, + { + "slug": "system-analysis", + "title": "Системный анализ", + "category": "Архитектура", + "description": "Требования, user stories, процессы и аналитические артефакты.", + "topics": [ + "functional vs non-functional requirements", + "user stories и acceptance criteria", + "BPMN и UML", + "API contracts", + "traceability и change management" + ] + }, + { + "slug": "system-design", + "title": "Проектирование UI", + "category": "Frontend", + "description": "UI-архитектура, rendering strategies, масштабирование и технические компромиссы.", + "topics": [ + "frontend system design", + "UI data flow", + "SSR, CSR и hydration", + "performance и accessibility", + "trade-offs и ограничения" + ] + }, + { + "slug": "typescript", + "title": "TypeScript", + "category": "Frontend", + "description": "Типизация, generics, utility types, архитектура типов и runtime-контракты.", + "topics": [ + "generics и constraints", + "union и narrowing", + "mapped и conditional types", + "type-safe API design", + "runtime validation" + ] + }, + { + "slug": "ui-ux", + "title": "UI/UX", + "category": "Frontend", + "description": "Usability, accessibility, сценарии пользователей, интерфейсные состояния и продуктовые решения.", + "topics": [ + "UX research", + "interaction design", + "accessibility", + "error и empty states", + "usability и product metrics" + ] + }, + { + "slug": "web-protocols", + "title": "Веб-протоколы и безопасность", + "category": "Основы и инструменты", + "description": "HTTP, браузерная сеть, authentication, authorization и web security.", + "topics": [ + "HTTP request lifecycle", + "HTTP caching и headers", + "cookies и sessions", + "authentication vs authorization", + "XSS, CSRF и CORS" + ] + } +] diff --git a/skills/computer-science/SKILL.md b/skills/computer-science/SKILL.md new file mode 100644 index 00000000..8f7d8fd5 --- /dev/null +++ b/skills/computer-science/SKILL.md @@ -0,0 +1,38 @@ +--- +name: computer-science +description: "Conduct a Архитектура компьютера technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Процессоры, память, машинные инструкции и основы устройства компьютера." +--- + +# Архитектура компьютера — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Архитектура компьютера**. + +## Topics to cover + +- CPU и инструкции +- иерархия памяти и кэши +- RAM и адресация +- параллелизм и выполнение +- системные ограничения + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Архитектура компьютера interview handbook](https://angular-ru.github.io/interview/computer-science/) as a **reference when it is accessible**. The editable source is [src/pages/computer-science/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/computer-science/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Архитектура компьютера." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Архитектура компьютера." diff --git a/skills/css/SKILL.md b/skills/css/SKILL.md new file mode 100644 index 00000000..89bee5fb --- /dev/null +++ b/skills/css/SKILL.md @@ -0,0 +1,38 @@ +--- +name: css +description: "Conduct a CSS technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Layout, Flexbox, Grid, каскад, адаптивность, rendering и performance." +--- + +# CSS — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **CSS**. + +## Topics to cover + +- cascade и specificity +- Flexbox и Grid +- responsive layout +- CSS architecture +- rendering и performance + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [CSS interview handbook](https://angular-ru.github.io/interview/css/) as a **reference when it is accessible**. The editable source is [src/pages/css/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/css/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по CSS." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по CSS." diff --git a/skills/databases-sql/SKILL.md b/skills/databases-sql/SKILL.md new file mode 100644 index 00000000..72f22e1c --- /dev/null +++ b/skills/databases-sql/SKILL.md @@ -0,0 +1,38 @@ +--- +name: databases-sql +description: "Conduct a Базы данных technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for SQL, проектирование схем, индексы, транзакции и производительность запросов." +--- + +# Базы данных — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Базы данных**. + +## Topics to cover + +- проектирование реляционной схемы +- JOIN, GROUP BY и подзапросы +- индексы и планы запросов +- транзакции и изоляция +- оптимизация SQL + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Базы данных interview handbook](https://angular-ru.github.io/interview/databases-sql/) as a **reference when it is accessible**. The editable source is [src/pages/databases-sql/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/databases-sql/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Базы данных." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Базы данных." diff --git a/skills/development-process/SKILL.md b/skills/development-process/SKILL.md new file mode 100644 index 00000000..5eeb2d29 --- /dev/null +++ b/skills/development-process/SKILL.md @@ -0,0 +1,38 @@ +--- +name: development-process +description: "Conduct a Процессы разработки technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Scrum, Kanban, планирование, декомпозиция и взаимодействие с аналитиками." +--- + +# Процессы разработки — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Процессы разработки**. + +## Topics to cover + +- Agile, Scrum и Kanban +- оценка и декомпозиция задач +- планирование и приоритизация +- определение готовности +- сотрудничество аналитиков и разработчиков + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Процессы разработки interview handbook](https://angular-ru.github.io/interview/development-process/) as a **reference when it is accessible**. The editable source is [src/pages/development-process/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/development-process/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Процессы разработки." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Процессы разработки." diff --git a/skills/docker/SKILL.md b/skills/docker/SKILL.md new file mode 100644 index 00000000..cf558acc --- /dev/null +++ b/skills/docker/SKILL.md @@ -0,0 +1,38 @@ +--- +name: docker +description: "Conduct a Docker technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Образы, контейнеры, Dockerfile, Compose и практический запуск приложений." +--- + +# Docker — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Docker**. + +## Topics to cover + +- images vs containers +- Dockerfile и слои +- volumes и networks +- Docker Compose +- безопасность и оптимизация образов + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Docker interview handbook](https://angular-ru.github.io/interview/docker/) as a **reference when it is accessible**. The editable source is [src/pages/docker/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/docker/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Docker." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Docker." diff --git a/skills/frontend-architecture-patterns/SKILL.md b/skills/frontend-architecture-patterns/SKILL.md new file mode 100644 index 00000000..6cfb99f3 --- /dev/null +++ b/skills/frontend-architecture-patterns/SKILL.md @@ -0,0 +1,38 @@ +--- +name: frontend-architecture-patterns +description: "Conduct a Организация кода technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Модульные границы, зависимости, архитектурные паттерны и организация frontend-кода." +--- + +# Организация кода — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Организация кода**. + +## Topics to cover + +- границы модулей +- layering и dependency direction +- архитектурные паттерны +- feature organization +- trade-offs и рефакторинг + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Организация кода interview handbook](https://angular-ru.github.io/interview/frontend-architecture-patterns/) as a **reference when it is accessible**. The editable source is [src/pages/frontend-architecture-patterns/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/frontend-architecture-patterns/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Организация кода." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Организация кода." diff --git a/skills/git/SKILL.md b/skills/git/SKILL.md new file mode 100644 index 00000000..21b4ff04 --- /dev/null +++ b/skills/git/SKILL.md @@ -0,0 +1,38 @@ +--- +name: git +description: "Conduct a Git technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for История изменений, ветвление, rebase, merge, pull requests и командная работа." +--- + +# Git — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Git**. + +## Topics to cover + +- commits и branches +- merge vs rebase +- cherry-pick и revert +- разрешение конфликтов +- pull request workflow + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Git interview handbook](https://angular-ru.github.io/interview/git/) as a **reference when it is accessible**. The editable source is [src/pages/git/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/git/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Git." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Git." diff --git a/skills/html/SKILL.md b/skills/html/SKILL.md new file mode 100644 index 00000000..0b646164 --- /dev/null +++ b/skills/html/SKILL.md @@ -0,0 +1,38 @@ +--- +name: html +description: "Conduct a HTML technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Семантика, формы, доступность, metadata, SEO и структура документов." +--- + +# HTML — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **HTML**. + +## Topics to cover + +- semantic HTML +- forms и validation +- accessibility и ARIA +- SEO и metadata +- SVG и media + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [HTML interview handbook](https://angular-ru.github.io/interview/html/) as a **reference when it is accessible**. The editable source is [src/pages/html/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/html/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по HTML." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по HTML." diff --git a/skills/infrastructure/SKILL.md b/skills/infrastructure/SKILL.md new file mode 100644 index 00000000..47f0aeff --- /dev/null +++ b/skills/infrastructure/SKILL.md @@ -0,0 +1,38 @@ +--- +name: infrastructure +description: "Conduct a DevOps technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for CI/CD, deployment, delivery pipelines, feature flags и эксплуатация." +--- + +# DevOps — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **DevOps**. + +## Topics to cover + +- CI/CD pipelines +- build и artifacts +- deployment и rollback +- feature flags +- monitoring и reliability + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [DevOps interview handbook](https://angular-ru.github.io/interview/infrastructure/) as a **reference when it is accessible**. The editable source is [src/pages/infrastructure/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/infrastructure/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по DevOps." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по DevOps." diff --git a/skills/integrations/SKILL.md b/skills/integrations/SKILL.md new file mode 100644 index 00000000..21334efe --- /dev/null +++ b/skills/integrations/SKILL.md @@ -0,0 +1,38 @@ +--- +name: integrations +description: "Conduct a Интеграции technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for REST, SOAP, очереди, брокеры сообщений и интеграционные паттерны." +--- + +# Интеграции — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Интеграции**. + +## Topics to cover + +- REST API +- SOAP и контрактные интеграции +- message queues +- синхронные и асинхронные взаимодействия +- идемпотентность и retries + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Интеграции interview handbook](https://angular-ru.github.io/interview/integrations/) as a **reference when it is accessible**. The editable source is [src/pages/integrations/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/integrations/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Интеграции." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Интеграции." diff --git a/skills/javascript/SKILL.md b/skills/javascript/SKILL.md new file mode 100644 index 00000000..1766d0ca --- /dev/null +++ b/skills/javascript/SKILL.md @@ -0,0 +1,38 @@ +--- +name: javascript +description: "Conduct a JavaScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Язык, асинхронность, Event Loop, DOM, fetch и runtime браузера." +--- + +# JavaScript — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **JavaScript**. + +## Topics to cover + +- types, references и memory +- closures и prototypes +- promises и async/await +- Event Loop +- DOM, fetch и browser APIs + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [JavaScript interview handbook](https://angular-ru.github.io/interview/javascript/) as a **reference when it is accessible**. The editable source is [src/pages/javascript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/javascript/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по JavaScript." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по JavaScript." diff --git a/skills/linux/SKILL.md b/skills/linux/SKILL.md new file mode 100644 index 00000000..a39308df --- /dev/null +++ b/skills/linux/SKILL.md @@ -0,0 +1,38 @@ +--- +name: linux +description: "Conduct a Linux / Unix technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Shell, файлы, права, процессы, сеть и рабочее окружение Unix." +--- + +# Linux / Unix — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Linux / Unix**. + +## Topics to cover + +- shell commands +- permissions и filesystem +- processes и signals +- network diagnostics +- pipes и shell scripts + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Linux / Unix interview handbook](https://angular-ru.github.io/interview/linux/) as a **reference when it is accessible**. The editable source is [src/pages/linux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/linux/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Linux / Unix." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Linux / Unix." diff --git a/skills/nodejs/SKILL.md b/skills/nodejs/SKILL.md new file mode 100644 index 00000000..b44c5f1a --- /dev/null +++ b/skills/nodejs/SKILL.md @@ -0,0 +1,38 @@ +--- +name: nodejs +description: "Conduct a Node.js technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Node runtime, npm, HTTP, networking, tooling и observability." +--- + +# Node.js — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Node.js**. + +## Topics to cover + +- Node.js runtime +- event loop и async I/O +- npm scripts +- HTTP servers +- diagnostics и observability + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Node.js interview handbook](https://angular-ru.github.io/interview/nodejs/) as a **reference when it is accessible**. The editable source is [src/pages/nodejs/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/nodejs/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Node.js." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Node.js." diff --git a/skills/operating-systems/SKILL.md b/skills/operating-systems/SKILL.md new file mode 100644 index 00000000..5468cf4a --- /dev/null +++ b/skills/operating-systems/SKILL.md @@ -0,0 +1,38 @@ +--- +name: operating-systems +description: "Conduct a Операционные системы technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Процессы, потоки, память, файловые системы и сетевые основы." +--- + +# Операционные системы — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Операционные системы**. + +## Topics to cover + +- processes vs threads +- scheduling +- virtual memory +- filesystems +- I/O и networking + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Операционные системы interview handbook](https://angular-ru.github.io/interview/operating-systems/) as a **reference when it is accessible**. The editable source is [src/pages/operating-systems/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/operating-systems/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Операционные системы." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Операционные системы." diff --git a/skills/qa/SKILL.md b/skills/qa/SKILL.md new file mode 100644 index 00000000..f342fa35 --- /dev/null +++ b/skills/qa/SKILL.md @@ -0,0 +1,38 @@ +--- +name: qa +description: "Conduct a QA technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Стратегия тестирования, unit/integration/e2e, метрики качества и анализ дефектов." +--- + +# QA — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **QA**. + +## Topics to cover + +- testing pyramid +- unit, integration и e2e +- test design и edge cases +- regression и flaky tests +- quality metrics + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [QA interview handbook](https://angular-ru.github.io/interview/qa/) as a **reference when it is accessible**. The editable source is [src/pages/qa/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/qa/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по QA." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по QA." diff --git a/skills/react/SKILL.md b/skills/react/SKILL.md new file mode 100644 index 00000000..c741e8ba --- /dev/null +++ b/skills/react/SKILL.md @@ -0,0 +1,38 @@ +--- +name: react +description: "Conduct a React technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Components, hooks, state, rendering, routing, forms и экосистема React." +--- + +# React — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **React**. + +## Topics to cover + +- components и JSX +- hooks и effects +- state и rendering +- forms и data fetching +- React architecture + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [React interview handbook](https://angular-ru.github.io/interview/react/) as a **reference when it is accessible**. The editable source is [src/pages/react/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/react/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по React." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по React." diff --git a/skills/state-management/SKILL.md b/skills/state-management/SKILL.md new file mode 100644 index 00000000..d811bc88 --- /dev/null +++ b/skills/state-management/SKILL.md @@ -0,0 +1,38 @@ +--- +name: state-management +description: "Conduct a State Management technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Client/server/URL state, кэширование, нормализация и state managers." +--- + +# State Management — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **State Management**. + +## Topics to cover + +- local vs shared state +- server state и caching +- URL state и forms +- normalization +- reactivity и state managers + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [State Management interview handbook](https://angular-ru.github.io/interview/state-management/) as a **reference when it is accessible**. The editable source is [src/pages/state-management/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/state-management/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по State Management." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по State Management." diff --git a/skills/system-analysis/SKILL.md b/skills/system-analysis/SKILL.md new file mode 100644 index 00000000..0f27ad60 --- /dev/null +++ b/skills/system-analysis/SKILL.md @@ -0,0 +1,38 @@ +--- +name: system-analysis +description: "Conduct a Системный анализ technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Требования, user stories, процессы и аналитические артефакты." +--- + +# Системный анализ — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Системный анализ**. + +## Topics to cover + +- functional vs non-functional requirements +- user stories и acceptance criteria +- BPMN и UML +- API contracts +- traceability и change management + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Системный анализ interview handbook](https://angular-ru.github.io/interview/system-analysis/) as a **reference when it is accessible**. The editable source is [src/pages/system-analysis/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-analysis/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Системный анализ." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Системный анализ." diff --git a/skills/system-design/SKILL.md b/skills/system-design/SKILL.md new file mode 100644 index 00000000..5a880db8 --- /dev/null +++ b/skills/system-design/SKILL.md @@ -0,0 +1,38 @@ +--- +name: system-design +description: "Conduct a Проектирование UI technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for UI-архитектура, rendering strategies, масштабирование и технические компромиссы." +--- + +# Проектирование UI — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Проектирование UI**. + +## Topics to cover + +- frontend system design +- UI data flow +- SSR, CSR и hydration +- performance и accessibility +- trade-offs и ограничения + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Проектирование UI interview handbook](https://angular-ru.github.io/interview/system-design/) as a **reference when it is accessible**. The editable source is [src/pages/system-design/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-design/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Проектирование UI." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Проектирование UI." diff --git a/skills/typescript/SKILL.md b/skills/typescript/SKILL.md new file mode 100644 index 00000000..843e410c --- /dev/null +++ b/skills/typescript/SKILL.md @@ -0,0 +1,38 @@ +--- +name: typescript +description: "Conduct a TypeScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Типизация, generics, utility types, архитектура типов и runtime-контракты." +--- + +# TypeScript — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **TypeScript**. + +## Topics to cover + +- generics и constraints +- union и narrowing +- mapped и conditional types +- type-safe API design +- runtime validation + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [TypeScript interview handbook](https://angular-ru.github.io/interview/typescript/) as a **reference when it is accessible**. The editable source is [src/pages/typescript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/typescript/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по TypeScript." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по TypeScript." diff --git a/skills/ui-ux/SKILL.md b/skills/ui-ux/SKILL.md new file mode 100644 index 00000000..266c1b17 --- /dev/null +++ b/skills/ui-ux/SKILL.md @@ -0,0 +1,38 @@ +--- +name: ui-ux +description: "Conduct a UI/UX technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Usability, accessibility, сценарии пользователей, интерфейсные состояния и продуктовые решения." +--- + +# UI/UX — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **UI/UX**. + +## Topics to cover + +- UX research +- interaction design +- accessibility +- error и empty states +- usability и product metrics + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [UI/UX interview handbook](https://angular-ru.github.io/interview/ui-ux/) as a **reference when it is accessible**. The editable source is [src/pages/ui-ux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ui-ux/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по UI/UX." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по UI/UX." diff --git a/skills/web-protocols/SKILL.md b/skills/web-protocols/SKILL.md new file mode 100644 index 00000000..d2cb52b2 --- /dev/null +++ b/skills/web-protocols/SKILL.md @@ -0,0 +1,38 @@ +--- +name: web-protocols +description: "Conduct a Веб-протоколы и безопасность technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for HTTP, браузерная сеть, authentication, authorization и web security." +--- + +# Веб-протоколы и безопасность — interview practice + +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Веб-протоколы и безопасность**. + +## Topics to cover + +- HTTP request lifecycle +- HTTP caching и headers +- cookies и sessions +- authentication vs authorization +- XSS, CSRF и CORS + +## Interview workflow + +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. + +## Grounding and boundaries + +- Use the [Веб-протоколы и безопасность interview handbook](https://angular-ru.github.io/interview/web-protocols/) as a **reference when it is accessible**. The editable source is [src/pages/web-protocols/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/web-protocols/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. + +## Example requests + +- "Проведи со мной Middle-собеседование по Веб-протоколы и безопасность." +- "Проверь мой ответ и скажи, что я упустил." +- "Дай сложный практический вопрос для Senior по Веб-протоколы и безопасность." diff --git a/src/components/SkillHero.astro b/src/components/SkillHero.astro new file mode 100644 index 00000000..95b2b437 --- /dev/null +++ b/src/components/SkillHero.astro @@ -0,0 +1,57 @@ +--- +import type {Skill} from '../data/skills'; +import {installCommand} from '../data/skills'; +import SkillInstall from './SkillInstall.astro'; + +interface Props { + readonly skill: Skill; +} + +const {skill} = Astro.props; +const base = import.meta.env.BASE_URL.replace(/\/$/, ''); +--- + +
+
+

/{skill.slug} · AI Skill

+

{skill.title}

+

{skill.description}

+ + + + +
+ + +
diff --git a/src/components/SkillInstall.astro b/src/components/SkillInstall.astro new file mode 100644 index 00000000..6d8e9995 --- /dev/null +++ b/src/components/SkillInstall.astro @@ -0,0 +1,54 @@ +--- +interface Props { + readonly command: string; +} + +const {command} = Astro.props; +--- + +
+ + {command} + +
+ + diff --git a/src/data/skills.ts b/src/data/skills.ts new file mode 100644 index 00000000..836624d0 --- /dev/null +++ b/src/data/skills.ts @@ -0,0 +1,8 @@ +import catalog from '../../skills/catalog.json'; + +export const skills = catalog; +export type Skill = (typeof skills)[number]; + +export const installAllCommand = 'npx skills@latest add Angular-RU/angular-ru-interview-questions'; + +export const installCommand = (slug: string): string => `${installAllCommand} --skill ${slug}`; diff --git a/src/layouts/Layout.astro b/src/layouts/Layout.astro index 3e265626..853b6df3 100644 --- a/src/layouts/Layout.astro +++ b/src/layouts/Layout.astro @@ -3,6 +3,8 @@ import {ClientRouter} from 'astro:transitions'; import SidebarNavigation from '../components/SidebarNavigation.astro'; import SiteSearch from '../components/SiteSearch.astro'; +import SkillHero from '../components/SkillHero.astro'; +import {skills} from '../data/skills'; import '../styles/global.css'; interface MarkdownHeading { @@ -33,6 +35,8 @@ const basePath = import.meta.env.BASE_URL.replace(/\/$/, ''); const currentPath = Astro.url.pathname.replace(/\/$/, ''); const homeHref = `${basePath}/`; const isHomePage = currentPath === basePath; +const skillSlug = currentPath.slice(basePath.length).replace(/^\/+|\/+$/g, ''); +const currentSkill = skills.find(({slug}) => slug === skillSlug); const showHomeLink = !isHomePage; const canonicalUrl = new URL(Astro.url.pathname, Astro.site ?? Astro.url.origin); @@ -123,6 +127,8 @@ const searchEnabled = import.meta.env.PROD; title={title} /> + {currentSkill && } + diff --git a/src/pages/index.astro b/src/pages/index.astro index 8e08a0cf..7a9d077b 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -187,6 +187,10 @@ const exampleCards = examples.slice().sort((a, b) => a.order - b.order); )) } + AI Skills diff --git a/src/pages/skills/index.astro b/src/pages/skills/index.astro new file mode 100644 index 00000000..3e05a733 --- /dev/null +++ b/src/pages/skills/index.astro @@ -0,0 +1,56 @@ +--- +import Layout from '../../layouts/Layout.astro'; +import SkillInstall from '../../components/SkillInstall.astro'; +import {installAllCommand, skills} from '../../data/skills'; + +const base = import.meta.env.BASE_URL.replace(/\/$/, ''); +const groups = [...new Set(skills.map(({category}) => category))]; +--- + + +
+
+

/skills

+

AI Skills для технических интервью

+

+ Превратите справочник вопросов в персонального AI-интервьюера. Скиллы задают вопросы, + разбирают ответы и помогают подготовиться к техническому собеседованию. +

+
+ Установить все скиллы + +
+
+ +
+ {skills.length} скиллов + Выберите тему и установите только то, что нужно +
+ + { + groups.map((group) => ( +
+

{group}

+
+ {skills + .filter(({category}) => category === group) + .map((skill) => ( + + + {skill.title} + {skill.description} + + /{skill.slug} + + + + ))} +
+
+ )) + } +
+
diff --git a/src/styles/global.css b/src/styles/global.css index 2330fc09..c519c640 100644 --- a/src/styles/global.css +++ b/src/styles/global.css @@ -8,3 +8,4 @@ @import './markdown.css'; @import './content-figures.css'; @import './markdown-details.css'; +@import './skills.css'; diff --git a/src/styles/skills.css b/src/styles/skills.css new file mode 100644 index 00000000..99b575d5 --- /dev/null +++ b/src/styles/skills.css @@ -0,0 +1,378 @@ +.skill-install { + display: flex; + min-height: 62px; + align-items: center; + gap: 12px; + padding: 10px 12px 10px 18px; + border: 1px solid #d9dde4; + border-radius: 12px; + background: #f5f6f8; +} + +.skill-install__prompt { + color: #808893; + font-family: monospace; +} + +.content .skill-install code { + flex: 1; + min-width: 0; + padding: 0; + overflow-wrap: anywhere; + color: #22262e; + background: transparent; + font-size: 0.9rem; + line-height: 1.4; +} + +.skill-install__copy { + flex-shrink: 0; + padding: 10px 12px; + border: 1px solid #d5d9df; + border-radius: 9px; + color: #343b45; + background: #fff; + font: inherit; + font-size: 0.82rem; + font-weight: 700; + cursor: pointer; +} + +.skill-install__copy:hover { + border-color: #9aaec8; + background: #edf2f9; +} + +.skill-install__copy:focus-visible, +.skill-hero a:focus-visible, +.skills-catalog a:focus-visible { + outline: 3px solid #8bb8ff; + outline-offset: 3px; +} + +.skill-hero { + display: grid; + grid-template-columns: minmax(0, 1.13fr) minmax(0, 0.87fr); + align-items: center; + gap: clamp(28px, 4vw, 56px); + padding: 22px 0 44px; + border-bottom: 1px solid var(--border); +} + +.content .skill-hero__eyebrow { + margin: 0 0 24px; + color: #575f6c; + font-family: monospace; + font-size: 0.9rem; +} + +.skill-hero__eyebrow span { + color: #838b96; +} + +.content .skill-hero h1 { + margin: 0; + color: #101216; + font-size: clamp(2.8rem, 5vw, 4.6rem); + line-height: 1; + letter-spacing: -0.06em; +} + +.content .skill-hero__lead { + margin: 26px 0 28px; + color: #49515d; + font-size: clamp(1.07rem, 1.6vw, 1.3rem); + line-height: 1.65; +} + +.skill-hero__links { + display: flex; + flex-wrap: wrap; + align-items: center; + gap: 10px; + margin-top: 18px; + color: #7f8791; + font-size: 0.88rem; +} + +.content .skill-hero__links a { + color: #4a5568; + font-weight: 500; + text-decoration: none; +} + +.skill-hero__visual { + min-width: 0; + padding: 10px; + border: 1px solid #dfe3e7; + border-radius: 23px; + background: #fff; + box-shadow: 0 9px 24px rgb(12 24 44 / 6%); +} + +.skill-hero__window { + min-height: 310px; + overflow: hidden; + border: 1px solid #161d25; + border-radius: 15px; + color: #dbeafe; + background: + repeating-linear-gradient(0deg, transparent 0 3px, rgb(255 255 255 / 2%) 4px 5px), + radial-gradient(ellipse at 53% 46%, #1d3550, transparent 65%), + #0c1119; +} + +.skill-hero__window-top { + display: flex; + height: 48px; + align-items: center; + gap: 6px; + padding: 0 18px; + border-bottom: 1px solid rgb(255 255 255 / 8%); +} + +.skill-hero__dot { + width: 7px; + height: 7px; + border-radius: 100%; + background: #52657a; +} + +.skill-hero__window-label { + margin-left: auto; + color: #7c8da0; + font-family: monospace; + font-size: 0.65rem; + letter-spacing: 0.13em; +} + +.skill-hero__terminal { + padding: 28px 30px 24px; + font-family: monospace; +} + +.skill-hero__terminal-label { + color: #6db9ee; + font-size: 0.68rem; + letter-spacing: 0.18em; +} + +.skill-hero__terminal-title { + margin: 12px 0 26px; + overflow-wrap: anywhere; + color: #fff; + font-size: clamp(1.5rem, 2.8vw, 2.5rem); + letter-spacing: -0.04em; + text-shadow: 0 0 24px rgb(80 183 255 / 45%); +} + +.skill-hero__terminal-line { + margin-top: 13px; + color: #bbc7d8; + font-size: 0.78rem; +} + +.skill-hero__terminal-line span { + margin-right: 12px; + color: #5f9dbb; +} + +.skill-hero__cursor { + display: inline-block; + width: 7px; + height: 13px; + margin-left: 3px; + background: #65cfff; + vertical-align: -2px; + animation: skill-cursor-pulse 1.4s steps(2) infinite; +} + +.skill-hero__terminal-footer { + margin-top: 26px; + color: #7d8ea2; + font-size: 0.68rem; +} + +.skill-hero__terminal-footer span { + padding: 0 7px; + color: #5f7187; +} + +@keyframes skill-cursor-pulse { + 50% { opacity: 0.1; } +} + +.skills-catalog__intro { + padding: 20px 0 36px; +} + +.content .skills-catalog__eyebrow { + margin: 0 0 22px; + color: #6b7280; + font-family: monospace; + font-size: 0.95rem; +} + +.content .skills-catalog h1 { + max-width: 850px; + margin: 0; + font-size: clamp(2.8rem, 6vw, 5.5rem); + line-height: 1.03; + letter-spacing: -0.06em; +} + +.content .skills-catalog__lead { + max-width: 790px; + margin: 26px 0 32px; + color: #4b5563; + font-size: 1.15rem; +} + +.skills-catalog__install { + max-width: 780px; +} + +.skills-catalog__install > span { + display: inline-block; + margin-bottom: 12px; + color: #555f6d; + font-size: 0.84rem; + font-weight: 700; +} + +.skills-catalog__summary { + display: flex; + flex-wrap: wrap; + gap: 10px 16px; + align-items: baseline; + padding: 20px 0; + border-top: 1px solid var(--border); + color: #637083; + font-size: 0.94rem; +} + +.skills-catalog__summary strong { + color: #151a20; +} + +.content .skills-catalog__section h2 { + margin: 36px 0 18px; + padding: 0; + border: 0; + font-size: 1.5rem; + letter-spacing: -0.03em; +} + +.skills-catalog__grid { + display: grid; + grid-template-columns: repeat(auto-fit, minmax(min(100%, 250px), 1fr)); + gap: 14px; +} + +.content .skills-catalog__card { + display: flex; + min-height: 224px; + flex-direction: column; + padding: 24px; + border: 1px solid #dde3eb; + border-radius: 17px; + color: #141a25; + background: #fff; + box-shadow: 0 9px 24px rgb(15 23 42 / 4%); + font-weight: 400; + text-decoration: none; + transition: transform 160ms ease, border-color 160ms ease, box-shadow 160ms ease; +} + +.skills-catalog__card:hover { + transform: translateY(-3px); + border-color: #8cb5e7; + box-shadow: 0 14px 30px rgb(15 23 42 / 10%); +} + +.skills-catalog__card-icon { + display: grid; + width: 53px; + height: 53px; + place-items: center; + margin-bottom: 20px; + border-radius: 12px; + color: #76cdf5; + background: #0b1826; + font-family: monospace; + font-size: 0.9rem; +} + +.skills-catalog__card-title { + color: #101827; + font-size: 1.25rem; + font-weight: 750; + letter-spacing: -0.025em; +} + +.skills-catalog__card-description { + margin-top: 9px; + color: #667285; + font-size: 0.9rem; + line-height: 1.5; +} + +.skills-catalog__card-footer { + display: flex; + justify-content: space-between; + align-items: center; + gap: 12px; + margin-top: auto; + padding-top: 22px; + color: #426ea1; +} + +.content .skills-catalog__card-footer code { + padding: 0; + overflow-wrap: anywhere; + background: none; + font-size: 0.76rem; +} + +@media (max-width: 900px) { + .skill-hero { + grid-template-columns: 1fr; + } + + .skill-hero__window { + min-height: 270px; + } +} + +@media (max-width: 600px) { + .skill-install { + align-items: flex-start; + flex-wrap: wrap; + } + + .skill-install__copy { + margin-left: auto; + } + + .skill-hero__terminal { + padding: 24px; + } + + .skills-catalog__grid { + grid-template-columns: 1fr; + } +} + +@media (prefers-reduced-motion: reduce) { + .skill-hero__cursor { + animation: none; + } + + .skills-catalog__card { + transition: none; + } + + .skills-catalog__card:hover { + transform: none; + } +} From 6f9d4a833c070bcec617f46f1d47b603188baa17 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9C=D0=B0=D0=BA=D1=81=D0=B8=D0=BC=20=D0=98=D0=B2=D0=B0?= =?UTF-8?q?=D0=BD=D0=BE=D0=B2?= Date: Sat, 14 Nov 2026 20:20:06 +0200 Subject: [PATCH 02/16] ci: temporarily extract exact Prettier formatting --- .github/workflows/build.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index fc415e9c..670c0482 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -30,6 +30,16 @@ jobs: - name: Install dependencies run: npm ci + - name: Generate formatted source (temporary) + run: | + npm run format + node --input-type=module -e ' + import {readFileSync} from "node:fs"; + import {execFileSync} from "node:child_process"; + const paths = execFileSync("git", ["diff", "--name-only", "-z"]).toString().split("\\0").filter(Boolean); + for (const path of paths) console.log("FORMATTED_FILE=" + JSON.stringify({path, content: readFileSync(path, "utf8")})); + ' + - name: Check formatting run: npm run format:check From 8f0b238b095d3e46340c5c77b60b95cbdd008b90 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9C=D0=B0=D0=BA=D1=81=D0=B8=D0=BC=20=D0=98=D0=B2=D0=B0?= =?UTF-8?q?=D0=BD=D0=BE=D0=B2?= Date: Sat, 14 Nov 2026 20:20:28 +0200 Subject: [PATCH 03/16] ci: correctly separate formatted paths --- .github/workflows/build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 670c0482..2125e6e0 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -36,7 +36,7 @@ jobs: node --input-type=module -e ' import {readFileSync} from "node:fs"; import {execFileSync} from "node:child_process"; - const paths = execFileSync("git", ["diff", "--name-only", "-z"]).toString().split("\\0").filter(Boolean); + const paths = execFileSync("git", ["diff", "--name-only", "-z"]).toString().split(String.fromCharCode(0)).filter(Boolean); for (const path of paths) console.log("FORMATTED_FILE=" + JSON.stringify({path, content: readFileSync(path, "utf8")})); ' From 6e67e73f677a1d426fd2a9c7e528df5d71424cb3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9C=D0=B0=D0=BA=D1=81=D0=B8=D0=BC=20=D0=98=D0=B2=D0=B0?= =?UTF-8?q?=D0=BD=D0=BE=D0=B2?= Date: Sat, 14 Nov 2026 20:23:03 +0200 Subject: [PATCH 04/16] style: apply project Prettier rules and accept multiline skill metadata --- .github/workflows/build.yml | 10 ------ README.md | 13 ++++--- package.json | 5 +-- scripts/check-skills.mjs | 2 +- skills/ai/SKILL.md | 35 +++++++++++++------ skills/angular/SKILL.md | 35 +++++++++++++------ skills/architecture/SKILL.md | 35 +++++++++++++------ skills/career-teamwork/SKILL.md | 35 +++++++++++++------ skills/catalog.json | 16 ++------- skills/computer-science/SKILL.md | 35 +++++++++++++------ skills/css/SKILL.md | 35 +++++++++++++------ skills/databases-sql/SKILL.md | 35 +++++++++++++------ skills/development-process/SKILL.md | 35 +++++++++++++------ skills/docker/SKILL.md | 35 +++++++++++++------ .../frontend-architecture-patterns/SKILL.md | 35 +++++++++++++------ skills/git/SKILL.md | 35 +++++++++++++------ skills/html/SKILL.md | 35 +++++++++++++------ skills/infrastructure/SKILL.md | 35 +++++++++++++------ skills/integrations/SKILL.md | 35 +++++++++++++------ skills/javascript/SKILL.md | 35 +++++++++++++------ skills/linux/SKILL.md | 35 +++++++++++++------ skills/nodejs/SKILL.md | 35 +++++++++++++------ skills/operating-systems/SKILL.md | 35 +++++++++++++------ skills/qa/SKILL.md | 35 +++++++++++++------ skills/react/SKILL.md | 35 +++++++++++++------ skills/state-management/SKILL.md | 35 +++++++++++++------ skills/system-analysis/SKILL.md | 35 +++++++++++++------ skills/system-design/SKILL.md | 35 +++++++++++++------ skills/typescript/SKILL.md | 35 +++++++++++++------ skills/ui-ux/SKILL.md | 35 +++++++++++++------ skills/web-protocols/SKILL.md | 35 +++++++++++++------ src/components/SkillHero.astro | 8 +++-- src/components/SkillInstall.astro | 4 ++- src/data/skills.ts | 6 ++-- src/pages/index.astro | 4 ++- src/pages/skills/index.astro | 21 ++++++++--- src/styles/skills.css | 12 ++++--- 37 files changed, 674 insertions(+), 337 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 2125e6e0..fc415e9c 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -30,16 +30,6 @@ jobs: - name: Install dependencies run: npm ci - - name: Generate formatted source (temporary) - run: | - npm run format - node --input-type=module -e ' - import {readFileSync} from "node:fs"; - import {execFileSync} from "node:child_process"; - const paths = execFileSync("git", ["diff", "--name-only", "-z"]).toString().split(String.fromCharCode(0)).filter(Boolean); - for (const path of paths) console.log("FORMATTED_FILE=" + JSON.stringify({path, content: readFileSync(path, "utf8")})); - ' - - name: Check formatting run: npm run format:check diff --git a/README.md b/README.md index 5a0f0709..72a6e7a9 100644 --- a/README.md +++ b/README.md @@ -5,9 +5,9 @@ ## AI Skills для подготовки к собеседованиям -Кроме справочника, в репозитории есть [каталог AI Skills](https://angular-ru.github.io/interview/skills/). -Каждый раздел вопросов доступен как отдельный скилл для AI-агентов: он проводит пробное интервью по теме, проверяет -ответы, объясняет ошибки и адаптирует сложность под Junior, Middle или Senior. +Кроме справочника, в репозитории есть [каталог AI Skills](https://angular-ru.github.io/interview/skills/). Каждый раздел +вопросов доступен как отдельный скилл для AI-агентов: он проводит пробное интервью по теме, проверяет ответы, объясняет +ошибки и адаптирует сложность под Junior, Middle или Senior. Установить все тематические скиллы: @@ -21,10 +21,9 @@ npx skills@latest add Angular-RU/angular-ru-interview-questions npx skills@latest add Angular-RU/angular-ru-interview-questions --skill angular ``` -Скиллы находятся в [`skills/`](skills/). Они дают инструкции для проведения интервью и список тем, -а полные вопросы и ответы остаются в [`src/pages/`](src/pages/). Работа с материалами справочника -требует доступа к сайту или исходникам; без доступа агент использует собственные знания и не должен -утверждать, что проверил первоисточник. +Скиллы находятся в [`skills/`](skills/). Они дают инструкции для проведения интервью и список тем, а полные вопросы и +ответы остаются в [`src/pages/`](src/pages/). Работа с материалами справочника требует доступа к сайту или исходникам; +без доступа агент использует собственные знания и не должен утверждать, что проверил первоисточник. `npm run skills:check` проверяет соответствие разделов сайта и устанавливаемых скиллов. diff --git a/package.json b/package.json index 23a4e1a8..51d7cdc3 100644 --- a/package.json +++ b/package.json @@ -7,10 +7,7 @@ "bugs": { "url": "https://github.com/Angular-RU/angular-ru-interview-questions/issues" }, - "workspaces": [ - "apps/*/*", - "apps/*/*/*" - ], + "workspaces": ["apps/*/*", "apps/*/*/*"], "repository": { "type": "git", "url": "git+https://github.com/Angular-RU/angular-ru-interview-questions.git" diff --git a/scripts/check-skills.mjs b/scripts/check-skills.mjs index 63e7478c..0eb5d12e 100644 --- a/scripts/check-skills.mjs +++ b/scripts/check-skills.mjs @@ -20,7 +20,7 @@ for (const skill of catalog) { const path = join(root, 'skills', skill.slug, 'SKILL.md'); assert(existsSync(path), `Missing SKILL.md: ${skill.slug}`); const content = readFileSync(path, 'utf8'); - assert(content.startsWith(`---\nname: ${skill.slug}\ndescription: `), `Invalid frontmatter: ${skill.slug}`); + assert(content.startsWith(`---\nname: ${skill.slug}\ndescription:`), `Invalid frontmatter: ${skill.slug}`); assert(content.includes(`/interview/${skill.slug}/`), `Missing handbook link: ${skill.slug}`); } diff --git a/skills/ai/SKILL.md b/skills/ai/SKILL.md index 28723465..d3c4cffa 100644 --- a/skills/ai/SKILL.md +++ b/skills/ai/SKILL.md @@ -1,11 +1,14 @@ --- name: ai -description: "Conduct a AI technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for AI-assisted development, агенты, промптинг, оценка качества AI-кода и безопасное применение моделей." +description: + 'Conduct a AI technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for + AI-assisted development, агенты, промптинг, оценка качества AI-кода и безопасное применение моделей.' --- # AI — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **AI**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **AI**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [AI interview handbook](https://angular-ru.github.io/interview/ai/) as a **reference when it is accessible**. The editable source is [src/pages/ai/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ai/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [AI interview handbook](https://angular-ru.github.io/interview/ai/) as a **reference when it is accessible**. + The editable source is + [src/pages/ai/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ai/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/angular/SKILL.md b/skills/angular/SKILL.md index 875c06db..13878222 100644 --- a/skills/angular/SKILL.md +++ b/skills/angular/SKILL.md @@ -1,11 +1,14 @@ --- name: angular -description: "Conduct a Angular technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Components, dependency injection, templates, signals, RxJS, routing, forms и SSR." +description: + 'Conduct a Angular technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for Components, dependency injection, templates, signals, RxJS, routing, forms и SSR.' --- # Angular — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Angular**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Angular**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Angular interview handbook](https://angular-ru.github.io/interview/angular/) as a **reference when it is accessible**. The editable source is [src/pages/angular/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/angular/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Angular interview handbook](https://angular-ru.github.io/interview/angular/) as a **reference when it is + accessible**. The editable source is + [src/pages/angular/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/angular/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/architecture/SKILL.md b/skills/architecture/SKILL.md index 8fdaa780..bd718382 100644 --- a/skills/architecture/SKILL.md +++ b/skills/architecture/SKILL.md @@ -1,11 +1,14 @@ --- name: architecture -description: "Conduct a Распределенные системы technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Микросервисы, надежность, согласованность данных и масштабирование." +description: + 'Conduct a Распределенные системы technical interview, ask one question at a time, evaluate candidate answers, and + explain gaps. Use for Микросервисы, надежность, согласованность данных и масштабирование.' --- # Распределенные системы — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Распределенные системы**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Распределенные системы**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Распределенные системы interview handbook](https://angular-ru.github.io/interview/architecture/) as a **reference when it is accessible**. The editable source is [src/pages/architecture/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/architecture/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Распределенные системы interview handbook](https://angular-ru.github.io/interview/architecture/) as a + **reference when it is accessible**. The editable source is + [src/pages/architecture/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/architecture/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/career-teamwork/SKILL.md b/skills/career-teamwork/SKILL.md index 8ec7ed79..19b1dadf 100644 --- a/skills/career-teamwork/SKILL.md +++ b/skills/career-teamwork/SKILL.md @@ -1,11 +1,14 @@ --- name: career-teamwork -description: "Conduct a Карьера в команде technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Soft skills, командное взаимодействие, коммуникация и технические интервью." +description: + 'Conduct a Карьера в команде technical interview, ask one question at a time, evaluate candidate answers, and explain + gaps. Use for Soft skills, командное взаимодействие, коммуникация и технические интервью.' --- # Карьера в команде — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Карьера в команде**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Карьера в команде**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Карьера в команде interview handbook](https://angular-ru.github.io/interview/career-teamwork/) as a **reference when it is accessible**. The editable source is [src/pages/career-teamwork/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/career-teamwork/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Карьера в команде interview handbook](https://angular-ru.github.io/interview/career-teamwork/) as a + **reference when it is accessible**. The editable source is + [src/pages/career-teamwork/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/career-teamwork/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/catalog.json b/skills/catalog.json index 3c48c6e3..7ae2a11f 100644 --- a/skills/catalog.json +++ b/skills/catalog.json @@ -147,13 +147,7 @@ "title": "HTML", "category": "Frontend", "description": "Семантика, формы, доступность, metadata, SEO и структура документов.", - "topics": [ - "semantic HTML", - "forms и validation", - "accessibility и ARIA", - "SEO и metadata", - "SVG и media" - ] + "topics": ["semantic HTML", "forms и validation", "accessibility и ARIA", "SEO и metadata", "SVG и media"] }, { "slug": "infrastructure", @@ -225,13 +219,7 @@ "title": "Операционные системы", "category": "Основы и инструменты", "description": "Процессы, потоки, память, файловые системы и сетевые основы.", - "topics": [ - "processes vs threads", - "scheduling", - "virtual memory", - "filesystems", - "I/O и networking" - ] + "topics": ["processes vs threads", "scheduling", "virtual memory", "filesystems", "I/O и networking"] }, { "slug": "qa", diff --git a/skills/computer-science/SKILL.md b/skills/computer-science/SKILL.md index 8f7d8fd5..65d8b43d 100644 --- a/skills/computer-science/SKILL.md +++ b/skills/computer-science/SKILL.md @@ -1,11 +1,14 @@ --- name: computer-science -description: "Conduct a Архитектура компьютера technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Процессоры, память, машинные инструкции и основы устройства компьютера." +description: + 'Conduct a Архитектура компьютера technical interview, ask one question at a time, evaluate candidate answers, and + explain gaps. Use for Процессоры, память, машинные инструкции и основы устройства компьютера.' --- # Архитектура компьютера — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Архитектура компьютера**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Архитектура компьютера**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Архитектура компьютера interview handbook](https://angular-ru.github.io/interview/computer-science/) as a **reference when it is accessible**. The editable source is [src/pages/computer-science/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/computer-science/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Архитектура компьютера interview handbook](https://angular-ru.github.io/interview/computer-science/) as a + **reference when it is accessible**. The editable source is + [src/pages/computer-science/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/computer-science/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/css/SKILL.md b/skills/css/SKILL.md index 89bee5fb..22a3787b 100644 --- a/skills/css/SKILL.md +++ b/skills/css/SKILL.md @@ -1,11 +1,14 @@ --- name: css -description: "Conduct a CSS technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Layout, Flexbox, Grid, каскад, адаптивность, rendering и performance." +description: + 'Conduct a CSS technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for + Layout, Flexbox, Grid, каскад, адаптивность, rendering и performance.' --- # CSS — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **CSS**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **CSS**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [CSS interview handbook](https://angular-ru.github.io/interview/css/) as a **reference when it is accessible**. The editable source is [src/pages/css/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/css/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [CSS interview handbook](https://angular-ru.github.io/interview/css/) as a **reference when it is + accessible**. The editable source is + [src/pages/css/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/css/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/databases-sql/SKILL.md b/skills/databases-sql/SKILL.md index 72f22e1c..a5666467 100644 --- a/skills/databases-sql/SKILL.md +++ b/skills/databases-sql/SKILL.md @@ -1,11 +1,14 @@ --- name: databases-sql -description: "Conduct a Базы данных technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for SQL, проектирование схем, индексы, транзакции и производительность запросов." +description: + 'Conduct a Базы данных technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. + Use for SQL, проектирование схем, индексы, транзакции и производительность запросов.' --- # Базы данных — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Базы данных**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Базы данных**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Базы данных interview handbook](https://angular-ru.github.io/interview/databases-sql/) as a **reference when it is accessible**. The editable source is [src/pages/databases-sql/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/databases-sql/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Базы данных interview handbook](https://angular-ru.github.io/interview/databases-sql/) as a **reference when + it is accessible**. The editable source is + [src/pages/databases-sql/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/databases-sql/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/development-process/SKILL.md b/skills/development-process/SKILL.md index 5eeb2d29..a11a4179 100644 --- a/skills/development-process/SKILL.md +++ b/skills/development-process/SKILL.md @@ -1,11 +1,14 @@ --- name: development-process -description: "Conduct a Процессы разработки technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Scrum, Kanban, планирование, декомпозиция и взаимодействие с аналитиками." +description: + 'Conduct a Процессы разработки technical interview, ask one question at a time, evaluate candidate answers, and + explain gaps. Use for Scrum, Kanban, планирование, декомпозиция и взаимодействие с аналитиками.' --- # Процессы разработки — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Процессы разработки**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Процессы разработки**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Процессы разработки interview handbook](https://angular-ru.github.io/interview/development-process/) as a **reference when it is accessible**. The editable source is [src/pages/development-process/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/development-process/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Процессы разработки interview handbook](https://angular-ru.github.io/interview/development-process/) as a + **reference when it is accessible**. The editable source is + [src/pages/development-process/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/development-process/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/docker/SKILL.md b/skills/docker/SKILL.md index cf558acc..e668917e 100644 --- a/skills/docker/SKILL.md +++ b/skills/docker/SKILL.md @@ -1,11 +1,14 @@ --- name: docker -description: "Conduct a Docker technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Образы, контейнеры, Dockerfile, Compose и практический запуск приложений." +description: + 'Conduct a Docker technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for Образы, контейнеры, Dockerfile, Compose и практический запуск приложений.' --- # Docker — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Docker**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Docker**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Docker interview handbook](https://angular-ru.github.io/interview/docker/) as a **reference when it is accessible**. The editable source is [src/pages/docker/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/docker/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Docker interview handbook](https://angular-ru.github.io/interview/docker/) as a **reference when it is + accessible**. The editable source is + [src/pages/docker/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/docker/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/frontend-architecture-patterns/SKILL.md b/skills/frontend-architecture-patterns/SKILL.md index 6cfb99f3..ff831969 100644 --- a/skills/frontend-architecture-patterns/SKILL.md +++ b/skills/frontend-architecture-patterns/SKILL.md @@ -1,11 +1,14 @@ --- name: frontend-architecture-patterns -description: "Conduct a Организация кода technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Модульные границы, зависимости, архитектурные паттерны и организация frontend-кода." +description: + 'Conduct a Организация кода technical interview, ask one question at a time, evaluate candidate answers, and explain + gaps. Use for Модульные границы, зависимости, архитектурные паттерны и организация frontend-кода.' --- # Организация кода — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Организация кода**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Организация кода**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Организация кода interview handbook](https://angular-ru.github.io/interview/frontend-architecture-patterns/) as a **reference when it is accessible**. The editable source is [src/pages/frontend-architecture-patterns/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/frontend-architecture-patterns/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Организация кода interview handbook](https://angular-ru.github.io/interview/frontend-architecture-patterns/) + as a **reference when it is accessible**. The editable source is + [src/pages/frontend-architecture-patterns/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/frontend-architecture-patterns/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/git/SKILL.md b/skills/git/SKILL.md index 21b4ff04..c941dbeb 100644 --- a/skills/git/SKILL.md +++ b/skills/git/SKILL.md @@ -1,11 +1,14 @@ --- name: git -description: "Conduct a Git technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for История изменений, ветвление, rebase, merge, pull requests и командная работа." +description: + 'Conduct a Git technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for + История изменений, ветвление, rebase, merge, pull requests и командная работа.' --- # Git — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Git**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Git**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Git interview handbook](https://angular-ru.github.io/interview/git/) as a **reference when it is accessible**. The editable source is [src/pages/git/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/git/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Git interview handbook](https://angular-ru.github.io/interview/git/) as a **reference when it is + accessible**. The editable source is + [src/pages/git/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/git/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/html/SKILL.md b/skills/html/SKILL.md index 0b646164..d4ca1f5d 100644 --- a/skills/html/SKILL.md +++ b/skills/html/SKILL.md @@ -1,11 +1,14 @@ --- name: html -description: "Conduct a HTML technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Семантика, формы, доступность, metadata, SEO и структура документов." +description: + 'Conduct a HTML technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for + Семантика, формы, доступность, metadata, SEO и структура документов.' --- # HTML — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **HTML**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **HTML**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [HTML interview handbook](https://angular-ru.github.io/interview/html/) as a **reference when it is accessible**. The editable source is [src/pages/html/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/html/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [HTML interview handbook](https://angular-ru.github.io/interview/html/) as a **reference when it is + accessible**. The editable source is + [src/pages/html/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/html/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/infrastructure/SKILL.md b/skills/infrastructure/SKILL.md index 47f0aeff..30c1fc71 100644 --- a/skills/infrastructure/SKILL.md +++ b/skills/infrastructure/SKILL.md @@ -1,11 +1,14 @@ --- name: infrastructure -description: "Conduct a DevOps technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for CI/CD, deployment, delivery pipelines, feature flags и эксплуатация." +description: + 'Conduct a DevOps technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for CI/CD, deployment, delivery pipelines, feature flags и эксплуатация.' --- # DevOps — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **DevOps**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **DevOps**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [DevOps interview handbook](https://angular-ru.github.io/interview/infrastructure/) as a **reference when it is accessible**. The editable source is [src/pages/infrastructure/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/infrastructure/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [DevOps interview handbook](https://angular-ru.github.io/interview/infrastructure/) as a **reference when it + is accessible**. The editable source is + [src/pages/infrastructure/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/infrastructure/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/integrations/SKILL.md b/skills/integrations/SKILL.md index 21334efe..5c416b74 100644 --- a/skills/integrations/SKILL.md +++ b/skills/integrations/SKILL.md @@ -1,11 +1,14 @@ --- name: integrations -description: "Conduct a Интеграции technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for REST, SOAP, очереди, брокеры сообщений и интеграционные паттерны." +description: + 'Conduct a Интеграции technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. + Use for REST, SOAP, очереди, брокеры сообщений и интеграционные паттерны.' --- # Интеграции — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Интеграции**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Интеграции**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Интеграции interview handbook](https://angular-ru.github.io/interview/integrations/) as a **reference when it is accessible**. The editable source is [src/pages/integrations/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/integrations/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Интеграции interview handbook](https://angular-ru.github.io/interview/integrations/) as a **reference when it + is accessible**. The editable source is + [src/pages/integrations/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/integrations/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/javascript/SKILL.md b/skills/javascript/SKILL.md index 1766d0ca..080e391c 100644 --- a/skills/javascript/SKILL.md +++ b/skills/javascript/SKILL.md @@ -1,11 +1,14 @@ --- name: javascript -description: "Conduct a JavaScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Язык, асинхронность, Event Loop, DOM, fetch и runtime браузера." +description: + 'Conduct a JavaScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. + Use for Язык, асинхронность, Event Loop, DOM, fetch и runtime браузера.' --- # JavaScript — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **JavaScript**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **JavaScript**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [JavaScript interview handbook](https://angular-ru.github.io/interview/javascript/) as a **reference when it is accessible**. The editable source is [src/pages/javascript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/javascript/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [JavaScript interview handbook](https://angular-ru.github.io/interview/javascript/) as a **reference when it + is accessible**. The editable source is + [src/pages/javascript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/javascript/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/linux/SKILL.md b/skills/linux/SKILL.md index a39308df..2e246291 100644 --- a/skills/linux/SKILL.md +++ b/skills/linux/SKILL.md @@ -1,11 +1,14 @@ --- name: linux -description: "Conduct a Linux / Unix technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Shell, файлы, права, процессы, сеть и рабочее окружение Unix." +description: + 'Conduct a Linux / Unix technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. + Use for Shell, файлы, права, процессы, сеть и рабочее окружение Unix.' --- # Linux / Unix — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Linux / Unix**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Linux / Unix**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Linux / Unix interview handbook](https://angular-ru.github.io/interview/linux/) as a **reference when it is accessible**. The editable source is [src/pages/linux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/linux/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Linux / Unix interview handbook](https://angular-ru.github.io/interview/linux/) as a **reference when it is + accessible**. The editable source is + [src/pages/linux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/linux/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/nodejs/SKILL.md b/skills/nodejs/SKILL.md index b44c5f1a..7a796678 100644 --- a/skills/nodejs/SKILL.md +++ b/skills/nodejs/SKILL.md @@ -1,11 +1,14 @@ --- name: nodejs -description: "Conduct a Node.js technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Node runtime, npm, HTTP, networking, tooling и observability." +description: + 'Conduct a Node.js technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for Node runtime, npm, HTTP, networking, tooling и observability.' --- # Node.js — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Node.js**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Node.js**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Node.js interview handbook](https://angular-ru.github.io/interview/nodejs/) as a **reference when it is accessible**. The editable source is [src/pages/nodejs/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/nodejs/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Node.js interview handbook](https://angular-ru.github.io/interview/nodejs/) as a **reference when it is + accessible**. The editable source is + [src/pages/nodejs/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/nodejs/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/operating-systems/SKILL.md b/skills/operating-systems/SKILL.md index 5468cf4a..f9f35175 100644 --- a/skills/operating-systems/SKILL.md +++ b/skills/operating-systems/SKILL.md @@ -1,11 +1,14 @@ --- name: operating-systems -description: "Conduct a Операционные системы technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Процессы, потоки, память, файловые системы и сетевые основы." +description: + 'Conduct a Операционные системы technical interview, ask one question at a time, evaluate candidate answers, and + explain gaps. Use for Процессы, потоки, память, файловые системы и сетевые основы.' --- # Операционные системы — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Операционные системы**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Операционные системы**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Операционные системы interview handbook](https://angular-ru.github.io/interview/operating-systems/) as a **reference when it is accessible**. The editable source is [src/pages/operating-systems/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/operating-systems/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Операционные системы interview handbook](https://angular-ru.github.io/interview/operating-systems/) as a + **reference when it is accessible**. The editable source is + [src/pages/operating-systems/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/operating-systems/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/qa/SKILL.md b/skills/qa/SKILL.md index f342fa35..bdd8e5b6 100644 --- a/skills/qa/SKILL.md +++ b/skills/qa/SKILL.md @@ -1,11 +1,14 @@ --- name: qa -description: "Conduct a QA technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Стратегия тестирования, unit/integration/e2e, метрики качества и анализ дефектов." +description: + 'Conduct a QA technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for + Стратегия тестирования, unit/integration/e2e, метрики качества и анализ дефектов.' --- # QA — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **QA**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **QA**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [QA interview handbook](https://angular-ru.github.io/interview/qa/) as a **reference when it is accessible**. The editable source is [src/pages/qa/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/qa/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [QA interview handbook](https://angular-ru.github.io/interview/qa/) as a **reference when it is accessible**. + The editable source is + [src/pages/qa/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/qa/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/react/SKILL.md b/skills/react/SKILL.md index c741e8ba..fe00d77b 100644 --- a/skills/react/SKILL.md +++ b/skills/react/SKILL.md @@ -1,11 +1,14 @@ --- name: react -description: "Conduct a React technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Components, hooks, state, rendering, routing, forms и экосистема React." +description: + 'Conduct a React technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for Components, hooks, state, rendering, routing, forms и экосистема React.' --- # React — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **React**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **React**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [React interview handbook](https://angular-ru.github.io/interview/react/) as a **reference when it is accessible**. The editable source is [src/pages/react/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/react/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [React interview handbook](https://angular-ru.github.io/interview/react/) as a **reference when it is + accessible**. The editable source is + [src/pages/react/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/react/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/state-management/SKILL.md b/skills/state-management/SKILL.md index d811bc88..908b91fc 100644 --- a/skills/state-management/SKILL.md +++ b/skills/state-management/SKILL.md @@ -1,11 +1,14 @@ --- name: state-management -description: "Conduct a State Management technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Client/server/URL state, кэширование, нормализация и state managers." +description: + 'Conduct a State Management technical interview, ask one question at a time, evaluate candidate answers, and explain + gaps. Use for Client/server/URL state, кэширование, нормализация и state managers.' --- # State Management — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **State Management**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **State Management**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [State Management interview handbook](https://angular-ru.github.io/interview/state-management/) as a **reference when it is accessible**. The editable source is [src/pages/state-management/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/state-management/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [State Management interview handbook](https://angular-ru.github.io/interview/state-management/) as a + **reference when it is accessible**. The editable source is + [src/pages/state-management/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/state-management/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/system-analysis/SKILL.md b/skills/system-analysis/SKILL.md index 0f27ad60..e52e7f97 100644 --- a/skills/system-analysis/SKILL.md +++ b/skills/system-analysis/SKILL.md @@ -1,11 +1,14 @@ --- name: system-analysis -description: "Conduct a Системный анализ technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Требования, user stories, процессы и аналитические артефакты." +description: + 'Conduct a Системный анализ technical interview, ask one question at a time, evaluate candidate answers, and explain + gaps. Use for Требования, user stories, процессы и аналитические артефакты.' --- # Системный анализ — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Системный анализ**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Системный анализ**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Системный анализ interview handbook](https://angular-ru.github.io/interview/system-analysis/) as a **reference when it is accessible**. The editable source is [src/pages/system-analysis/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-analysis/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Системный анализ interview handbook](https://angular-ru.github.io/interview/system-analysis/) as a + **reference when it is accessible**. The editable source is + [src/pages/system-analysis/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-analysis/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/system-design/SKILL.md b/skills/system-design/SKILL.md index 5a880db8..c282d103 100644 --- a/skills/system-design/SKILL.md +++ b/skills/system-design/SKILL.md @@ -1,11 +1,14 @@ --- name: system-design -description: "Conduct a Проектирование UI technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for UI-архитектура, rendering strategies, масштабирование и технические компромиссы." +description: + 'Conduct a Проектирование UI technical interview, ask one question at a time, evaluate candidate answers, and explain + gaps. Use for UI-архитектура, rendering strategies, масштабирование и технические компромиссы.' --- # Проектирование UI — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Проектирование UI**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Проектирование UI**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Проектирование UI interview handbook](https://angular-ru.github.io/interview/system-design/) as a **reference when it is accessible**. The editable source is [src/pages/system-design/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-design/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Проектирование UI interview handbook](https://angular-ru.github.io/interview/system-design/) as a **reference + when it is accessible**. The editable source is + [src/pages/system-design/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/system-design/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/typescript/SKILL.md b/skills/typescript/SKILL.md index 843e410c..77f1ea2f 100644 --- a/skills/typescript/SKILL.md +++ b/skills/typescript/SKILL.md @@ -1,11 +1,14 @@ --- name: typescript -description: "Conduct a TypeScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Типизация, generics, utility types, архитектура типов и runtime-контракты." +description: + 'Conduct a TypeScript technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. + Use for Типизация, generics, utility types, архитектура типов и runtime-контракты.' --- # TypeScript — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **TypeScript**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **TypeScript**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [TypeScript interview handbook](https://angular-ru.github.io/interview/typescript/) as a **reference when it is accessible**. The editable source is [src/pages/typescript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/typescript/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [TypeScript interview handbook](https://angular-ru.github.io/interview/typescript/) as a **reference when it + is accessible**. The editable source is + [src/pages/typescript/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/typescript/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/ui-ux/SKILL.md b/skills/ui-ux/SKILL.md index 266c1b17..328cae0b 100644 --- a/skills/ui-ux/SKILL.md +++ b/skills/ui-ux/SKILL.md @@ -1,11 +1,14 @@ --- name: ui-ux -description: "Conduct a UI/UX technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for Usability, accessibility, сценарии пользователей, интерфейсные состояния и продуктовые решения." +description: + 'Conduct a UI/UX technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use + for Usability, accessibility, сценарии пользователей, интерфейсные состояния и продуктовые решения.' --- # UI/UX — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **UI/UX**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **UI/UX**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [UI/UX interview handbook](https://angular-ru.github.io/interview/ui-ux/) as a **reference when it is accessible**. The editable source is [src/pages/ui-ux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ui-ux/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [UI/UX interview handbook](https://angular-ru.github.io/interview/ui-ux/) as a **reference when it is + accessible**. The editable source is + [src/pages/ui-ux/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/ui-ux/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/skills/web-protocols/SKILL.md b/skills/web-protocols/SKILL.md index d2cb52b2..e5552247 100644 --- a/skills/web-protocols/SKILL.md +++ b/skills/web-protocols/SKILL.md @@ -1,11 +1,14 @@ --- name: web-protocols -description: "Conduct a Веб-протоколы и безопасность technical interview, ask one question at a time, evaluate candidate answers, and explain gaps. Use for HTTP, браузерная сеть, authentication, authorization и web security." +description: + 'Conduct a Веб-протоколы и безопасность technical interview, ask one question at a time, evaluate candidate answers, + and explain gaps. Use for HTTP, браузерная сеть, authentication, authorization и web security.' --- # Веб-протоколы и безопасность — interview practice -Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an answer, or run a mock interview about **Веб-протоколы и безопасность**. +Use this skill when the user wants to prepare for an interview, practice technical questions, receive feedback on an +answer, or run a mock interview about **Веб-протоколы и безопасность**. ## Topics to cover @@ -17,18 +20,28 @@ Use this skill when the user wants to prepare for an interview, practice technic ## Interview workflow -1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and let the candidate change either at any time. -2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. -3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. Point out inaccuracies explicitly and respectfully. -4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before moving to the next topic. -5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on architecture, constraints, and trade-offs. -6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never invent a numerical score without stating the criteria. +1. Use the role level and language already given by the candidate. Otherwise default to **Middle** and **Russian**, and + let the candidate change either at any time. +2. Ask **one question at a time**. Choose questions from the topics above and vary between fundamentals, practical + situations, debugging, and trade-offs. Do not reveal the solution before the candidate answers. +3. Wait for an answer, then assess **correctness**, **completeness**, **reasoning**, and **practical application**. + Point out inaccuracies explicitly and respectfully. +4. Give a concise reference answer, explain the missing details and edge cases, and ask a focused follow-up before + moving to the next topic. +5. Adapt difficulty: Junior focuses on fundamentals; Middle on real implementation and debugging; Senior on + architecture, constraints, and trade-offs. +6. After several questions, provide a short progress summary: strengths, gaps, and the next topics to study. Never + invent a numerical score without stating the criteria. ## Grounding and boundaries -- Use the [Веб-протоколы и безопасность interview handbook](https://angular-ru.github.io/interview/web-protocols/) as a **reference when it is accessible**. The editable source is [src/pages/web-protocols/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/web-protocols/index.md). -- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. -- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official documentation for verification; state uncertainty instead of inventing behavior. +- Use the [Веб-протоколы и безопасность interview handbook](https://angular-ru.github.io/interview/web-protocols/) as a + **reference when it is accessible**. The editable source is + [src/pages/web-protocols/index.md](https://github.com/Angular-RU/angular-ru-interview-questions/blob/main/src/pages/web-protocols/index.md). +- This skill contains an interview **workflow and topic outline**, not a local copy of every question and answer. If the + reference cannot be opened, rely on your own knowledge and **do not claim to have verified the handbook**. +- For version-dependent APIs, ask which version the user targets when that changes the answer. Prefer official + documentation for verification; state uncertainty instead of inventing behavior. - If the user requests a direct explanation instead of an interview, explain the topic without forcing the Q&A workflow. ## Example requests diff --git a/src/components/SkillHero.astro b/src/components/SkillHero.astro index 95b2b437..39a07683 100644 --- a/src/components/SkillHero.astro +++ b/src/components/SkillHero.astro @@ -29,7 +29,9 @@ const base = import.meta.env.BASE_URL.replace(/\/$/, ''); href={`https://github.com/Angular-RU/angular-ru-interview-questions/tree/main/skills/${skill.slug}`} rel="noopener noreferrer" target="_blank" - >Исходный код + > + Исходный код + @@ -49,7 +51,9 @@ const base = import.meta.env.BASE_URL.replace(/\/$/, '');
/{skill.slug}
01 Choose your level
02 Answer questions
-
03 Get feedback
+
+ 03 Get feedback +
diff --git a/src/components/SkillInstall.astro b/src/components/SkillInstall.astro index 6d8e9995..88c995a2 100644 --- a/src/components/SkillInstall.astro +++ b/src/components/SkillInstall.astro @@ -14,7 +14,9 @@ const {command} = Astro.props; + > + $ + {command}