← all publishers

Adobe

@adobe source repo

Report this profile Claim this profile

• 314 skills
• 0 followers
• 142 repo stars
• 204 verified
• last week last updated

1. ▌
   Build Service Database 2 · adobe

   Build a feature's ecs service-database — db-bound service factories. If the feature exposes services.
   142 repo stars
2. ▌
   Aio Ffcpe CLI · adobe

   Use 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 catalog changes, or explaining how developers should invoke this plugin. Some users still say **Workflow Builder**; that name referred to the same product area — the CLI topic is **`ffcpe`** (`aio ffcpe`).
   142 repo stars
3. ▌
   Ffcpe Catalog Entry JSON · adobe

   Use 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 discovery, customActionConfig, validation, workflow usage, and troubleshooting. Use **`aio ffcpe catalog`** to validate/register—never raw curl. Older searches may say **Workflow Builder**; same plugin and topic **`ffcpe`**.
   142 repo stars
4. ▌
   Ffcpe Custom Node Sdk · adobe bundle

   Helps 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, inputs/outputs, IMS-aware routes). Use when the user is wiring a custom-action app in App Builder, implementing FfcpeNodeWorkerHandler, mounting routes with mountFfcpeNodeRoutes, configuring web: raw OpenWhisk actions, debugging submit/statusUrl polling, handling Text/Image/Video/Json inputs, or producing action outputs for run-workflow. For catalog-entry.json and aio ffcpe catalog CLI, use companion skills from adobe/aio-cli-plugin-ffcpe.
   142 repo stars
5. ▌
   Ffcpe App Builder Actions · adobe

   Describes 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, submit/status contract). Describes adding actions to existing Adobe App Builder repos: co-located <action-name>.web|worker|entry files, *.config.yaml updates, and webpack + esbuild-loader partial for TypeScript with CommonJS output. Use when scaffolding or migrating FFCPE web/worker pairs, fixing ext.config.yaml / runtimeManifest, or debugging hono-openwhisk-adapter web actions (web: raw). After deploy, use aio ffcpe catalog with co-located <action-name>.entry.json (skills in adobe/aio-cli-plugin-ffcpe) to register the action.
   142 repo stars
6. ▌
   Tool Image Prompt · adobe bundle

   Generate 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", "generate a tool thumbnail", "make a Firefly prompt for this tool".
   142 repo stars
7. ▌
   Aio Telemetry Setup · adobe bundle

   Interactive 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 traces, metrics, or logs, (3) configure an observability backend (Grafana, New Relic, Datadog, etc.) for App Builder, (4) set up distributed tracing across actions, (5) add Commerce event/webhook integrations, or (6) understand how to setup @adobe/aio-lib-telemetry. Triggers on: "add telemetry", "instrument my action", "set up tracing", "configure observability", "export traces/metrics/logs", "OpenTelemetry for App Builder".
   142 repo stars
8. ▌
   Aio Telemetry Instrument · adobe bundle

   Interactive 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 internal functions, (3) add custom metrics with defineMetrics(), (4) add span attributes or events to enrich traces, (5) add structured logging correlated with traces, (6) choose between traces, metrics, and logs for an observability goal, (7) instrument outbound HTTP calls or cross-action propagation, or (8) get a guided assessment of what telemetry to add to a specific action. Prerequisite: general telemetry setup done (library installed, defineTelemetryConfig defined). Per-action steps like instrumentEntrypoint and ENABLE_TELEMETRY can be handled here. Triggers on: "instrument this action", "what should I trace", "add spans", "add metrics to my action", "what should I observe", "help me instrument", "add logging", "instrument my function".
   142 repo stars
9. ▌
   Aio Telemetry Troubleshooting · adobe bundle

   Interactive 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 spans, (4) errors from the telemetry library, (5) "works locally but not in production" issues, (6) backend-specific problems (New Relic, Grafana, etc.), (7) hot reload / dev mode telemetry issues, (8) configuration validation or review, or (9) any unexpected behavior related to @adobe/aio-lib-telemetry. Triggers on: "telemetry not working", "no traces", "missing spans", "export failed", "telemetry error", "debug telemetry", "traces not showing", "broken traces", "check my config", "validate configuration".
   142 repo stars
10. ▌
    Guide Review · adobe bundle

    Review 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, consistency checks, diagram audits, and claims audits.
    142 repo stars
11. ▌
    Documentation · adobe

    Write, 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`).
    142 repo stars
12. ▌
    Harness Setup · adobe bundle

    Build or extend a repository harness. Understands the repo first, then determines what to build, migrate, or create based on what exists.
    142 repo stars
13. ▌
    Harness Inspect · adobe bundle

    Audit 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.
    142 repo stars
14. ▌
    Enhance Sync Pr · adobe

    Enhances auto-generated spectrum-design-data PRs from spectrum-tokens-studio-data sync (branch tokens-sync/patch-spectrum2-from-main, author mrcjhicks). Diagnoses CI failures, suggests fixes, creates changesets with token-changeset-generator, updates PR title/body, and attributes the original Tokens Studio implementer. Use when fixing sync PRs, PRs from tokens-sync, enhance-sync-pr workflow gaps, or missing changesets on studio syncs.
    142 repo stars
15. ▌
    S2 Docs · adobe bundle

    Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField, ActionButton, etc.). Helps prevent drift from documented S2 design decisions during prototyping.
    142 repo stars
16. ▌
    Design Data · adobe

    Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum. Use when the user asks about token values, component options, naming conventions, or wants to validate/explore design-token data. Also triggers when a .design-data.toml config is involved or the user mentions the design-data CLI.
    142 repo stars
17. ▌
    Design Data Agent · adobe

    Validate, query, resolve, diff, and author spec-conformant design tokens and components using the design-data MCP tools against a local dataset. Use when the user asks about design tokens, a design system, token lookup, spec-conformance, drift detection, or token authoring on custom data.
    142 repo stars
18. ▌
    Lint · adobe

    Fix code style issues and ensure linting CI gates pass in S3Mock. Use when ktlint or Checkstyle violations are reported, when asked to fix formatting, or as a required final step after any code change. Runs ktlint for Kotlin source files and Checkstyle for Java and XML files.
    142 repo stars
19. ▌
    Test · adobe

    Write, update, and fix tests in S3Mock. Use when asked to add test coverage, create test cases, fix failing tests, or verify test correctness. Covers unit tests (*Test.kt in server/), controller slice tests (@WebMvcTest), and integration tests (*IT.kt in integration-tests/ against a live Docker container).
    142 repo stars
20. ▌
    Document · adobe

    Generate and update S3Mock project documentation. Use when asked to document code, update CHANGELOG.md, update README.md, update AGENTS.md files, or fix formatting, wording, or style in any existing documentation file. Also invoked at the end of the implement skill workflow.
    142 repo stars
21. ▌
    Refactor · adobe

    Improve code readability, enforce idiomatic Kotlin conventions, and enhance documentation quality in S3Mock without changing behavior. Use when asked to clean up code, improve naming, add KDoc, or align with Kotlin/project idioms. Also invoked by the implement and test skills before adding new code to messy areas.
    142 repo stars
22. ▌
    Implement · adobe

    Implement features, fix bugs, and modify production source code in S3Mock. Use when asked to add functionality, change behavior, or modify source files in server/, integration-tests/, or testsupport/. Not for documentation-only or test-only changes. Orchestrates lint, test, and document skills as part of the complete workflow.
    142 repo stars
23. ▌
    Commerce App Init · adobe bundle

    Scaffold 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 scaffolding, chains to appbuilder-project-init for Developer Console setup (project, workspace, API subscriptions) when the user wants to deploy. Does not configure extensibility domains — use commerce-app-eventing, commerce-app-webhooks, commerce-app-business-config, commerce-app-admin-ui, or commerce-app-storage for that.
    142 repo stars
24. ▌
    Commerce App Migrate · adobe bundle

    Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
    142 repo stars
25. ▌
    Commerce App Storage · adobe bundle

    Integrate 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 (HTTP-invokable) or from an event/webhook handler. Requires a base app initialized with commerce-app-init.
    142 repo stars
26. ▌
    Commerce App Admin UI · adobe bundle

    Add or modify Adobe Commerce Admin UI extensions on the commerce/backend-ui/2 extension point: custom grid columns, mass actions, order view buttons, a custom Admin menu entry, and custom ACL resources. Use whenever the user wants to extend the Commerce Admin — add a column to the order, product, or customer grid, add a bulk/mass action to a grid, add a button to the order view page, add a custom menu item or page, or declare custom permissions the app checks itself — even when they don't name the extension point.
    142 repo stars
27. ▌
    Commerce App Eventing · adobe bundle

    Add 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 changes) or third-party systems. Requires a base app initialized with commerce-app-init.
    142 repo stars
28. ▌
    Commerce App Webhooks · adobe bundle

    Add 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.
    142 repo stars
29. ▌
    Commerce App Business Config · adobe bundle

    Manage custom business configuration in an Adobe Commerce app. Use when the user wants to add, modify, or remove merchant-configurable settings (config fields, admin config, store configuration) exposed through Commerce Admin. Creates typed config fields (text, password, email, url, tel, boolean, list) in businessConfig.schema. Requires a base app initialized with commerce-app-init.
    142 repo stars
30. ▌
    Jira Ticket · adobe

    Guidelines for drafting and formatting Jira tickets
    142 repo stars
31. ▌
    Explain Code · adobe

    Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
    142 repo stars
32. ▌
    Token Update · adobe

    Dispatches to the correct design token update workflow (custom tokens only vs @adobe/spectrum-tokens version bump). Use whenever asked to update, bump, or upgrade design tokens, or when told to run a token update.
    142 repo stars
33. ▌
    Ask Questions If Underspecified · adobe

    Clarify requirements before implementing. Use when serious doubts arise.
    142 repo stars
34. ▌
    Documentation Standards · adobe

    When writing documentation in a variety of scenarios, follow the Adobe content writing standards.
    142 repo stars
35. ▌
    Migration API · adobe

    Phase 3 of 1st-gen to 2nd-gen component migration. Use to move properties, methods, and types from 1st-gen to 2nd-gen while maintaining a clear public API.
    142 repo stars
36. ▌
    Vrt Authoring · adobe

    Author dedicated Storybook visual regression stories for 2nd-gen components. Use when adding or reviewing `.vrt.ts` files, Chromatic VRT coverage, forced-colors coverage, pseudo-state snapshots, global stylesheet coverage, or custom-property VRT coverage.
    142 repo stars
37. ▌
    Migration A11Y · adobe

    Phase 4 of 1st-gen to 2nd-gen component migration. Use to implement WCAG-aligned semantics, ARIA, keyboard support, and focus management, and document accessibility behavior.
    142 repo stars
38. ▌
    Migration Prep · adobe bundle

    Phase 1 of 1st-gen to 2nd-gen component migration. Use to understand the component, plan breaking changes, and define scope before any refactoring begins.
    142 repo stars
39. ▌
    Migration Setup · adobe

    Phase 2 of 1st-gen to 2nd-gen component migration. Use to create the 2nd-gen file and folder structure, wire up exports, and confirm the build passes before implementation begins.
    142 repo stars
40. ▌
    Session Handoff · adobe bundle

    Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
    142 repo stars
41. ▌
    Code Conformance · adobe

    Review 2nd-gen component files against project style guides, run linters, and surface guideline gaps. Apply whenever reviewing or auditing 2nd-gen component code for style conformance.
    142 repo stars
42. ▌
    Consistency Pass · adobe

    Defines when and how to run a consistency and validity self-audit on changed files and the migration plan. Apply before declaring any migration phase or significant implementation task complete.
    142 repo stars
43. ▌
    Migration Review · adobe

    Phase 8 of 1st-gen to 2nd-gen component migration. Use to run final checks, verify lint/tests/build/Storybook, update the workstream status table, and open a PR.
    142 repo stars
44. ▌
    Migration Styling · adobe bundle

    Phase 5 of 1st-gen to 2nd-gen component migration. Use to migrate CSS to the 2nd-gen structure, apply Spectrum 2 tokens, and ensure stylelint passes.
    142 repo stars
45. ▌
    Migration Testing · adobe

    Phase 6 of 1st-gen to 2nd-gen component migration. Use to write unit tests, accessibility tests, and Storybook play functions for a migrated component.
    142 repo stars
46. ▌
    Deep Understanding · adobe

    Require a thorough deep-read of the relevant codebase before planning or implementing; write findings to a persistent markdown file (e.g. research.md) so the user can review and correct before any work proceeds.
    142 repo stars
47. ▌
    Github Description · adobe

    Generates GitHub pull request and issue descriptions — title, labels, and body — following Spectrum Web Components conventions. Prompts for a linked ticket if none is provided.
    142 repo stars
48. ▌
    Contributor Docs Nav · adobe bundle

    Run the CONTRIBUTOR-DOCS nav script to update breadcrumbs and TOCs, and handle link verification. Use when updating contributor docs structure, regenerating navigation, or fixing broken links.
    142 repo stars
49. ▌
    Conventional Commit · adobe

    Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
    142 repo stars
50. ▌
    Migration Conformance · adobe

    Sub-task after Phase 6 of 1st-gen to 2nd-gen component migration. Use to verify all migrated files conform to the project style guides, run linters, and surface any guideline gaps as PR comment notes.
    142 repo stars
51. ▌
    Session Retrospective · adobe

    Document lessons learned after completing work, especially when the user corrected planning documents or implementation. Creates and maintains a persistent lessons file in .ai/memory/ that future agents read at session start.
    142 repo stars
52. ▌
    Migration Documentation · adobe

    Phase 7 of 1st-gen to 2nd-gen component migration. Use to author the per-component MDX docs page and finalize Storybook stories so the component is usable and understandable by others.
    142 repo stars
53. ▌
    Test Driven Development · adobe bundle

    Use when implementing any feature or bugfix, before writing implementation code
    142 repo stars
54. ▌
    Accessibility Compliance · adobe bundle

    Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
    142 repo stars
55. ▌
    Consumer Migration Guide · adobe bundle

    Use when creating a per-component migration guide for application developers upgrading from Spectrum 1 Web Components to Spectrum 2 components.
    142 repo stars
56. ▌
    Migration Phase Awareness · adobe

    Keeps multi-phase migration obligations in context during a session. Emits Migration Checkpoint blocks at phase completion for cross-session continuity. Apply whenever any migration-* skill is active or migration files are being edited.
    142 repo stars
57. ▌
    Spectrum Web Components · adobe

    Build UIs with Spectrum Web Components (SWC), Adobe's Spectrum 1 web component library. Use when developers are working with @spectrum-web-components/* packages or sp-* custom elements. Includes component API references, usage examples, accessibility guidance, and integration guides.
    142 repo stars
58. ▌
    Component Migration Analysis · adobe bundle

    Create rendering-and-styling migration analysis docs for 2nd-gen component migration. Use when on the "analyze rendering and styling" step for one or more components.
    142 repo stars
59. ▌
    Migrate Swc Gen1 To Gen2 · adobe

    Upgrade Spectrum 1 (sp-* elements, @spectrum-web-components/*) to Spectrum 2 (swc-* elements, @adobe/spectrum-wc). Use when developers need to migrate from Spectrum 1 to Spectrum 2 web components, or when they mention @spectrum-web-components, sp-* elements, or Spectrum 1.
    142 repo stars
60. ▌
    Accessibility Migration Analysis · adobe

    Create accessibility migration analysis docs for 2nd-gen component migration. Use when on the "analyze accessibility" step for one or more components.
    142 repo stars
61. ▌
    Clone New Component Epic · adobe

    Clones the SWC-2164 component migration epic template and all 7 child stories into new Jira issues, replacing all [COMPONENT] placeholders with the target component name. TRIGGER whenever a user asks to create a new component epic, clone the new component template, scaffold a new component epic in Jira, or says anything like "set up new component tickets for [component]", "create the new component epic for [component]", or "clone 2164 for [component]". Requires the component name as input — always ask for it if not provided.
    142 repo stars
62. ▌
    Clone Gen2 Migration Epic · adobe

    Clones the SWC-1727 component migration epic template and all 7 child stories into new Jira issues, replacing all [COMPONENT] placeholders with the target component name. TRIGGER whenever a user asks to create a new component migration epic, clone the migration template, scaffold a new component migration in Jira, or says anything like "set up migration tickets for [component]", "create the migration epic for [component]", or "clone 1727 for [component]". Requires the component name as input — always ask for it if not provided.
    142 repo stars
63. ▌
    Think · adobe

    Reflective Thought Composition. Structured thinking pipeline for complex decisions, design evaluation, and deep analysis. Use when quality of reasoning matters more than speed of response.
    142 repo stars
64. ▌
    Performance · adobe

    Use when optimizing a hot path in @adobe/data — especially when an interface (Column, TypedBuffer, ManagedArray, etc.) has many concrete instances created from closure-returning factories and is dispatched from a tight per-row loop. Provides the closure→class refactor pattern, the V8 hidden-class reasoning behind it, accept/reject criteria, and the discipline that keeps the public API closure-free even when implementations are class-based.
    142 repo stars
65. ▌
    X Log · adobe

    logs all named inputs to chat
    142 repo stars
66. ▌
    Review · adobe

    Review built feature/application output against the @adobe/data feature rules; report whether it is optimal and where any fix belongs. Read-only.
    142 repo stars
67. ▌
    X Trace · adobe

    inserts a /x-log call right after every non log piped function
    142 repo stars
68. ▌
    Build UI · adobe

    Build a feature's ui/ layer — presentation bound to the main-service database. The final, top layer.
    142 repo stars
69. ▌
    Structure · adobe

    Use when laying out or reasoning about a feature's file/folder structure and layer dependencies.
    142 repo stars
70. ▌
    X Execute · adobe

    executes an input optionally with validate first
    142 repo stars
71. ▌
    Build Data · adobe

    Build a feature's data/ layer — data-type namespaces and the State spec. The first, foundational feature phase.
    142 repo stars
72. ▌
    Build Game · adobe

    Build a game — an application whose features model game state, rules, and rendering.
    142 repo stars
73. ▌
    Meta Build · adobe

    Purpose: exercise and **polish the build-* skills and the rules they reference**, using
    142 repo stars
74. ▌
    X Validate · adobe

    validates nested or piped function calls to determine if output types match all required input types
    142 repo stars
75. ▌
    Build Actions · adobe

    Build a feature's action-database — async orchestration over services and transactions. If the feature has async flows or side effects outside of the main store.
    142 repo stars
76. ▌
    Build Feature · adobe

    Build a complete feature step by step
    142 repo stars
77. ▌
    Build Indexes · adobe

    Build a feature's index-database — component/archetype indexes for O(1) lookup. As needed.
    142 repo stars
78. ▌
    Build Systems · adobe

    Build a feature's system-database — the real-time tick loop (systems the scheduler runs each frame). For real-time features only.
    142 repo stars
79. ▌
    Graph Execute · adobe

    executes a graph of steps
    142 repo stars
80. ▌
    Build Computed · adobe

    Build a feature's computed-database — derived observable values.
    142 repo stars
81. ▌
    Build Services · adobe

    Build a feature's services/ layer — async capability contracts (ports to the outside world). Optional.
    142 repo stars
82. ▌
    Build App Entry · adobe

    Wire built features into a running application — import peer schemas, lazy-load peers, and mount the root UI.
    142 repo stars
83. ▌
    Build Application · adobe

    Build an application — a base feature hosting lazily-loaded peer features.
    142 repo stars
84. ▌
    Build Transactions · adobe

    Build a feature's transaction-database — atomic mutations over the store.
    142 repo stars
85. ▌
    Build Core Database · adobe

    Build a feature's schema — the core-database (components, resources, archetypes). The first main-service layer.
    142 repo stars
86. ▌
    Build Service Database · adobe

    Build a feature's service-database — db-bound service factories. If the feature exposes services.
    142 repo stars
87. ▌
    Leonardo Colors · adobe bundle

    Generate accessible color themes using @adobe/leonardo-contrast-colors. Use when the user needs help building contrast-based color palettes, checking WCAG accessibility, creating adaptive themes, or using the Leonardo API.
    142 repo stars
88. ▌
    Reskin · adobe bundle

    Rebuild existing site pages with byte-faithful content on a separately-defined donor design system, preserving text, images, and metadata while applying a new visual design.
    142 repo stars
89. ▌
    Cdp Connect · adobe bundle

    Connect to an existing Chrome browser via Chrome DevTools Protocol to navigate, click, type, screenshot, evaluate JavaScript, read the accessibility tree, and monitor console or network events.
    142 repo stars
90. ▌
    Domain Mask · adobe bundle

    Masks a URL behind a custom domain for demos and recordings by setting up an HTTPS reverse proxy with trusted certificates and automatic cleanup.
    142 repo stars
91. ▌
    Page Reduce · adobe bundle

    Reduces a webpage to a structural skeleton by tokenizing content in the browser and applying LLM reasoning to collapse repeated patterns.
    142 repo stars
92. ▌
    Replica · adobe bundle

    Re-platforms a site to AEM Edge Delivery (or any clean front end) while keeping its current design near pixel-perfect. Recreates key pages as clean HTML/CSS, verifies each against the live site with a measured source-fidelity gate, then hands off for site-wide delivery.
    142 repo stars
93. ▌
    Page Collect · adobe bundle

    Extract structured resources (icons, metadata, text, forms, videos, social links) from any webpage using playwright-cli.
    142 repo stars
94. ▌
    Browser Probe · adobe bundle

    Probe a URL with escalating headless browser configurations to detect CDN bot protection and produce a browser recipe for downstream Playwright consumers.
    142 repo stars
95. ▌
    Cdp Ext Pilot · adobe bundle

    Launches Chrome with an unpacked extension, opens its UI (sidepanel, popup, or options page), and enables interaction via CDP commands for testing and automation.
    142 repo stars
96. ▌
    Cwv Optimizer · adobe bundle

    Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages using EDS-specific domain knowledge, including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and INP with before/after projections.
    142 repo stars
97. ▌
    Page Prep · adobe bundle

    Detects and removes disruptive overlays (cookie banners, modals, paywalls, login walls) from webpages before screenshots, scraping, or browser automation.
    142 repo stars
98. ▌
    Page Tree · adobe bundle

    Captures a spatial hierarchy of rendered DOM elements from any webpage via Playwright CLI, returning an LLM-friendly text tree, structured JSON tree, and a node map with CSS selectors and overlay metadata.
    142 repo stars
99. ▌
    Page Langs · adobe bundle

    Detects all languages used on a webpage — both declared (html@lang, hreflang, nested lang=, meta content-language) and actually present in the body text using Google CLD3 WASM. Reconciles the two signal sets and flags mismatches for i18n audits, hreflang validation, and multilingual content verification.
    142 repo stars
100. ▌
     Audit · adobe bundle

     Audits a website from three perspectives—design, SEO/technical, and LLM/AI-search visibility—and produces a scored, evidence-bound report with prioritized improvements.
     142 repo stars