plugins/ordis-quality-engineering/skills/using-quality-engineering/SKILL.md
Use when user asks about E2E testing, performance testing, chaos engineering, test automation, flaky tests, test data management, or quality practices - routes to specialist reference sheets with deep expertise instead of providing general guidance
npx skillsauth add tachyon-beep/skillpacks using-quality-engineeringInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Your entry point to quality engineering methodology. This skill routes you to the right reference sheet for comprehensive quality engineering guidance.
This is a meta-skill that:
You should use this skill: When facing testing challenges, quality automation, performance concerns, or reliability engineering problems.
Ad-Hoc Testing: Write tests → Hope they catch bugs → Fix when broken
Quality Engineering: Strategy → Architecture → Automation → Observability
Use quality-engineering when:
Don't use quality-engineering when:
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-quality-engineering/SKILL.md
Reference sheets like flaky-test-prevention.md are at:
skills/using-quality-engineering/flaky-test-prevention.md
NOT at:
skills/flaky-test-prevention.md ← WRONG PATH
When you see a link like [flaky-test-prevention.md](flaky-test-prevention.md), read the file from the same directory as this SKILL.md.
When the user asks about quality engineering topics, load the appropriate reference sheet:
| User's Question Topic | Load Reference Sheet | |----------------------|---------------------| | Test Fundamentals & Isolation | | | Test independence, idempotence, order-independence, isolation | test-isolation-fundamentals.md | | API & Integration Testing | | | REST/GraphQL API testing, request validation, API mocking | api-testing-strategies.md | | Component integration, database testing, test containers | integration-testing-patterns.md | | End-to-End & UI Testing | | | End-to-end test design, E2E anti-patterns, browser automation | e2e-testing-strategies.md | | Screenshot comparison, visual bugs, responsive testing | visual-regression-testing.md | | Performance & Load Testing | | | Load testing, benchmarking, performance regression | performance-testing-fundamentals.md | | Stress testing, spike testing, soak testing, capacity planning | load-testing-patterns.md | | Test Quality & Maintenance | | | Test coverage, quality dashboards, CI/CD quality gates | quality-metrics-and-kpis.md | | Test refactoring, page objects, reducing test debt | test-maintenance-patterns.md | | Mutation testing, test effectiveness, mutation score | mutation-testing.md | | Static Analysis & Security | | | SAST tools, ESLint, Pylint, code quality gates | static-analysis-integration.md | | Dependency scanning, Snyk, Dependabot, vulnerability management | dependency-scanning.md | | Fuzzing, random inputs, security vulnerabilities | fuzz-testing.md | | Advanced Testing Techniques | | | Property-based testing, Hypothesis, fast-check, invariants | property-based-testing.md | | Production Testing & Monitoring | | | Feature flags, canary testing, dark launches, prod monitoring | testing-in-production.md | | Metrics, tracing, alerting, quality signals | observability-and-monitoring.md | | Fault injection, resilience testing, failure scenarios | chaos-engineering-principles.md | | Test Infrastructure | | | Test pyramid, CI/CD integration, test organization | test-automation-architecture.md | | Fixtures, factories, seeding, test isolation, data pollution | test-data-management.md | | Flaky tests, race conditions, timing issues, non-determinism | flaky-test-prevention.md | | API contracts, schema validation, consumer-driven contracts | contract-testing.md |
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Only answer directly (without loading) for:
User demands "just answer, don't route" is NOT an exception - still load the reference sheet. User asking to skip routing signals they need the specialist guidance even more.
After routing, load the appropriate reference sheet for detailed guidance:
tools
Use when designing, implementing, or auditing an MCP (Model Context Protocol) server — tool API design, idempotency under agent retry, structured error envelopes agents can recover from, schema versioning across model drift, transport reliability (stdio / HTTP), output-shape and pagination discipline, and choosing between tools / resources / prompts / sampling. Also use when an MCP server's tools confuse agents, return unstructured errors, deadlock under concurrent calls, double-execute under retry, or lose state across reconnects. Do not use for general REST/GraphQL API design (use `/web-backend`), for client-side prompt engineering or tool-loop design (use `/llm-specialist`), for general in-process plugin architecture (use `/system-architect`), or for cryptographic-provenance audit trails (use `/audit-pipelines`).
development
Use when running **SQLite or DuckDB inside an application process** as the durable store — not as a development convenience but as the production database. Use when scaling an SQLite layer that worked at low concurrency and is now hitting SQLITE_BUSY, WAL bloat, lock contention, schema-migration ceremony, or correctness gaps under multi-process writers. Use when introducing DuckDB as an OLAP complement to an OLTP SQLite store, or when picking between the two for a new component. Pairs with `/web-backend` (the API surface above the DB) and `/audit-pipelines` (when the DB is also the audit trail). Do not load for server databases (Postgres, MySQL), key-value stores, or ORM choice in isolation.
development
Use when designing or critiquing the structure of a staged procedure — a wizard, configuration flow, troubleshooting tree, training curriculum, multi-stage approval pipeline, decision pipeline, or any decomposition of expert work into composable stages. Use for both producer work (build the decomposition) and critic work (audit a proposed decomposition). Use when reasoning about capacity, bottlenecks, or soundness of a procedural flow. Do not use for implementation-plan critique of code changes (use `/axiom-planning` instead), for execution-time dynamics (use `/simulation-foundations`), or for rendering an already-designed procedure as docs or UI (use `/technical-writer` or `/ux-designer`).
testing
Use when the user wants to draft fiction or creative nonfiction prose, get craft critique on prose they have written, or plan story structure, outline, or premise. Workshop-voiced. Three explicit modes (draft, critique, plan) and the router will refuse to begin work without a declared mode.