307건(HoangNguyen0403의 저장소) · 인기순
Test React Native components with Jest and React Native Testing Library. Use when writing Jest or React Native Testing Library tests for React Native components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Red Team persona for Business Logic and Auth manipulation. Generates and executes stateful fuzzing scripts (Playwright/Python) to test RBAC bypasses, BOLA/IDOR, race conditions, and complex multi-step transaction flaws.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize React rendering, bundle size, and data flow with profiler-led decisions. Use when reducing re-renders, fixing waterfalls, or deciding whether memoization is warranted in React.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design Python error paths with narrow exceptions, rollback, contextual logs, and preserved blocker truth. Use when handling retries, verifier outcomes, parser failures, or exception flow in Python services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure Python backends with explicit dependency direction, ports/adapters, and runtime boundaries. Use when shaping project layout, clean architecture, service boundaries, dependency injection, report rendering boundaries, or transport separation in Python.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Secure Python services against secret leakage, injection, unsafe subprocess calls, and dependency drift. Use when handling env vars, tokens, SQL, file paths, shell commands, auth flows, or Python security gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement Python database access with parameterized SQL, transaction scope, connection helpers, and repository seams. Use when editing Postgres queries, repositories, transactions, pooling, or persistence boundaries in Python.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drives iOS/Android mobile devices via Appium MCP. Runs a preflight, picks local emulator/simulator/USB or a device cloud, captures screenshots/page source into a named evidence dir. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure React Native projects with feature-first organization and separation of concerns. Use when structuring a React Native project or applying clean architecture patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure Python tooling, dependency surfaces, static analysis, and verification gates. Use when editing `pyproject.toml`, `requirements.txt`, `pytest.ini`, `ruff`, `pyright`, CI, or Python release checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write maintainable Python with small functions, explicit boundaries, guard clauses, and readable state flow. Use when refactoring Python services, helpers, modules, or async logic for clarity—not generic test writing, tooling setup, or database transaction implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build modern React Native components using function components and composition. Use when building or refactoring React Native function components and composable UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverage_analysis_report.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation — use zephyr-test-generation instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Secure token storage (HttpOnly Cookies) and Middleware patterns. Use when implementing authentication, secure session storage, or auth middleware in Next.js.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-stack selector and test-id policy for web and mobile automation. Use when writing or reviewing E2E/UI test locators, or adding data-testid/accessibility identifiers to components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Captures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write PHP following PSR coding standards, SOLID principles, and code-quality guidelines. Use for PHP style, design, refactoring, naming, and guard clauses—not Composer/PSR-4 project configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Next.js version migrations using official guides and codemods. Use when migrating a Next.js project to a new major version using codemods.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PHP-only security standards for database access, password handling, and input validation. Use when securing PHP apps against SQL injection, XSS, or weak password storage; defer Laravel middleware and security questions in other languages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.