테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Quando o usuário quer auditar, revisar ou diagnosticar problemas de SEO no seu site. Também use quando o usuário menciona "auditoria de SEO," "SEO técnico," "por que não estou ranqueando," "problemas de SEO," "SEO on-page," "revisão de meta tags," ou "verificação de saúde de SEO." Para construir páginas em escala visando palavras-chave, veja programmatic-seo. Para adicionar dados estruturados, veja schema-markup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quando o usuário quer planejar, projetar ou implementar um teste A/B ou experimento. Também use quando o usuário menciona "teste A/B", "split test", "experimento", "testar essa mudança", "copy variante", "teste multivariado" ou "hipótese". Para implementação de rastreamento, veja analytics-tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gere planos de teste abrangentes, casos de teste manual, suítes de teste de regressão e relatórios de bugs para engenheiros de QA. Inclui integração Figma MCP para validação de design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, or improve a reusable Canvas skill from a concrete workflow. Author a complete organization skill or a new skill inside an existing plugin draft, preserve supporting files, and test the exact published result.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level colour preferences via CSS media queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and fix common accessibility issues in Angular templates and Angular Material components. Use when the user mentions Lighthouse, axe, screen readers, keyboard navigation, ARIA, asks to fix a11y issues in Angular HTML templates, or after any feature, bug fix, or refactor that changed Angular templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a rendered page (resizing the viewport, pressing real keys, capturing and comparing screenshots) rather than only inspecting static markup or a single computed accessibility tree. Covers Reflow risk (SC 1.4.10) and Focus Visible risk (SC 2.4.7) checks. Absolutely always report indicator results separately from confirmed failures. Under no circumstances treat a clean behavioral scan as WCAG conformance, or collapse `cantTell`/test-error/indicator outcomes into a single pass/fail signal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and layered automated + manual testing across all pages and user preferences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit live URLs using Playwright and Axe combined with WCAG skills
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operational readiness checklist (security, cost, legal, data design, performance, incident response, LLM integration defenses) applied when a change touches deployment, infrastructure, external services, secrets, or user data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish or audit an agent-operated repository's quality contract or recurring stewardship friction. Skip routine repairs with a known owner and native check. Use for charter/docs ownership, validation gates, evidence paths, maturity proof, consumer/producer boundaries, command-surface evolution, or a repo ecology pass to decide what should be compressed, merged, retired, or moved to checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.