2.5万 件 ・ 関連度順
Authenticate with AEM Edge Delivery Services. Opens browser for login and captures token. Works for admin.hlx.page and Config Service APIs regardless of content source (Document Authoring, SharePoint, or Google Drive).
日本語の概要は準備中です。原文の説明を表示しています。
AEM Cloud Service expert skill for the Asset Manager API (com.day.cq.dam.api.AssetManager). Covers two migration paths — Path A (create/upload, replacing createAssetForBinary/getAssetForBinary/client-facing createAsset with Direct Binary Access via @adobe/aem-upload) and Path B (delete, replacing removeAssetForBinary with in-JVM resolver.delete() + commit or external HTTP Assets API with IMS bearer tokens). Covers IMS authentication, service-user setup with crx delete permissions, asset processing pipeline, common pitfalls (hardcoded credentials, AEM calling its own HTTP API), and composition with replication/event-migration skills.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate multi-step tasks across multiple skills for complex workflows.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare an explicit production launch, staged rollout, launch-monitoring, or rollback plan; do not trigger from AILI SHIP, implementation completion, packaging, review, or release wording that lacks a concrete launch/rollout target.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and synthesize a source-grounded multi-paper literature review. Use for systematic literature reviews, survey matrices, inclusion/exclusion criteria, research gaps, or "review the literature on X" requests; do not use for reviewing one paper, ordinary web summaries, citation formatting only, or medical/legal conclusions.
日本語の概要は準備中です。原文の説明を表示しています。
Create or materially revise a durable specification when the user explicitly requests a spec/new feature contract or a named ambiguity requires formal DEFINE; do not trigger for ordinary bounded edits, implementation, task breakdown alone, review, or documentation of already-settled behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve one exact official/current documentation gap when the user requests source verification or a version-sensitive API/SDK/provider/framework question can materially change the current decision; do not trigger for every implementation decision, ordinary framework code, local business logic, or broad research.
日本語の概要は準備中です。原文の説明を表示しています。
AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Implement an accepted change in bounded dependency-ordered increments when the user requests implementation and the scope benefits from multiple coherent slices; do not trigger merely because work touches multiple files, changes behavior, or is over an arbitrary line count.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Configure or diagnose project context, rules files, context packs, or documented context degradation when explicitly requested; do not trigger automatically at session start, task switching, ordinary repository exploration, implementation, or completion.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.
日本語の概要は準備中です。原文の説明を表示しています。
Configure or modify concrete CI/CD pipelines, jobs, quality gates, test runners, or deployment automation; do not trigger merely because an existing CI gate failed or ordinary source code needs repair.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, fill, or template-format editable Word/DOCX documents with managed OfficeCLI first and OpenXML fallback for complex or preservation-sensitive work.
日本語の概要は準備中です。原文の説明を表示しています。
Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns. Provides state machine approach recommendations, loading skeletons, error boundaries, and empty state components. Use when implementing "loading states", "error handling", "empty states", or "state machines".
日本語の概要は準備中です。原文の説明を表示しています。
Identifies performance bottlenecks and provides ordered scaling strategies with triggers, phased plans, and cost implications. Use for "scalability planning", "performance bottlenecks", "capacity planning", or "growth strategy".
日本語の概要は準備中です。原文の説明を表示しています。
Audits database schemas for naming conventions, type consistency, nullability patterns, and missing constraints. Provides violations report with recommended fixes. Use for "schema validation", "database linting", "schema standards", or "consistency checks".
日本語の概要は準備中です。原文の説明を表示しています。
Detects leaked API keys, tokens, passwords, and credentials in code with pre-commit hooks, CI checks, scanning rules, and remediation procedures. Use for "secret scanning", "credential detection", "API key leaks", or "secret management".
日本語の概要は準備中です。原文の説明を表示しています。
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.
日本語の概要は準備中です。原文の説明を表示しています。
Migrates TypeScript projects to strict mode incrementally with type guards, utility types, and best practices. Use when users request "TypeScript strict", "strict mode migration", "type safety", "strict TypeScript", or "ts-strict".
日本語の概要は準備中です。原文の説明を表示しています。
Implements comprehensive observability with OpenTelemetry tracing, Prometheus metrics, and structured logging. Includes instrumentation plans, sample dashboards, and alert candidates. Use for "observability", "monitoring", "tracing", or "metrics".
日本語の概要は準備中です。原文の説明を表示しています。