By easingthemes
Automate Adobe Experience Manager workflows by combining browser automation for DOM inspection, dialog verification, and QA capture with post-task hooks that enforce plugin version checks and curl allowlist rules.
Executes AEM-specific bug verification steps — navigates to AEM pages, reproduces bugs visually via Chrome DevTools, captures screenshots, and returns verification evidence. Used by dx-bug-verify skill when the bug involves AEM components.
Captures AEM component editorial guide via Chrome DevTools — opens editor, triggers dialog, screenshots, and writes editor-friendly docs. Use for post-development documentation.
Verifies AEM component frontend rendering — creates/reuses demo pages, screenshots components in wcmmode=disabled via Chrome DevTools, compares against Figma reference or requirements using multimodal vision. Used by aem-fe-verify skill.
Resolves all source files for a component across project repos. Reads file-patterns.yaml for path conventions. Returns file paths with clickable ADO URLs. Used by aem-component and dx-ticket-analyze skills.
Inspects AEM components via MCP — captures dialog fields, finds pages, creates test pages, configures demo data. Use for pre/post development component verification.
Find all source files, AEM pages, and dialog fields for an AEM component. Use when a developer asks "where is component X?", "what files for hero?", or any component lookup question.
Generate AEM demo documentation — find or create docs page with configured component, capture dialog and website screenshots on QA, write authoring guide. Extends /aem-editorial-guide for automated pipeline use. Invoked by /dx-agent-all Phase 7 and /dx-req-dod.
Check health of AEM project infrastructure — verifies component definitions, OSGi configs, dispatcher rules, and content structure against expected state. Use to diagnose configuration drift or after making infrastructure changes.
Capture editorial guide for a component dialog in AEM — open editor, screenshot dialog, and write editor-friendly authoring guide. Use after /aem-verify or deploying changes to create editorial documentation.
Visually verify a component's frontend rendering on local AEM — screenshots the component in wcmmode=disabled, compares against Figma reference or requirements using multimodal vision, and fixes gaps in a loop. Use after build deploys to local AEM. Trigger on "verify frontend", "visual verify", "fe verify", "check component rendering", "compare AEM with figma".
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Enterprise AI development platform for teams shipping on Azure DevOps and Atlassian. 75+ skills that run identically across Claude Code, GitHub Copilot CLI, and VS Code Chat — from ticket to PR, fully autonomous. Deep AEM specialization built in.
Enterprise teams run complex sprints across multiple repos, multiple IDEs, and multiple team members. They need a system that handles the full lifecycle — requirements analysis, implementation planning, code generation, testing, verification, documentation, and PR creation — with governance at every step. Without re-explaining the project every session.
KAI is a structured development workflow built as a plugin system for enterprise teams. It encodes your entire sprint lifecycle — requirements, planning, execution, review, PR — into skills that orchestrate multi-agent pipelines across every major AI platform. A single command like /dx-req-all pulls the ticket from Azure DevOps or Jira, validates readiness against your DoR, distills developer requirements, researches the codebase with parallel subagents, and generates a team summary. Each skill chains specialized agents (Opus for deep review, Sonnet for execution, Haiku for lookups), gathers context from multiple sources (tickets, config, codebase, Figma designs, live AEM content), and writes structured output that the next skill picks up automatically.
What makes it different:
Add the marketplace, then install the plugins you need:
# Add the marketplace (once)
/plugin marketplace add easingthemes/dx-aem-flow
# Install plugins
/plugin install dx-core@dx-aem-flow # Core workflow (all projects)
/plugin install dx-hub@dx-aem-flow # Multi-repo orchestration (optional)
/plugin install dx-aem@dx-aem-flow # AEM tools (AEM projects)
/plugin install dx-automation@dx-aem-flow # Autonomous agents (24/7 pipelines)
From a local clone:
/plugin marketplace add /path/to/dx-aem-flow
/plugin install dx-core@dx-aem-flow
Full-stack development workflow for Azure DevOps and Jira projects: requirements gathering, implementation planning, step-by-step execution with testing and review, code review, bug fixes, and PR management.
Works with any tech stack.
Hub directory management for coordinating work across multiple consumer repos — init, config, status.
The complete AEM development lifecycle: component dialog inspection, JCR content, page authoring, editorial QA with browser automation, snapshot/verify lifecycle, and demo capture. Includes the AEM MCP server for live JCR and dialog access. Purpose-built for AEM Cloud and on-premise projects.
Requires dx plugin.
npx claudepluginhub easingthemes/dx-aem-flow --plugin dx-aemFull-stack development workflow for Azure DevOps projects — requirements, planning, execution, review, bug fixes, and PR management
Autonomous AI agents for ADO workflows — Definition of Ready checker, Definition of Done checker, DoD fixer, PR reviewer, PR answerer. Runs as ADO pipelines triggered by AWS Lambda webhooks.
Multi-repo hub orchestration — run dx skills across sibling repositories from a single hub directory.
Persistent file-based planning for AI coding agents. Crash-proof markdown plans (task_plan.md, findings.md, progress.md) that survive context loss and /clear, with an opt-in completion gate and multi-agent shared state. Manus-style. Works with Claude Code, Codex CLI, Cursor, Kiro, OpenCode and 60+ agents via the SKILL.md standard. Includes Arabic, German, Spanish, and Chinese (Simplified and Traditional).
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.