6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
Interview the user relentlessly about every aspect of a plan, walking down each branch of the design tree and resolving dependencies between decisions one-by-one until a shared…
Legacy support for SpecFlow (.NET BDD framework that predates Reqnroll) - for projects that haven't migrated yet. Mirrors Reqnroll's API closely (Reqnroll is the SpecFlow fork).
Executes real end-to-end verification against a running application after specification implementation.
Use when when you have a pre-cleaned spectral library (e.g., GNPS, MoNA, or MTBLS1572) with an existing training/test boundary established by prior work (e.g., MSBERT), and you…
Cross-cutting contract for the test-readiness pipeline. Specifies per-layer test speed budgets (unit / integration / smoke / E2E) as 95p targets, per-test hard caps, and per-layer…
Test: Verhandlung, Vergleich und Eskalation: konkreter Spezialworkflow mit Sachverhaltsklärung, Rechtsrahmen, Belegen, Risikoampel und verwertbarem Output.
Spike Test Setup - Auto-activating skill for Performance Testing. Triggers on: spike test setup, spike test setup Part of the Performance Testing skill category.
Process split datasets into training, validation, and testing sets for ML model development. Use when requesting "split dataset", "train-test split", or "data partitioning".
Prüft Sprachprüfungen, Zertifikate, Anerkennung, Täuschungsvorwurf und Fristen im Prüfungsrecht Hochschule.
Migrates Spring Boot applications to Boot 4 with Java 25, including related Spring Modulith 2 and Testcontainers 2 upgrade work.
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
Use when the user explicitly requests TDD workflow, or during a Ralph loop where TDD methodology is the selected workflow - not for routine coding tasks
Fix bugs with regression testing and auto-retry. Triggers on fix/debug/broken/error/not-working intent.
Use when connecting to embedded board targets (avm, xvm, hvm, hvm_x) over SSH. Triggers on any mention of board SSH, jump host connections, uploading scripts to boards, or…
Wendet den SSNIP-Test (Small but Significant Non-transitory Increase in Price / Hypothetischer-Monopolisten-Test) an.
Validate Server-Side Request Forgery (SSRF) vulnerabilities by testing if user-controlled URLs can reach internal services, cloud metadata endpoints, or alternative protocols.
Autonomous test-driven development cycle. Reads the project's spec + handoff TODO, picks the next queued or unchecked item, writes failing tests first, implements until the full…
CI testing for WebContainer apps with Playwright browser tests. Use when working with WebContainers or StackBlitz SDK. Trigger: "stackblitz CI".
Configure local development for WebContainer applications with hot reload and testing. Use when building browser-based IDEs, testing WebContainer file operations, or setting up…
Implement coding changes in engineer-reviewed stages. Use only when the user explicitly invokes $staged-implementation or directly requests staged implementation, incremental…
Stagehand is Browserbase's open source browser automation framework that blends natural-language actions with code-level control.
Global coding standards for all projects and languages. Use when writing any code. Covers linting with lintro, testing with coverage, semantic commits, PR creation, and code…
Odin coding standards. Use when writing Odin code. Covers idiomatic error handling with or_else and or_return, memory/allocator patterns, attributes, naming and API conventions,…
Python >= 3.11 coding standards. Use when writing Python code. Requires type hints, return types, Google-style docstrings, trailing commas, explicit kwargs, StrEnum with auto(),…
Rust coding standards. Use when writing Rust code. Covers edition, error handling with thiserror/anyhow, unsafe policy, type patterns, testing, documentation, and dependency…
Pre-flight with Chrome. Runs /start then confirms Chrome DevTools tools are available for UI testing. Use instead of /start when you need browser access.
Diagnose a blank, empty, or broken Claude Code statusline and suggest fixes. Invoke when the user says things like "my statusline is blank", "the statusline isn't showing",…
Use when asked to scrape a bot-protected website, bypass anti-bot detection, run Playwright with stealth patches, automate a site that blocks normal browsers, or simulate…
Halt physical degradation through climate control, archival materials, and conservation ethics. Use when setting up storage for a new acquisition, evaluating an existing storage…
Implement, review, or improve in-app purchases and subscriptions using StoreKit 2. Use when building paywalls with SubscriptionStoreView or ProductView, processing transactions…
Validate that documentation, READMEs, and onboarding guides are comprehensible to someone with zero prior context.
Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions \u2014 diagnosis quality, guiding policy strength, action coherence,…
Take a Stryker summary.json (from n8n:mutation-test), triage the surviving mutants by user-reachable-behaviour risk, write minimal assertion changes to kill the top 3-5…
Run AgentDojo benchmark environments to evaluate prompt-injection attacks and defenses against LLM agents before trusting them with real tools or data.
Stress Test Config - Auto-activating skill for Performance Testing. Triggers on: stress test config, stress test config Part of the Performance Testing skill category.
Stress-test eligibility criteria against the addressable population and site capacity before the protocol locks, since restrictive criteria are the biggest enrollment killer.
Run mutation testing against JS or TS projects to find tests that still pass when real defects are introduced.
Stress-test your product through 6 adversarial decision-maker personas -- skeptical board member, activist investor, power user, churned customer, competitor CEO, and enterprise…
Use mutation testing to expose weak Python tests before merge or release by checking which code changes survive the current test suite.
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
Use when working with Stripe API fundamentals, webhooks, authentication, error handling, CLI, or testing.
Implement production-grade Stripe integrations for SaaS billing. Covers subscription lifecycle management, checkout sessions, plan upgrades/downgrades with proration, usage-based…
Stripe webhook integration in Rails 8 — Stripe::Webhook.construct_event for signature + timestamp verification, idempotency via event.id, the canonical event types to handle…
Test skills via RED/GREEN/REFACTOR TDD with fresh subagents. Use when: validating skill behavior, preventing priming bias.
Abonelik fiyatlama stratejileri. 3-tier framework, price anchoring, charm pricing, regional pricing (18 ulke), introductory offers, win-back campaigns, churn prevention ve A/B…
A success check accepting any non-empty output passes on failure, because failure output is non-empty too.
Suede-owned experimentation discipline for hypotheses, sample sizing, test duration, significance, and repeatable experiment programs.
Catch a broken Suede Skills MCP before it ships — one that lists missing skills or returns malformed output.
Use gotestsum to turn noisy `go test` output into compact failure summaries, JUnit or JSON artifacts, and optional reruns of flaky tests before an agent starts fixing Go code.
Use when the user asks a generic testing question — "how do I test this?", "what should I check for X?" — that doesn't fit a more specific QA skill.
Use when the user asks for a formal test plan, entry/exit criteria, or a phased QA approach for a piece of work.
Use after sumo-qa-planning-qa-rollout to dispatch a written QA plan task-by-task. Each task runs in a fresh subagent (parallel where independent); each subagent's output goes…
Use when the user asks about test data — what data to test X, find a known-good record, validate an entry, register new known-good data.
Use after sumo-qa-deciding-approach picks tdd-scaffold, regression-first, or coverage-first-then-refactor — e.g.
Use when the user asks to plan QA for a story, ticket, or piece of work before coding starts. Identifies named risks anchored in the change shape, then proposes a smallest useful…
Use after sumo-qa-deciding-approach picks strengthen-test-coverage. Mutation-testing follow-up, raise-coverage tasks, killing weak assertions.
The official detailed guide for developing, testing, deploying, and auditing TRON smart contracts using the Sunhat toolkit.
Use when: Mau implement fitur/bugfix - Test-Driven Development SEBELUM production code
SurrealKit schema sync, rollout migrations, seeding, and declarative testing for SurrealDB apps. Part of the surreal-skills collection.