테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing API endpoint tests — integration tests, contract validation, response assertions, mocked external services — even when the user says 'test this route' without naming API testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit one or all supported agent harnesses (claude, codex, opencode, pi, omp, antigravity, cursor, grok) for config efficiency, hook overhead, permission friction, plugin and MCP cost, skill metadata portability, dead config, and measured session friction. Use when invoked as `$optimize-harness [harness ...] [focus]`, or when the user asks to optimize or compare agent harness configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use requesting-code-review for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive QA of a SwiftUI app on a real iPhone over USB - screenshot, read the accessibility tree, inspect @Observable state, tap, swipe, and type through an HTTP bridge embedded in the app under test. Use when asked to test an iOS app on a physical device, find bugs on the device, or expose a connected iPhone to a remote agent over Tailscale. Requires the ios-agent-qa runtime; not for simulator or XCTest work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recreate a worktree for a given PR to test it locally — useful after /implement auto-cleaned the worktree. Usage: /open <PR>
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.