> quality-engineering-quality-assurance
Write manual test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use when writing or reviewing manual test cases for Zephyr — to split compound TCs, fix naming violations, assign correct platform tags, or determine bug priority. (triggers: test case, manual test, zephyr, test scenario, naming convention, acceptance criteria)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/quality-engineering-quality-assurance?format=md"Quality Assurance Standards
Priority: P1 (HIGH)
1. Test Case Granularity
- 1 Test Case = 1 Condition on 1 Screen.
- Split Screens: "Order Details" & "Item Details" are separate.
- Split Conditions: "Config A" & "Config B" are separate.
- No "OR" Logic: Each TC must test a single, distinct path.
2. Naming Convention
- Pattern:
([Platform]) [Module]_[Action] on [Screen] when [Condition] - Rule: Only include
[Platform]if requirement is exclusive to one platform (e.g.,[Mobile]). Omit if it supports Both. - Example:
Order_Verify payment term on Item Details when Toggle is OFF(Supports Both)
3. Priority Levels
Use priority rationale to justify each classification:
- High: Critical path, blocker bug.
- Normal: Standard validation, edge case.
- Low: Cosmetic, minor improvement.
4. References
Anti-Patterns
- ❌
"Verify order flow works"— too broad; every TC must cover exactly 1 condition on 1 screen - ❌ Testing Web and Mobile behavior in a single TC when behavior diverges — split into separate TCs per platform
- ❌
Order_Verify page— name must follow the full pattern:Module_Action on Screen when Condition - ❌ Marking a cosmetic spacing bug as High priority — reserve High for critical path blockers only
> related_skills --same-repo
> common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app. (triggers: generate changelog, app store notes, play store release, what's new, release notes, ve
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)