Results for “the-mom-test”

妈妈唠叨模式 — 中国式妈妈提醒风格的生产力 coaching。底层行为仍是结构化排障、证据优先、完成质量检查。

妈妈唠叨模式 — 中国式妈妈提醒风格的生产力 coaching。底层行为仍是结构化排障、证据优先、完成质量检查。

Guides testing Megatron-LM: test layout, recipe YAML, adding and running unit/functional tests, golden values, marker filters, and CI parity.

Analyzes production code to find gaps in existing tests by reasoning about hypothetical mutations and checking whether tests would catch them.

Verifies that tests for already-implemented behavior are meaningful by temporarily breaking the production code and confirming the test fails for the expected reason.

Write effective unit tests with best practices for any project. Use when writing tests, creating test cases, improving test coverage, increasing confidence before release, or when the user mentions testing. Mutation score / assertion theater → test-mutation.

Executes Atomic Red Team tests mapped to MITRE ATT&CK techniques, performs coverage gap analysis, and runs detection validation loops to measure blue team visibility.

Generates unit tests for multiple languages and frameworks, including coverage reports and boundary/exception cases.

Use when writing or modifying tests in a Bun project

Provides comprehensive testing patterns for Perl applications using Test2::V0, Test::More, prove runner, mocking, and coverage analysis with Devel::Cover.

Runs and writes tests for a project, supporting unit, integration, and end-to-end scopes, plus two-pass TDD orchestration with quality-gate checks and regression sweeps.

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

Runs a relentless interview that asks every frontier question at once, round by round. Use when the user wants to be grilled on a design or map a design tree.

当意识到当前行为模式可能导致不理想的未来，需要一种具体方法来激发改变动力时

Runs and writes tests, verifies behavior, and orchestrates two-pass TDD across scoped modes, blocking on quality gates and never editing production code.

Writes Jest unit tests for Lightning Web Components using @salesforce/sfdx-lwc-jest, covering wire adapter mocks, imperative Apex mocking, and async rerender handling.

Go测试模式包括表格驱动测试、子测试、基准测试、模糊测试和测试覆盖率。遵循TDD方法论，采用地道的Go实践。

Simulates man-in-the-middle attacks using Ettercap, mitmproxy, and Bettercap in authorized environments to intercept, analyze, and modify network traffic for testing encryption enforcement, certificate validation, and detection capabilities.

Suggests oral contraceptives over injectable contraceptives for women with BMI ≥27 kg/m2 with comorbidities or BMI ≥30 kg/m2 seeking contraception, provided they are well‑informed and oral contraceptives are not contraindicated. Triggers include clinician questions such as “Which contraceptive method is less likely to cause weight gain in this obese patient?” or “Should I recommend oral pills instead of depot injection for this patient with BMI 29 and hypertension?”.

Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.

Escribe tests en Go con la biblioteca estándar: unitarios, table-driven, con mocks y cobertura, incluyendo modelos Bubbletea con teatest.

Gemini: A Family of Highly Capable Multimodal Models

A/B test design and experiment planning for paid advertising. Structured hypothesis framework, statistical significance calculator, test duration estimator, sample size calculator, and platform-specific experiment setup guides (Meta Experiments, Google Experiments, LinkedIn A/B). Use when user says A/B test, split test, experiment design, test hypothesis, statistical significance, sample size, or test duration.

Analyse experiment results, run validity checks (SRM, exposure parity, data integrity, novelty/primacy), interpret causally, make a ship/iterate/kill decision against the pre-declared rule, and append to cumulative learnings. Forces honest readouts — strips significance claims from underpowered or peek-violating tests; never lets directional results masquerade as causal wins. Load when results exist, or when the user says "read out this experiment", "analyse the test", "did the test win", "interpret the results", "what did we learn", "ship or kill", or when the experimentation orchestrator routes here.

Most teams run one test — expected peak for ten minutes — and believe they have