Agent skill

Playwright Test

by Arman-Kudaibergenov in Arman-Kudaibergenov/1c-ai-development-kit

Этот скилл MUST быть вызван когда пользователь говорит "напиши UI-тест", "создай playwright тест", "scaffold playwright", "протестируй фичу в браузере".

AGPL-3.0Auto-check: notesTesting & QA

Install Playwright Test

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/playwright-test .claude/skills/playwright-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .claude/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/playwright-test .agents/skills/playwright-test && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .agents/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/playwright-test .cursor/skills/playwright-test && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .cursor/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git --path .claude/skills/playwright-test

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/playwright-test .gemini/skills/playwright-test && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .gemini/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/playwright-test .github/skills/playwright-test && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .github/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Arman-Kudaibergenov/1c-ai-development-kit playwright-test --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Arman-Kudaibergenov/1c-ai-development-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/playwright-test .opencode/skills/playwright-test && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "playwright-test" agent skill from https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/master/.claude/skills/playwright-test into .opencode/skills/playwright-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-test", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: playwright-test
GitHub stars: 166
Token cost: ~2k tokens
SKILL.md length: 397 words
Files: 1
Skills in repo: 50
Repo updated: May 25, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Works in 2 steps: JSONL-лог теста → Журнал регистрации 1С
Tasks that involve Browser testing
SKILL.md covers Когда использовать, Когда НЕ использовать, Шаг 1 — Scaffold… and Шаг 2 — Определить контрольные…, plus 6 more sections
Calls npm and npx

What it does

Playwright Test is an agent skill from Arman-Kudaibergenov/1c-ai-development-kit. Этот скилл MUST быть вызван когда пользователь говорит "напиши UI-тест", "создай playwright тест", "scaffold playwright", "протестируй фичу в браузере". SHOULD также вызывать после деплоя фичи 1С для создания автоматизированного регрессионного теста. Do NOT использовать для интерактивной автоматизации браузера — используй 1c-web-session или web-test.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Browser testing. It works with Playwright and npm. The repository describes itself as: Comprehensive AI agents, skills and rules toolkit for 1C:Enterprise development in Cursor IDE. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Browser testing

Example prompts

“напиши UI-тест”
“создай playwright тест”
“scaffold playwright”
“/playwright-test”

Requirements

Node.js
Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash

Workflow steps

2 steps, taken from the step headings in SKILL.md.

JSONL-лог теста
Журнал регистрации 1С

What it can do on your machine

Read from SKILL.md and the folder at commit 92d389e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npm
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Playwright Test loads about 2k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~92
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Arman-Kudaibergenov/1c-ai-development-kit at commit 92d389e, republished under its AGPL-3.0 licence (© Arman-Kudaibergenov). 397 words, ~1,964 tokens.

Download SKILL.mdSave it as .claude/skills/playwright-test/SKILL.md (or your agent's skills folder).

name: playwright-test
description: Этот скилл MUST быть вызван когда пользователь говорит "напиши UI-тест", "создай playwright тест", "scaffold playwright", "протестируй фичу в браузере". SHOULD также вызывать после деплоя фичи 1С для создания автоматизированного регрессионного теста. Do NOT использовать для интерактивной автоматизации браузера — используй 1c-web-session или web-test.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
argument-hint: <feature-name>

/playwright-test — Scaffold UI-теста для 1С фичи

Автономный Playwright-тест, который запускается без AI (npm run test:ui), пишет точечные наблюдения в JSONL, а Claude выносит вердикт по логу.

Когда использовать

После деплоя фичи в базу (/db-load-xml → /db-update)
Фича затрагивает UI (формы, кнопки, табличные части)

Когда НЕ использовать

Backend-only фича (новый MCP-инструмент, только BSL без форм)
Изменения только в конфигурации/правах/подсистемах без UI-эффектов

Шаг 1 — Scaffold инфраструктуры (одноразово на проект)

Проверить наличие package.json и playwright.config.js в корне целевого проекта.

Если отсутствуют — создать из шаблонов:

package.json

json

{
  "name": "<project-name>-tests",
  "private": true,
  "scripts": {
    "test:ui": "npx playwright test",
    "test:ui:headed": "npx playwright test --headed",
    "test:ui:debug": "npx playwright test --debug"
  },
  "devDependencies": {
    "@playwright/test": "^1.50.0"
  }
}

playwright.config.js

javascript

const { defineConfig } = require('@playwright/test');

module.exports = defineConfig({
  testDir: './tests/playwright',
  timeout: 60000,
  retries: 0,
  use: {
    // URL базы 1С — подставить из CLAUDE.md проекта
    baseURL: 'http://localhost:8080',
    // 1С веб-клиент: headless ненадёжен для некоторых действий
    headless: true,
    viewport: { width: 1280, height: 720 },
    ignoreHTTPSErrors: true,
  },
  projects: [
    {
      name: '1c-ui',
      use: { browserName: 'chromium' },
    },
  ],
});

После создания:

bash

cd <project-root> && npm install && npx playwright install chromium

Шаг 2 — Определить контрольные точки (UI checkpoints)

До написания теста — определить что именно проверяется. Источники:

openspec/changes/<feature>/design.md → секция ## UI checkpoints
Form.xml фичи → элементы формы, кнопки, команды
Здравый смысл → после действия X что меняется на экране?

Формат контрольной точки:

<действие пользователя> → <ожидаемое наблюдение на экране>

Примеры:

Нажать "Провести" → заголовок содержит "№" и дату
Заполнить Контрагент → поле "Договор" стало доступно
Добавить строку в ТЧ Товары → количество строк увеличилось на 1

Если после действия ничего не меняется визуально — тест не может проверить. Нужно доработать UI (сообщение пользователю, смена статуса, индикатор).

Шаг 3 — Сгенерировать spec.js

Создать tests/playwright/<feature>.spec.js по паттерну:

javascript

// tests/playwright/<feature>.spec.js
const { test, expect } = require('@playwright/test');
const fs = require('fs');
const path = require('path');

const LOG_FILE = path.join(__dirname, '<feature>.log.jsonl');
const BASE_URL = '<url-from-project-claude-md>';

// --- Logging helpers ---
function log(step, observation) {
  const entry = {
    ts: new Date().toISOString(),
    step,
    ...observation,
  };
  fs.appendFileSync(LOG_FILE, JSON.stringify(entry) + '\n');
}

function clearLog() {
  if (fs.existsSync(LOG_FILE)) fs.unlinkSync(LOG_FILE);
}

// --- 1C helpers ---
async function clipboardPaste(page, value) {
  await page.evaluate((v) => navigator.clipboard.writeText(v), value);
  await page.keyboard.press('Control+A');
  await page.keyboard.press('Control+V');
}

async function checkFormClosed(page) {
  const hasModal = await page.locator('.modalSurface').count() > 0;
  const hasValidation = await page.locator('[title="Закрыть (Ctrl+Shift+Z)"]')
    .filter({ visible: true }).count() > 0;
  return { hasModal, hasValidation };
}

// --- Tests ---
test.describe('<Feature Name>', () => {
  test.beforeAll(() => clearLog());

  test('checkpoint: <description>', async ({ page }) => {
    // Navigate
    await page.goto(BASE_URL);
    await page.waitForTimeout(2000); // 1C web client init

    // Action
    // ... (clipboard paste, DLB clicks, etc.)

    // Observe — точечная проверка, НЕ полный DOM
    const fieldValue = await page.locator('[id$="_FieldName"]').textContent();
    const isVisible = await page.locator('[id$="_Element"]').isVisible();

    log('checkpoint-name', {
      fieldValue,
      isVisible,
      pass: fieldValue === 'expected',
    });

    expect(fieldValue).toBe('expected');
  });
});

Правила генерации spec.js

Один test() на контрольную точку — изолированная проверка
JSONL-лог обязателен — каждый test() пишет log(step, observation)
Наблюдения точечные: isVisible, textContent, count — НЕ полный снапшот
Селекторы 1С: суффиксные [id$="_FieldName_DLB"], НИКОГДА хардкод формы form40_
Ввод только через clipboard — стандартные fill()/type() не работают в 1С
aria-label и текст кнопок — не CSS-классы (нестабильны в 1С)

Анализ Form.xml для генерации

Прочитать Form.xml фичи (через Read или /form-info), извлечь:

Имена элементов → суффиксные селекторы [id$="_<ElementName>"]
Команды → кнопки для нажатия
Реквизиты формы → поля для проверки значений
TabularSection → проверка количества строк

Show full SKILL.md (156 more words)Show less

Шаг 4 — Запустить тест

bash

cd <project-root> && npm run test:ui 2>&1 || true

Если есть ошибки Playwright setup (браузер не установлен):

bash

npx playwright install chromium

Шаг 5 — Вердикт

AI читает два источника и выносит оценку:

1. JSONL-лог теста

bash

cat tests/playwright/<feature>.log.jsonl

Каждая строка — JSON-объект с step, pass, и observation-полями. Проверить: все pass: true?

2. Журнал регистрации 1С

json

{"name": "get_event_log", "arguments": {"count": 20}}

Проверить: нет ли ошибок, связанных с фичей, после прогона теста?

Формат вердикта

UI-тест: ✅ PASS (N/N checkpoints)
  - checkpoint-1: OK (field = "expected")
  - checkpoint-2: OK (element visible)
Журнал 1С: нет ошибок

или

UI-тест: ❌ FAIL (N-1/N checkpoints)
  - checkpoint-1: OK
  - checkpoint-2: FAIL (expected "Проведён", got "Новый")
  → Воспроизвести через Playwright MCP, browser_snapshot на шаге 2

При FAIL

Не повторять тест автоматически. Воспроизвести проблемный шаг через Playwright MCP (browser_navigate → browser_snapshot) для диагностики. browser_snapshot — инструмент отладки, не основной механизм.

Полный пример (end-to-end)

1. /db-load-xml + /db-update (фича уже в базе)
2. Проверить tests/ инфраструктуру → scaffold если нет
3. Прочитать Form.xml → извлечь элементы
4. Определить checkpoints из design.md
5. Сгенерировать tests/playwright/payment-form.spec.js
6. npm run test:ui → читать .log.jsonl
7. get_event_log → проверить ошибки
8. Вердикт: PASS/FAIL + детали

Ограничения

Только Chromium (1С веб-клиент оптимизирован под него)
headless: true может не работать для некоторых 1С-действий — переключить на headed через test:ui:headed
Тест проверяет UI-поведение, не бизнес-логику (для логики → /1c-test-runner)
package.json и playwright.config.js живут в целевом проекте, не в этом workspace
Clipboard paste требует разрешений — Chromium grant по умолчанию

Связанные скилы

/1c-web-session — интерактивная работа с 1С в браузере (для отладки теста)
/1c-test-runner — unit-тестирование бизнес-логики (серверная сторона)
/form-info — анализ Form.xml для извлечения элементов
/db-load-xml + /db-update — деплой фичи перед тестом

Files

Just SKILL.md in .claude/skills/playwright-test of Arman-Kudaibergenov/1c-ai-development-kit.

Open the folder on GitHubat commit 92d389e

Compare with similar skills

Playwright Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Playwright Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Playwright Test this skillArman-Kudaibergenov/1c-ai-development-kit	166	—	~2k	Automated safety check: Notes	AGPL-3.0	4 mo ago
PlaywrightKiln-AI/Kiln	5.2k	—	~1.3k	Automated safety check: Pass	Custom licence	today
UI Previewtingly-dev/tingly-box	351	—	~2k	Automated safety check: Notes	MPL-2.0	today
Run One SpecLiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator	1.8k	—	~746	Automated safety check: Pass	GPL-3.0	yesterday
UI Visual DebuggingNangoHQ/nango	13k	—	~1.3k	Automated safety check: Pass	Custom licence	today
Proxy Setupasmyshlyaev177/test-proxy-recorder	112	—	~4.3k	Automated safety check: Pass	MIT	today

Similar skills

Playwright
Kiln-AI/Kiln
Look at Kiln's UI in a real browser, and run its end-to-end tests.
5.2k GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed
UI Preview
tingly-dev/tingly-box
Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser.
351 GitHub stars~2k tokensUpdated today
Testing & QAAuto-check: notes
Run One Spec
LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator
Run a single Node, browser, or Playwright spec instead of the full suite.
1.8k GitHub stars~746 tokensUpdated yesterday
Testing & QAAuto-check passed
UI Visual Debugging
NangoHQ/nango
A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.
13k GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed
Proxy Setup
asmyshlyaev177/test-proxy-recorder
Set up test-proxy-recorder for any Playwright project. An agent skill from asmyshlyaev177/test-proxy-recorder.
112 GitHub stars~4.3k tokensUpdated today
Testing & QAAuto-check passed
Playwright Pnpm Workspace
mizchi/luna.mbt
A skill your agent uses when running Playwright tests in this repo (luna.mbt) and either the test fails to discover specs ("did not expect test.describe()" / "two different versions of…
173 GitHub stars~1.2k tokensUpdated 23 days ago
Testing & QAAuto-check passed

More from Arman-Kudaibergenov/1c-ai-development-kit

All 50 skills in this repo

1c Web Session
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван для управления 1С:Предприятие в веб-клиенте через Playwright MCP: запуск/перезапуск/завершение сеанса, навигация, создание и редактирование справочников и документов.
166 GitHub stars~2.5k tokensUpdated 4 mo ago
Auto-check: notes
Inspect
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван для анализа и инспекции любого объекта 1С из XML-выгрузки: конфигурация (cf-info), объект метаданных (meta-info), управляемая форма (form-info), схема компоновки данных…
166 GitHub stars~3.4k tokensUpdated 4 mo ago
Auto-check: notes
1c Project Init
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван когда пользователь говорит "инициализируем проект", "init project", просит настроить 1С-проект.
166 GitHub stars~4.2k tokensUpdated 4 mo ago
Auto-check: notes
Cf Edit
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван когда нужно изменить свойства конфигурации, добавить или удалить объект из состава ChildObjects, настроить роли по умолчанию.
166 GitHub stars~582 tokensUpdated 4 mo ago
Auto-check: notes
Cfe Diff
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван когда нужно проанализировать состав расширения (CFE): заимствованные объекты, перехватчики, проверить перенесены ли вставки.
166 GitHub stars~531 tokensUpdated 4 mo ago
Auto-check: notes
Cfe Init
Arman-Kudaibergenov/1c-ai-development-kit
Этот скилл MUST быть вызван когда пользователь просит создать новое расширение конфигурации (CFE) для исправления, доработки или дополнения.
166 GitHub stars~569 tokensUpdated 4 mo ago
Auto-check: notes

Works with

Questions about Playwright Test

What does Playwright Test do?

Этот скилл MUST быть вызван когда пользователь говорит "напиши UI-тест", "создай playwright тест", "scaffold playwright", "протестируй фичу в браузере". Playwright Test is an agent skill from Arman-Kudaibergenov/1c-ai-development-kit. Этот скилл MUST быть вызван когда пользователь говорит "напиши UI-тест", "создай playwright тест", "scaffold playwright", "протестируй фичу в браузере".

When should I use Playwright Test?

Playwright Test fits situations like: tasks that involve Browser testing.

How do I install Playwright Test in Claude Code?

Run `npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a claude-code`. Or copy the skill folder (.claude/skills/playwright-test in Arman-Kudaibergenov/1c-ai-development-kit) into .claude/skills/playwright-test in your project. Claude Code loads it when a task matches its description.

How do I install Playwright Test in Codex?

Run `npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a codex`. Or copy the skill folder (.claude/skills/playwright-test in Arman-Kudaibergenov/1c-ai-development-kit) into .agents/skills/playwright-test in your project. Codex loads it when a task matches its description.

Can I use Playwright Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Arman-Kudaibergenov/1c-ai-development-kit --skill playwright-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/playwright-test, .gemini/skills/playwright-test, .github/skills/playwright-test and .opencode/skills/playwright-test in your project.

What does Playwright Test need to run?

Going by SKILL.md and its folder, Playwright Test needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash.

Does Playwright Test access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Playwright Test safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Playwright Test use?

Playwright Test is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Playwright Test use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Playwright Test?

Skills that share tags, products or a category with Playwright Test: Playwright (Kiln-AI/Kiln, 5.2k stars), UI Preview (tingly-dev/tingly-box, 351 stars), Run One Spec (LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator, 1.8k stars) and UI Visual Debugging (NangoHQ/nango, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Playwright Test?

Arman-Kudaibergenov (a GitHub user) maintains it in Arman-Kudaibergenov/1c-ai-development-kit, which has 166 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on May 25, 2026.

Source: Arman-Kudaibergenov/1c-ai-development-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Playwright Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/playwright-test — Scaffold UI-теста для 1С фичи

Когда использовать

Когда НЕ использовать

Шаг 1 — Scaffold инфраструктуры (одноразово на проект)

package.json

playwright.config.js

Шаг 2 — Определить контрольные точки (UI checkpoints)

Шаг 3 — Сгенерировать spec.js

Правила генерации spec.js

Анализ Form.xml для генерации

Шаг 4 — Запустить тест

Шаг 5 — Вердикт

1. JSONL-лог теста

2. Журнал регистрации 1С

Формат вердикта

При FAIL

Полный пример (end-to-end)

Ограничения

Связанные скилы

Files

Compare with similar skills

Similar skills

More from Arman-Kudaibergenov/1c-ai-development-kit

Related

Questions about Playwright Test