> quality-engineering-quality-assurance
Standards for creating high-quality, granular manual test cases and QA processes. Use when creating manual test cases, defining QA processes, or reviewing test coverage. (triggers: **/*.feature, **/*.test.ts, **/test_plan.md, test case, qa, bug report, testing standard, zephyr, jira ticket, acceptance criteria, test scenario, manual test, !src/**/*.ts, !src/**/*.js, !src/**/*.tsx, !src/**/*.jsx)
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
- High: Critical path, blocker bug.
- Normal: Standard validation, edge case.
- Low: Cosmetic, minor improvement.
4. References
🚫 Anti-Patterns
- Do NOT use standard patterns if specific project rules exist.
- Do NOT ignore error handling or edge cases.
> related_skills --same-repo
> typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)
> typescript-security
Secure coding practices for TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration. (triggers: **/*.ts, **/*.tsx, validate, sanitize, xss, injection, auth, password, secret, token)
> typescript-language
Modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)
> typescript-best-practices
Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)