3.3万 件 ・ 関連度順
Audit and optimize headings across AEM Edge Delivery Services pages for search intent, hierarchy, and consistency. Extracts all headings (H1-H6), evaluates uniqueness, keyword alignment, specificity, and structural correctness, then generates optimized heading suggestions per page. Use when improving on-page SEO, fixing heading hierarchy issues, or standardizing heading patterns across a site.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the migrate-prep cascade — extract --prep → direct --prep → prototype --prep → assets prep — with confirmation gates between phases. Builds the data structure migrate consumes.
日本語の概要は準備中です。原文の説明を表示しています。
AEM Cloud Service expert skill for Sling Scheduler. Routes to path-a.md (Runnable + OSGi properties) or path-b.md (Sling Jobs via JobManager). Covers classification, CS-specific constraints (no @SlingScheduled, multi-pod runOn, Boolean type hint), review checklist, troubleshooting fingerprints, and common pitfalls.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze content sequences and determine authoring approach (default content vs blocks). Validates block selection and section styling for import/migration to AEM Edge Delivery Services.
日本語の概要は準備中です。原文の説明を表示しています。
Apply consistent photo adjustments across a set of images so they look like they were edited together. Use this skill whenever the user says "make my photos look cohesive", "give all these the same style", "apply a warm and golden feel to all of these", "make this cinematic", "match the look across my photos", "edit all my travel photos the same way", "batch edit these", "make these consistent", "fix my phone photos", or uploads a folder of photos and wants a unified, polished result. Also triggers for requests like "apply a preset to all of these", "make these look professional", or "they were shot in mixed lighting — can you fix them all". Outputs direct final image URLs plus an in-chat preview grid and optional Firefly Board link. Access: 🔐 Signed-In required | Gen AI: ❌
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services (EDS) tasks. Use when the user needs to define acceptance criteria, write requirements, scope work, or create a definition of done for EDS blocks, components, variants, bug fixes, or styling changes. Produces task breakdowns, identifies edge cases, and documents analysis for new blocks, variants, behavior modifications, CSS-only changes, and bug fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation and testing using Playwright MCP server for visual regression, accessibility, route testing, and screenshot capture.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch up-to-date, version-specific documentation for any major library (Next.js 16, Sanity, LangGraph, React, Tailwind CSS, Vitest, Framer Motion) via the Context7 MCP server. Use when writing code against unfamiliar or recently-changed framework APIs, when training data may be stale, when resolving deprecations or version-specific syntax, or when the repo warns about framework drift (e.g. the nextjs-agent-rules block in portfolio-v1/AGENTS.md). Invokes the resolve-library-id and get-library-docs MCP tools.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
日本語の概要は準備中です。原文の説明を表示しています。
Manage the canary token honeypot system for detecting security scanning
日本語の概要は準備中です。原文の説明を表示しています。
Creates a new experience document in the Sanity studio. Use when the user wants to add a job, role, internship, or work history entry to the Experience collection.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Review copy, content, and documentation for clarity, consistency, and correctness.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a new certification document in the Sanity studio. Use when the user wants to add a credential, certificate, or professional accreditation to the Certifications collection.
日本語の概要は準備中です。原文の説明を表示しています。
Improve search engine visibility with proper meta tags, structured data, sitemaps, and semantic HTML.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes for correctness, consistency, performance, accessibility, and adherence to repo conventions.
日本語の概要は準備中です。原文の説明を表示しています。
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 project document in the Sanity studio. Use when the user wants to add a new portfolio project, a case study, or a work sample to the Projects collection.
日本語の概要は準備中です。原文の説明を表示しています。
Edits the heroSection singleton in the Sanity studio. Use when the user wants to change the homepage hero copy, name, title, role rotator, or contact email.
日本語の概要は準備中です。原文の説明を表示しています。
Publishes a blog post by marking it as published and syncing to Sanity. Use when the user wants to make a post live on the site.
日本語の概要は準備中です。原文の説明を表示しています。
Provides advanced UI/UX design intelligence for portfolio and app work, including design system selection, palette and typography guidance, and implementation checks.
日本語の概要は準備中です。原文の説明を表示しています。
Audit dependencies for security vulnerabilities, licensing, and maintenance.
日本語の概要は準備中です。原文の説明を表示しています。