chrome-extension-development
Use when building Chrome extensions (Manifest V3). Covers floating panel architecture, sidepanel API, storage patterns, message passing, content scripts, SPA navigation detection, context menus, Vitest testing,...
Découvrez les skills blockchain testing, comparez leurs dépôts et consultez leurs instructions.
Use when building Chrome extensions (Manifest V3). Covers floating panel architecture, sidepanel API, storage patterns, message passing, content scripts, SPA navigation detection, context menus, Vitest testing,...
Use when automating browsers with Playwright/Puppeteer, testing Chrome extensions, using Chrome DevTools Protocol (CDP), handling dynamic content/SPAs, or debugging automation issues
Methods for working with the ios simulator, mcp, and maestro test framework
Use Playwright MCP to check UI styles and usability. Automatically used for requests like "check UI", "verify appearance", "take screenshot", "UI review", "screenshot analysis".
Generates comprehensive Elixir tests using ExUnit following TDD principles.
Use browser automation MCP (Playwright/Browser/Browser-Use) to validate UI flows, capture screenshots, and reproduce issues. Use when visual verification or web flow testing is needed.
Perform root-cause analysis for bugs/errors/regressions using logs, repro steps, and hypothesis testing. Use when the user reports “nie działa”, stack traces, failing tests, or regressions.
Generate comprehensive test cases for code
テスト駆動開発(TDD)を行うためのスキル。「TDDで実装して」「テストファーストで開発して」「テスト駆動で作って」などのリクエスト時に使用する。table driven testパターンを採用。
Test local web applications using Playwright for UI verification, debugging, screenshot capture, and end-to-end testing. Use when testing web apps, verifying UI behavior, or capturing screenshots of running app...
End-to-end testing with wallet automation using Synpress. Use this skill for testing dApp flows that require MetaMask/wallet interactions, transaction signing, and on-chain verification.
Test local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Browser automation via Playwriter MCP - works as a Chrome extension with full Playwright API access. Use for browser testing, web scraping, form filling, and any browser interaction.
Professional Quality Control expert for Odoo 19 development. Specializes in Unit testing, Integration testing, and compliance with OCA and Odoo SA standards in Docker environments. Use this skill when reviewing...
Write tests using TDD principles with integration tests as default and minimal mocking. Use when writing code, fixing bugs, or when user mentions tests, TDD, unit tests, integration tests, or testing strategy.
Testing best practices and TDD workflow. Use when writing tests, following TDD, or improving test coverage.
Testing setup for this project. MSW for API mocking, happy-dom environment, coverage thresholds. Triggers on "test setup", "msw", "mocking", "vitest", "testing".
Expert guidance for Python testing with pytest framework. Use when (1) writing unit tests or integration tests, (2) setting up test fixtures for setup/teardown, (3) parametrizing tests with multiple inputs, (4)...
Use when writing tests for pgdbm-based code - provides fixture selection decision tree and complete usage patterns without needing testing docs
テストコードのレビューを行うとき、テストの品質チェックを行うときに使用
Testing best practices for Lingx. Unit tests with Vitest, integration tests with Prisma, E2E tests with Playwright. Use when writing tests, reviewing test code, or setting up test infrastructure.
Generate Vitest test files for the dealflow-network project with proper setup, teardown, database patterns, and assertion styles. Use when creating tests for new features, database operations, or API endpoints.
Modern testing patterns for Svelte 5 using vitest-browser-svelte and Sveltest methodology. Use when users ask about testing Svelte components, unit tests, integration tests, vitest, vitest-browser-svelte, testi...
integration testing system compatibility dependencies validation coherence
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.