테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Audit an AEM Edge Delivery Services page for content quality, SEO, accessibility, performance, and EDS best practices. Produces a prioritized fix list with specific remediation steps. Use when reviewing page quality, preparing for launch, or optimizing existing content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resize, crop, or export any image or video into platform-ready social media assets using Adobe Creative Cloud tools. Use this skill when a user wants to prepare a photo, image, or video for one or more social platforms — Instagram, TikTok, LinkedIn, Facebook, YouTube, Snapchat, Pinterest, Threads, or X/Twitter. Triggers on: "prepare my image for Instagram", "resize for TikTok", "get this ready to post", "make versions for all platforms", "social media sizes", "crop for stories", "export for LinkedIn", "resize my video for social", "make social media assets", or any request to adapt a photo or video for specific platforms. Handles subject-aware cropping, AI canvas expansion, test previews before full runs, and same-ratio video resizing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan an AEM Edge Delivery Services page for WCAG 2.1 AA accessibility violations and generate specific fixes. Identifies missing alt text, heading hierarchy issues, link text problems, color contrast concerns, and EDS-specific accessibility patterns. Use when fixing accessibility issues, preparing for compliance audits, or remediating WCAG violations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs. Supports extending Core Components and project components. When a Figma design URL is provided, fetches the design via Figma MCP (get_design_context) and translates it into pixel-perfect HTL, CSS, and JS. Follows Adobe Experience League best practices for AEM Cloud Service and 6.5. Use this skill whenever the user mentions creating, building, generating, or scaffolding an AEM component, or mentions component types like teaser, card, hero, banner, accordion, tabs, carousel, list, navigation, breadcrumb, or any custom AEM component. Also trigger when the user wants to extend a Core Component, create a component dialog, add a Sling Model, or convert a Figma design into an AEM component.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browser automation and testing using Playwright MCP server for visual regression, accessibility, route testing, and screenshot capture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage the canary token honeypot system for detecting security scanning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and fix accessibility issues across the portfolio to ensure WCAG 2.1 AA compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, run, and maintain tests using Vitest with proper isolation patterns and coverage targets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement feature flags for gradual rollouts and A/B testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit dependencies for security vulnerabilities, licensing, and maintenance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure Content Security Policy and security headers for the portfolio
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lighthouse audits, bundle analysis, image optimization, font loading, Core Web Vitals tracking, and performance monitoring setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run one bounded adversarial pass when the user explicitly requests a report-style stress test or ROSE identifies a concrete material loophole in an existing strategy, spec, plan, review, or claim; do not trigger for an interactive grill/frontier interview or merely before write-back, implementation, reconciliation, or completion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or materially revise a repository-local test plan, QA plan, acceptance matrix, or regression checklist on explicit request or when one concrete testability gap blocks formal DEFINE; do not trigger for ordinary implementation, test execution, TDD, review, or completion claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a bounded security design/hardening pass for explicit security or threat-model intent, or a concrete auth/authorization/secret/untrusted-input/file-upload/sensitive-data risk; do not trigger for every input, data store, third-party call, implementation, review, or release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clarify a concrete requirements decision, create one bounded static interview packet, or run an explicitly user-invoked frontier batch over a plan, decision, or idea; trigger on explicit grill/interview/refinement intent or a named material ambiguity, not on ordinary planning, implementation, research, test-plan, report-style review, or BUILD work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E2E artifact handling routing. Use when traces, videos, screenshots, reports, or failure bundles need controlled repository-local placement; do not use for simple unit tests or production-mutating E2E flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines raw ideas through structured divergent and convergent thinking for ordinary non-command brainstorming, idea shaping, options comparison, and explicit IDEATE deepening routed by `aili-delivery-flow`; do not use as the top-level `/ideate` command owner or for existing-plan stress-test, review, or completion-claim checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a backend service or an end-to-end frontend/backend integration when service/API/data boundaries are the primary deliverable; do not trigger for pure UI, contract design only, security review, test workflow, or every feature touching both folders.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform direct, bounded browser inspection through the `browser.qa` capability when the user requests runtime UI evidence or one browser-specific claim needs DOM/accessibility/console/network/visual verification; do not trigger for every UI change, backend work, delegated QA, or durable E2E artifact routing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, critique, or specify honest charts and data visualizations from known data and audience needs. Use for chart selection, misleading-chart audits, accessibility, dashboard visuals, or "make this data easier to understand"; do not use for raw data analysis, PPT deck generation, spreadsheet surgery, or fabricated chart data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.