테스트 설계, 취약점 진단, 품질 보증 (1.4만건)
Fallback local Playwright daemon for real-browser visual QA / screenshots / smoke. Use ONLY when the host platform has no native browser mode — prefer the host browser first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before any deployment or completion claim. Enforces test gates, evidence-based verification, and frontend safety checks. No deploy without passing. No claims without evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix. Routes to the core Red-Green-Refactor loop, test quality guidance, rationalization handling, examples, or stuck-state recovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safe i18n: multi-pass batching, parallel-per-language dispatch, 8 audit gates, HTML integrity. Use for translating or mass-converting hardcoded strings to t() calls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Working memory protocol — routes to session protocol, memory audit, MCP/URI integration, or storage details based on the current need. Keeps default continuity usage cheap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use to run the full sprint pipeline: brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap any new project: identity, design system, staging+production, i18n, SEO, test infrastructure, 8-gate deploy pipeline. Prevents tech debt from day 0.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Laravel 13 best practices: architecture, Eloquent, security, queues, testing, tooling. PHP 8.3+. Use when writing or reviewing Laravel applications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic Go 1.25 practices: errors, interfaces, concurrency, generics, testing, security, tooling. Use when writing or reviewing Go code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modern PHP 8.5 practices: type system, OOP, security, architecture, async, testing, tooling. Use when writing or reviewing PHP code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Development workflows for WordPress ATmosphere plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, or working with wp-env.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing patterns for PHPUnit tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ATmosphere features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting a session and suspecting configuration issues, after hook failures, MCP connection errors, or degraded vault performance. Also useful as a periodic health audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when running a validated local Shipfox workflow change against a real trigger and inspecting its effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evaluating, comparing, installing, or recommending a Claude Code plugin, Agent Skill, MCP server, agent toolkit, or GitHub-hosted AI extension, especially when popularity is weak evidence or the candidate requests shell, network, filesystem, or credential access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before publishing documentation, merging a docs PR, or reporting a Markdown-heavy repo's navigation as complete — when you want ground-truth confirmation that internal links, heading anchors, and directory links resolve, without opening every file yourself.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during periodic cleanup of an accumulated skills directory, or when asked to review skill quality — checks frontmatter validity, description quality against Skill Discovery Optimization conventions, body size, and cross-scope name collisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Behavior-first test guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Practice test-driven development for new features and bug fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a branch or PR for merge readiness and produce a QA report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define, review, or update SECURITY.md guidance for a repository or component. Use when the user wants to clarify what Codex Security should review, what is out of scope, which security properties must hold, or whether existing guidance still matches the code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.