القائمة
Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Short-lived feature branches only — never commit on main; merge then push. TDD + lint + npm run ci as exit criteria before commit on the branch. Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.
Creates and edits project documentation for both public and internal audiences. Use when writing or updating README.md, AGENT_HANDOFF (or AGENTS.md), CONTRIBUTING, or internal docs (e.g. PM_PLAN, DEV_GUIDE, TEST_TDD, DESIGN_SYSTEM). Covers structure, tone, and what to include for each doc type.
Manifest V3 Chromium/Edge extension engineering for this repo: ephemeral service workers, chrome.storage rehydration, chrome.alarms, message passing (sendMessage, onMessage + sendResponse), extension context invalidation in content scripts, idle-first-message failures, and overlay/background wiring. Use when editing manifest.json, src/background/, src/content/page-overlay.ts, messaging, or when the user mentions MV3, service worker sleep, idle resume, Extension context invalidated, sendMessage, or runtime.connect.
Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with ESLint tiers in eslint.config.mjs. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.
Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review.
Shapes extension-wide architecture for this repo: boundaries between background, content scripts, and UI surfaces; composition with existing overlays; storage and messaging contracts; feature flags and permissions rationale. Use when designing a new epic, splitting work across layers, reviewing structural risk, or when the user asks for an extension architect, system design for the extension, or how features should be layered in MV3.
| name | tester |
| description | Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green. |
Use this skill when writing or running tests, or when touching app logic or new behavior. First action when adding new behavior: Read this skill and TEST_TDD.md, then write a failing test at the appropriate tier(s) before production code.
npm test → red, then code → green. Tier 2: Playwright — npm run test:e2e (after npm run build) → red, then code → green. Use Tier 2 whenever behavior spans the real browser or extension surfaces.npm run ci before merge.