Search Results

Test-Driven Development specialist enforcing write-tests-first methodology with 80%+ test coverage across unit, integration, and E2E tests.

Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the te...

Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS vs Support vs AM distinctions). Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires. Strategic only —...

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG…

Trade compliance automation patterns: HS classification, tariff calculation, denied party screening, export controls, FTZ management, customs brokerage workflows, and regulatory audit trails for cross-border commerce.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks.

Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, httptest for API testing, testify assertions, and coverage measurement with TDD methodology.

Kotlin testing with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage with TDD methodology.

Test-driven development for Laravel with PHPUnit and Pest: factories, database testing, fakes, and coverage targets.

Verification loop for Laravel: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.

Perl testing with Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Playwright E2E testing patterns: Page Object Model, test configuration, CI/CD integration with artifact capture (screenshots, videos, traces), flaky test quarantine, and critical user flow coverage strategies.

Python testing with pytest: fixtures, parametrize, mocking with unittest.mock, hypothesis property-based testing, coverage with pytest-cov, and TDD methodology for Python applications.

Rust testing patterns: unit tests, integration tests, async testing with tokio::test, property-based testing with proptest, mocking strategies, and coverage measurement with cargo-tarpaulin.

SHA-256 content-hash caching for expensive file processing. Path-independent keys auto-invalidate on content change. Frozen dataclass cache entries with file-based O(1) storage.

Test-driven development for Spring Boot: JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo coverage.

Verification loop for Spring Boot: build, static analysis, tests with coverage, security scans, and diff review before release.

Thread-safe Swift data persistence using actors: in-memory cache with file-backed storage, eliminating data races by design.

Test-driven development enforcement: write-tests-first methodology, RED/GREEN/REFACTOR cycle, 80%+ coverage requirement across unit/integration/E2E, user journey definitions, test pyramid structure, and coverage verification gates.

Pre-PR verification pipeline: sequential build check, type check, lint, test with coverage, security scan, and diff review. Hard stop on build failure. Report all type errors before proceeding.

pytest-django, factory_boy, coverage

Lint, static analysis, coverage, security

Build, analysis, coverage, security scans

Write-tests-first with 80%+ coverage gates