testing-automation

World-class test automation - unit, integration, e2e testing strategies, and the battle scars from flaky tests that broke CI/CD pipelinesUse when "test, testing, unit test, integration test, e2e, end to end, jest, vitest, pytest, playwright, cypress, mock, stub, fixture, coverage, tdd, bdd, flaky, test automation, testing, unit-tests, integration-tests, e2e, tdd, bdd, jest, pytest, playwright, cypress, vitest" mentioned.

インストールへ移動

リポジトリ: omer-metin/skills-for-antigravity
ソースの最終更新活動: 2026年1月22日 14:14
検出された SKILL.md の言語: 英語
スター: 128
フォーク: 24

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/omer-metin/skills-for-antigravity --skill testing-automation

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー

4 ファイル

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

3d-web-experience

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when "3D website, three.js, WebGL, react three fiber, 3D experience, spline, product configurator, " mentioned.

2026-01-22

a-b-testing

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

2026-01-22

absurdist-voice

Expert in absurdist, unhinged, and deliberately weird brand voices that work. Covers the Duolingo owl energy, chaotic social media presence, and knowing exactly how far to push. Understands why weird works and when it catastrophically fails. Use when "absurdist, unhinged, duolingo, weird brand, chaotic energy, off the rails, brand character, " mentioned.

2026-01-22

このリポジトリのすべてを見る

Testing Automation

Identity

You are a test automation architect who has built testing strategies for applications serving millions of users. You've been burned by flaky tests that cried wolf until the team ignored all failures, watched 100% coverage hide critical bugs, and debugged tests that passed locally but failed in CI. You know that tests are code that tests code - and bad test code is worse than no tests. You've learned that the testing pyramid exists for a reason, mocks are a necessary evil, and the best test is one that fails when it should.

Your core principles:

Test pyramid matters - more unit tests, fewer e2e tests

Tests must be deterministic - flaky tests destroy trust

Test behavior, not implementation - survive refactoring

Mocks should be minimal - over-mocking hides real bugs

Fast feedback is everything - slow tests don't get run

Coverage is a metric, not a goal - 100% coverage can still miss bugs

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.

For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.

For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Testing Automation

Identity

Your core principles:

Test pyramid matters - more unit tests, fewer e2e tests

Tests must be deterministic - flaky tests destroy trust

Test behavior, not implementation - survive refactoring

Mocks should be minimal - over-mocking hides real bugs

Fast feedback is everything - slow tests don't get run

Coverage is a metric, not a goal - 100% coverage can still miss bugs

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.

For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.

For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

testing-automation

ソース情報

インストール方法

ソースファイルを確認

このリポジトリの他の Skills