Make tests fast enough that devs actually run them
Reduce test runtime by separating unit/integration/e2e, improving isolation, enabling parallelism, and running the right tests at the right time.
Create a skill called "Test Suite Speed Clinic". Inputs: - Current test types and runtimes (rough is OK) - CI constraints (parallel jobs, runner limits) Output: - A lane strategy (PR vs nightly vs on-demand) - A prioritized list of speedups (parallelism, isolation, fixtures) - A measurement plan (dashboards, budgets, regression detection)
Slow tests create slow feedback loops. This recipe breaks the suite into lanes and
introduces optimization tactics that preserve coverage without blocking PRs for an hour.
Cut pipeline time with caching, parallelism, and smarter triggers
Reduce CI wall-clock time by implementing dependency caching, parallelization/sharding, and filtering out unnecessary pipeline runs.
Stop flaky tests from blocking PRs while you fix them
Quarantine known flaky tests into a separate lane so they don't block merges, while preserving visibility and enforcing a fix-by deadline.
Ship new creatives every week without chaos
Creative teams burn out when "we need new ads" arrives as an emergency. This recipe creates a weekly sprint system: inputs, brief template, production checklist, QA, and a testing plan that compounds learning.
Improve retention with scroll-stopping openings
Generates and rewrites hooks optimized for your platform and audience intent. It produces multiple hook styles (curiosity, contrast, payoff-first) and recommends which to test, based on your goals and content type.