메뉴
QA and testing reference - test strategy, patterns, coverage, CI/CD integration, and quality metrics. Language-agnostic. Use when designing test strategies, reviewing test quality, setting up CI/CD quality gates, or selecting testing tools.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Testing strategy, patterns, and coverage optimization for quality assurance. Use this skill whenever the task involves deciding what to test, how to structure tests, what coverage to aim for, when to use mocks vs real dependencies, or how to write tests that actually catch bugs (not just pass). Also use when the user asks about test pyramids, flaky tests, integration vs unit, TDD, or improving an existing test suite.
Production readiness validation — runs all checks before merging or deploying. Use this skill whenever the task involves verifying that code is ready to ship: type checking, linting, tests passing, coverage thresholds, dead code, security issues, or any pre-merge checklist. Also use when the user asks "is this ready?", wants a pre-PR review, or needs to confirm nothing is broken after a refactor.
Swift architecture reference — SwiftUI, UIKit, Combine, async/await, actors, and production best practices for Swift 5.9/6.0 (2024-2025). Use when making architectural decisions, reviewing Swift code, or selecting libraries. Also use when the user mentions iOS development, macOS apps, or Apple platform development.
UI/Frontend architecture reference - React 19, Next.js 15, Vue 3, Svelte 5, Angular 19, CSS modern features, component libraries, state management, and production best practices for 2024-2025. Use when building frontend UIs, selecting frameworks, reviewing component code, or making frontend architecture decisions.
UX design reference - research methods, design systems, accessibility (WCAG 2.2, EAA), UX laws, AI-driven workflows, tools (Figma, Penpot), and production best practices for 2024-2025. Use when making UX decisions, reviewing designs, implementing accessibility, selecting design tools, or applying UX principles.
C# architecture reference - frameworks, design patterns, ASP.NET Core, Entity Framework, Blazor, Unity, and production best practices for C# 12/13 and .NET 8/9 (2024-2025). Use when making architectural decisions, reviewing C# code, or selecting libraries.
| name | qa-patterns |
| description | QA and testing reference - test strategy, patterns, coverage, CI/CD integration, and quality metrics. Language-agnostic. Use when designing test strategies, reviewing test quality, setting up CI/CD quality gates, or selecting testing tools. |
| user-invocable | true |
| argument-hint | [frameworks|patterns|architecture|practices|concepts|all] |
Comprehensive language-agnostic reference for testing and quality assurance decisions. Use $ARGUMENTS to focus on a specific area, or browse all sections.
testing, Swift Testing, RSpec (Ruby), NUnit/xUnit (.NET)| Aspect | TDD | BDD | Exploratory |
|---|---|---|---|
| Who writes | Developer | Dev + QA + PO | QA / Tester |
| When | Before code | Before/during feature | After feature |
| Language | Code (assertions) | Gherkin (Given/When/Then) | Session notes |
| Primary value | Design feedback, regression safety | Shared understanding, living docs | Find unexpected bugs |
| Cost | Medium (upfront investment) | High (3-layer translation) | Low (no automation) |
| Best for | Logic-heavy code, APIs | User-facing features, acceptance | Complex UX, edge cases |
| Output | Unit/integration tests | Executable specifications | Bug reports, test charters |
| Level | Description | Key Indicators |
|---|---|---|
| 0 - Ad hoc | No formal testing | Manual testing only, no CI |
| 1 - Reactive | Some unit tests | Tests written after bugs, <30% coverage |
| 2 - Managed | Consistent testing | CI pipeline, >60% coverage, test reviews |
| 3 - Proactive | Quality-first | TDD, >80% coverage, quality gates, mutation testing |
| 4 - Optimized | Continuous improvement | Metrics-driven, chaos engineering, shift-left security |