9.4万 件 ・ 関連度順
概要と使いどころ
Compare two versions of an AEM Edge Delivery Services page to identify what changed. Fetches preview vs live, or two different URLs, and produces a detailed content diff showing added, removed, and modified content, metadata, and blocks. Use when reviewing changes before publishing, auditing content modifications, or tracking content evolution.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes a multi-step conversion funnel to find where visitors drop off and which steps have the worst leakage. Use this skill when someone describes a journey and asks about conversion rates, drop-off, fallout, or step completion. Trigger for "analyze our checkout funnel," "where are visitors dropping off," "what's our add-to-cart to purchase conversion rate," "funnel analysis," "show me fallout between steps," or "which step loses the most visitors."
日本語の概要は準備中です。原文の説明を表示しています。
Write and review component documentation (MDX) and registry descriptions. Covers doc structure, description writing, Features, Composition, Credits, and References sections. Use when creating new component docs, updating descriptions, adding Features sections, adding Composition sections, adding Credits sections, adding References sections, or reviewing component documentation quality.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a new blog post document in the Sanity studio. Use when the user wants to write a blog post, publish an article, or schedule a future post.
日本語の概要は準備中です。原文の説明を表示しています。
Service worker management, offline support, cache strategies, and SW debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Optimized workflows for OpenCode IDE with MiMo v2.5 free model
日本語の概要は準備中です。原文の説明を表示しています。
Provides advanced UI/UX design intelligence for portfolio and app work, including design system selection, palette and typography guidance, and implementation checks.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement webhooks for event-driven architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Build beautiful, responsive, accessible UIs using React, Tailwind CSS, Framer Motion, and the Vercel Web Interface Guidelines.
日本語の概要は準備中です。原文の説明を表示しています。
Quick repo-hygiene and consistency checks before committing.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging workflow for errors, performance issues, and runtime problems in the portfolio.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, analyze, format, or validate Excel/XLSX/CSV spreadsheets with managed OfficeCLI first and pandas/XML preservation-aware fallbacks.
日本語の概要は準備中です。原文の説明を表示しています。
Create, fill, or reformat print-ready PDFs with strong visual page fidelity.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, fill, or template-format editable Word/DOCX documents with managed OfficeCLI first and OpenXML fallback for complex or preservation-sensitive 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.
日本語の概要は準備中です。原文の説明を表示しています。
将已有中文论文正文、报告、邮件、说明或 PPT 文案改得自然、减少 AI 腔与模板感；用于明确的“说人话”、自然化改写或论文 AIGC 风险段落处理，不用于自动润色所有回答、从零代写论文、英文改写、概念教学、事实核查、检测分数保证或 PPTX 文件生成。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify production UI components, layouts, client state, responsive behavior, accessibility, or UX inside an app when that frontend surface is the primary deliverable; do not trigger for rich campaign/media pages, backend integration, every user-facing text change, delegated browser QA, or review alone.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct one bounded evidence-grounded code review when the user explicitly requests review or ROSE names a concrete unresolved correctness/quality risk; do not trigger automatically after implementation, before every merge, for every bug fix/refactor, or as a completion gate.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.
日本語の概要は準備中です。原文の説明を表示しています。