name	aem-performance
description	AEM performance review — JCR queries, traversal, resolver lifecycle, PostConstruct overhead
allowed-tools	Read, Grep, Glob
argument-hint	[file or class path]

Review $ARGUMENTS for AEM performance issues. Report each finding as Blocking / Warning / Suggestion.

JCR query without an Oak index or without a result limit — Blocking
Query executed inside a loop — Blocking
Thread.sleep() in servlet, job, scheduler, or workflow step — Blocking
Request-scoped state (resolver, session, request) stored in an OSGi singleton field — Blocking
Expensive query or broad tree traversal in @PostConstruct on a frequently rendered Sling Model — Warning
ResourceResolver or Session held open longer than needed — Warning
Lazy initialization missing where data is not always needed — Suggestion

Más de este repositorio

mismo repositorio

aem-accessibility

techforum-repo/aem-claude-code

AEM accessibility review — WCAG 2.1 AA compliance in HTL templates, Coral UI dialogs, and frontend components

2026-03-208

aem-cloudmanager

techforum-repo/aem-claude-code

Cloud Manager and OakPAL review — package filters, embed order, Dispatcher SDK, deployment safety

2026-03-188

aem-headless

techforum-repo/aem-claude-code

AEM headless review — Content Fragment models, GraphQL persisted queries, CF Java integration, CORS, and Dispatcher rules for headless delivery

2026-03-188

aem-oak-index

techforum-repo/aem-claude-code

Oak index review and creation — index type selection, property coverage, evaluatePathRestrictions, async configuration

2026-03-188

aem-project-conventions

techforum-repo/aem-claude-code

Always-loaded AEM project conventions — naming patterns, package structure, utility library usage, and team-specific standards that Claude applies silently on every task

2026-03-188

aem-security

techforum-repo/aem-claude-code

AEM security review — admin resolver, query injection, path validation, exposed endpoints, hardcoded secrets

2026-03-188

name	aem-performance
description	AEM performance review — JCR queries, traversal, resolver lifecycle, PostConstruct overhead
allowed-tools	Read, Grep, Glob
argument-hint	[file or class path]

Review $ARGUMENTS for AEM performance issues. Report each finding as Blocking / Warning / Suggestion.

JCR query without an Oak index or without a result limit — Blocking
Query executed inside a loop — Blocking
Thread.sleep() in servlet, job, scheduler, or workflow step — Blocking
Request-scoped state (resolver, session, request) stored in an OSGi singleton field — Blocking
Expensive query or broad tree traversal in @PostConstruct on a frequently rendered Sling Model — Warning
ResourceResolver or Session held open longer than needed — Warning
Lazy initialization missing where data is not always needed — Suggestion