cli-create-profile-verifyValidates that "Create profile base" completed successfully. Checks that expected schemas, datasets, merge policies, and segment definitions (audiences) exist in the sandbox. Owns cleanup of those four artifact types only — flows, connections, mapping sets,…cli-data-load-verifyValidates that the "Load profile data" menu option completed successfully. Runs three layers: (1) all dep: flows are enabled via the list endpoint, (2) base connection exists, (3) profile and lookup records are present in the Profile store via…cli-githubHandles all GitHub workflow steps for DEP CLI changes: PR creation with a mandatory versioning and changelog gate, checkpoint evidence, CI monitoring, reviewer comment triage and response, and merge readiness check. Use whenever the user says "create PR",…cli-menuScaffolds the three files needed for a new DEP CLI menu action: the menu.js entry, the action.js file pre-wired to the standard pattern, and the lib function stub. Use whenever the user says "scaffold a new action", "add a menu item", "create a new CLI…cli-review-cycleRuns the full quality gate for DEP CLI changes: simplify → code review → security review → DEP-specific compliance checks → regression checkpoint. Loops until all phases are clean and all acceptance criteria still pass. Use whenever the user says "start…cli-verifyVerifies the current state of the DEP CLI project against acceptance criteria. When a plan file with acceptance criteria is in context, verifies its numbered criteria. When invoked standalone (no plan), traces changed files from git, groups affected actions…
explorador de repositórios
adobe · Repositórios e skills representativas - Página 2
Visão por repositório de 380 skills coletadas em 23 repositórios do GitHub.
apply-api-specReads a feature spec, locates the matching API spec, reads the project's backend service cards, and produces a Low Level Design (LLD) document describing all the backend implementation changes needed. Does not write code — outputs a structured engineering…apply-experience-cardReads an experience card, optionally fetches the Figma design if a URL is defined in the card, reads the project's UI service cards, and produces a Low Level Design (LLD) document describing all UI implementation changes an engineer needs to make. Does not…generate-ui-service-cardGenerate a complete UI Service Card set for any application by reading its codebase. Produces all 7 card files (UI_SERVICE_CARD, UI_MODULE_INDEX, ROUTES, DATA_LAYER, STATE_MANAGEMENT, UI_CODE_PATTERNS, UI_PLATFORM) filled with real project values. Works with…implement-featureExecutes a pre-written LLD by reading the target repo's service cards for coding conventions, then writing all files specified in the LLD. Supports backend-only, UI-only, or full-stack generation via an optional mode argument. The LLD defines WHAT to build;…verify-featureAudits a generated feature implementation against its LLD — checking every file in the Change Summary table, every bullet in every Change Required cell, wiring between frontend and backend, and experience card acceptance criteria. Read-only. Reports pass /…
commerce-app-storageIntegrate App Builder Database Storage (@adobe/aio-lib-db) into an Adobe Commerce app and scaffold a runtime action that reads and writes documents. Use when the user wants persistent, queryable storage backing a Commerce app — either from a web action…commerce-app-eventingAdd or modify Commerce and external event subscriptions, configure event field extraction and filter rules in an Adobe Commerce app. Use when the user wants to set up event-driven workflows triggered by Commerce operations (such as order placement or catalog…commerce-app-webhooksAdd or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.commerce-app-initScaffold a new Adobe Commerce app using the aio-commerce-sdk. Creates the base project structure and app.commerce.config file with metadata. Use when the user wants to create a new Commerce app from scratch or initialize a bare Commerce app project. After…
documentationWrite, edit, or restructure content in this repository harnesses guide. Use when adding, updating, or reviewing any of the nine numbered chapters (01–09) or the companion materials (`guide/README.md`, `guide/READING.md`, `guide/FAQ.md`).guide-reviewReview a multi-chapter guide, series, or book from six specialist perspectives. Orchestrates Series Editor, Non-Technical Proxy, Practitioner Proxy, Consistency Auditor, Diagram Reviewer, and Claims Auditor. Use for single-chapter review, full-series audit,…harness-inspectAudit an existing harness for rot, gaps, and improvement opportunities. Use monthly (health check, quick pass) or quarterly (full audit, thorough assessment), and after any agent incident, major refactor, or structural change.harness-setupBuild or extend a repository harness. Understands the repo first, then determines what to build, migrate, or create based on what exists.
aio-telemetry-instrumentInteractive guide for adding telemetry instrumentation to an Adobe App Builder runtime action using @adobe/aio-lib-telemetry. Use when the user wants to: (1) decide what to instrument inside a runtime action, (2) add child spans with instrument() to trace…aio-telemetry-setupInteractive setup guide for adding OpenTelemetry observability to Adobe App Builder runtime actions using @adobe/aio-lib-telemetry. Use when the user wants to: (1) add telemetry/observability to an App Builder action, (2) instrument runtime actions with…aio-telemetry-troubleshootingInteractive troubleshooting for @adobe/aio-lib-telemetry issues in Adobe App Builder runtime actions. Use when a user reports: (1) telemetry not working, no data showing up, (2) missing traces, metrics, or logs, (3) broken distributed traces or disconnected…
code-reviewReview code for AEM Edge Delivery Services projects. Use for self-review before committing, or to review pull requests with one-click GitHub suggestions.tool-image-promptGenerate Adobe Firefly image prompts for AEM tools website (tools.aem.live) tool card thumbnails. Use when creating or updating thumbnail images for tools, or when a new tool needs a card image. Triggers on requests like "create an image for the X tool",…
ffcpe-app-builder-actionsDescribes how to implement FFCPE (Firefly Creative Production for Enterprise) custom-action web and worker OpenWhisk actions using @adobe/ffcpe-custom-node-core and @adobe/ffcpe-custom-node-app-builder (Hono, mountFfcpeNodeRoutes, createFfcpeNodeWorker,…ffcpe-custom-node-sdkHelps Adobe App Builder developers build FFCPE (Firefly Creative Production for Enterprise) custom actions using @adobe/ffcpe-custom-node-core and @adobe/ffcpe-custom-node-app-builder (OpenWhisk web + worker actions, Hono, submit/status HTTP contract,…
aio-ffcpe-cliUse when working with the Adobe I/O CLI plugin @adobe/aio-cli-plugin-ffcpe (FFCPE — Firefly Creative Production for Enterprise). Covers installation, authentication, env overrides, and all `aio ffcpe catalog` commands. Use for terminal workflows, scripting…ffcpe-catalog-entry-jsonUse when authoring or validating an FFCPE (Firefly Creative Production for Enterprise) custom-action catalog-entry.json for the run-workflow service (App Builder actions). Covers installing the Adobe I/O CLI and this plugin, schema shape, org/auth, agent…