effective-testing
Rapid Software Testing (RST)
Overview
Rapid Software Testing (RST) is a human-centered, context-driven methodology that treats the product as a mystery to be investigated. It focuses on people, heuristics, skills, and ethics to find the "bugs that matter" as efficiently as possible.
Part I: Introduction & Core Mindset
- The Product is a Mystery: Do not assume it works; probe it to discover its true nature.
- Testing is Learning: Every test is an episode of learning about the product's status.
- Testing vs. Checking: Testing is a human process of exploration; checking is algorithmic verification. See RST Workflows.
- The Responsible Tester: You are an independent agent accountable for the quality of your investigation.
- Vital Qualities: Empirical, Skilled, Different, Motivated, Available. See Tester Qualities.
Part II: Methodology & Process
- Model the Product: Use the HTSM to brainstorm coverage.
- Define Strategy: Use the Test Strategy Guide to prioritize risks.
- Execute Sessions: Use Session-Based Test Management (SBTM). Use the Session Template.
More from ab22593k/skills
latency-principles
Comprehensive framework for diagnosing, optimizing, and hiding latency in software systems. You MUST use this skill whenever the user mentions slow performance, response time, p99/tail latency, or asks about system throughput and concurrency. It covers Little's Law, Amdahl's Law, and strategies for Data/Compute optimization (e.g., zero-copy, wait-free sync, request hedging). Trigger this even for theoretical questions about latency laws or ballpark estimations using latency constants.
14expressive-design
Material 3 Expressive design system for Flutter (Android & Linux). You MUST use this skill whenever the user asks to improve, modernize, or transform a Flutter UI, especially for consumer, media, or communication apps. It provides exact specs for Bento Grids, Masonry, color convergence, variable fonts, and expressive motion. Trigger this for any request involving 'modern' or 'emotionally engaging' Flutter widgets, even if they don't explicitly mention 'Expressive' design. Do NOT use for banking or safety-critical apps where standard M3 is required.
13widget-previewer
Use the Flutter Widget Previewer to preview widgets in isolation with real-time rendering in Chrome. Use when working with Flutter widget previews, @Preview annotations, preview configurations, or widget development workflows. Triggers include setting up widget previewer, adding @Preview annotations, customizing previews, creating custom preview annotations, handling multiple preview configurations, or troubleshooting widget preview issues.
3generative-thinker
Guides the agent to apply Generativity Theory to solve problems by building high-leverage, open-ended systems. Use this skill when the user asks for "out of the box" ideas, platform strategies, or when a task benefits from enabling others to innovate rather than providing a narrow, single-purpose fix.
3kernel-maintainer
YOU MUST use this skill for ANY Rust Linux kernel work. This includes: writing kernel modules in Rust, reviewing Rust kernel patches, debugging kernel panics/crashes, working with kernel APIs (Mutex, SpinLock, UserPtr, IOCTL), adding module parameters, creating device drivers (character/block/network), handling kernel errors, memory allocation in kernel, and following kernel Rust coding standards. If the user mentions 'kernel' and 'Rust' together, USE THIS SKILL. Essential for kernel maintainers, patch contributors, and developers working with Rust For Linux (RFL).
1latency principles
Comprehensive framework for diagnosing, optimizing, and hiding latency in software systems. You MUST use this skill whenever the user mentions slow performance, response time, p99/tail latency, or asks about system throughput and concurrency. It covers Little's Law, Amdahl's Law, and strategies for Data/Compute optimization (e.g., zero-copy, wait-free sync, request hedging). Trigger this even for theoretical questions about latency laws or ballpark estimations using latency constants.
1