kienhaminh/anti-chaotic
Overview
This skill provides a disciplined QA testing framework for planning, creating, executing, and reporting Unit, E2E, Security, and Performance tests. It enforces a docs-first approach so every test and bug report ties back to the project documentation. Use it to produce reproducible test cases, automation-ready scripts, and clear defect reports that support fast remediation.
How this skill works
The skill first reads and verifies project documentation in the docs/ folder and halts to confirm with the user if docs are missing or contradictory. It discovers existing test cases, performs noun-verb extraction, keyword permutation checks, and state-transition mapping to generate a complete set of test cases. It can convert Markdown test cases to automation scripts, drive exploratory verification via a browser agent, execute runs, analyze failures, and produce standardized reports and bug tickets.
When to use it
- Planning a QA strategy or test plan for a new release or feature
- Creating formal, reproducible test cases from project documentation
- Executing manual exploratory or automated Unit, E2E, Security, or Performance tests
- Converting existing Markdown test cases into Playwright or similar automation
- Reporting bugs with clear Steps to Reproduce, Expected vs Actual results
Best practices
- Always read and base tests on files under docs/ before designing or running tests
- Stop and confirm with the user if docs are missing, empty, or conflict with the code
- Follow the Standard Test Case Format: ID, Preconditions, Test Data, Steps, Expected Results
- Cover happy path, negative path, boundary cases, edge cases, and cross-module flows
- Match generated test code to the project’s existing language and framework conventions
Example use cases
- Generate TC-AUTH-001..005 for login flows by extracting 'User' and 'Login' verbs from docs
- Create Playwright scripts from Markdown test cases and run them in CI to validate E2E flows
- Design security test checklist (OWASP-style) for authentication and input validation
- Run performance load tests for checkout flow and report regressions against baseline
- Execute browser-driven exploratory tests to capture visual regressions and UI bugs
FAQ
I will stop and ask you to confirm requirements before proceeding; I do not assume missing information.
Can you produce automation code?
Yes — I generate production-ready scripts (e.g., Playwright) and adapt them to the project's existing style and frameworks.
8 skills
This skill helps plan, generate, and execute comprehensive QA test cases and reports strictly from project docs to ensure high-quality software.
This skill helps define product vision, prioritize roadmaps, and validate user needs using JTBD, RICE, and Kano methods.
This skill orchestrates rules and workflows to standardize project context, align with agile practices, and maximize multi-step automation across teams.
This skill helps you craft accessible, brand-aligned UI and design systems, auditing UX and implementing intentional, high-quality visuals.
This skill helps you create and update modular Antigravity agent skills, packaging them for distribution and ensuring compliance with skill standards.
This skill helps optimize React and Next.js performance by applying Vercel's best-practice guidelines across components, pages, data fetching, and bundle
This skill designs and enforces automated, IaC-driven CI/CD, multi-cloud infra, and observability to improve security, reliability, and speed.
This skill guides building production-grade GenAI and agentic systems with robust evaluation, advanced RAG, and scalable MLOps.
