Design

Searches the aem.live documentation for information on features of the platform. Use this skill when you need more information about a feature, want guidance on how to implement a feature, and using existing tools you have to search the web isn't turning up relevant results.

Evidence-based completion verification for Starwards - run actual npm test commands, check E2E snapshots, verify TypeScript types, and confirm build success before claiming work is complete; evidence before assertions always

JSON file content generation guide. Use this skill when you need to create JSON files that can be previewed via `frago view`. Covers formatted display and best practices.

Create effective content models for your blocks that are easy for authors to work with. Use this skill anytime you are building new blocks, making changes to existing blocks that modify the initial structure authors work with.

Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright/Puppeteer, linting, performance validation, and guidance on which tests to maintain vs use as throwaway validation.

Test-driven development for Starwards - write the test first, watch it fail, write minimal code to pass; includes Jest unit tests, Playwright E2E tests, Colyseus state sync, @gameField decorators, Tweakpane UI, and multiplayer scenarios

Guide for creating new AEM Edge Delivery blocks or modifying existing blocks. Use this skill whenever you are creating a new block from scratch or making significant changes to existing blocks that involve JavaScript decoration, CSS styling, or content model changes.

Code file content generation guide. Use this skill when you need to create code files that can be previewed via `frago view`. Covers supported languages, theme selection, and best practices.

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.

PREPARE PHASE: Research methodologies and documentation gathering workflows.Provides systematic research approaches, source evaluation criteria, documentationtemplates, API exploration techniques, and technology comparison frameworks.Use when: conducting technology research, evaluating documentation sources,comparing framework options, analyzing API documentation, gathering requirements.

CODE PHASE (Database): Data layer implementation patterns and best practices.Provides schema design patterns, query optimization strategies, indexing guidelines,data integrity constraints, migration patterns, and database security practices.Use when: designing schemas, writing queries, optimizing performance, planningmigrations, implementing data validation, ensuring data integrity.

ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance.Provides proven architectural patterns including microservices, layered architecture,event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns.Use when: designing system architecture, creating component diagrams, defining interfaces,planning component boundaries, choosing architectural patterns, organizing system modules,or when user mentions: architecture, components, system design, diagrams, C4, microservices,API contracts, service boundaries, architectural patterns.Use for: component design, interface definition, system boundaries, dependency management,architecture documentation, design patterns, integration patterns.DO NOT use for: code implementation details, specific framework syntax, database schema design,frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).

CODE PHASE (Frontend): Client-side implementation patterns and best practices.Provides component architecture patterns, state management strategies, accessibilityguidelines, performance optimization, and responsive design approaches.Use when: building UI components, managing state, implementing forms, optimizingperformance, ensuring accessibility, creating responsive layouts.

CODE PHASE (Backend): Server-side implementation patterns and best practices.Provides service layer patterns, API implementation guidance, error handling strategies,data validation approaches, middleware patterns, and backend security practices.Use when: implementing APIs, creating services, handling errors, validating data,building middleware, implementing authentication/authorization.

CROSS-CUTTING: API contract design patterns for architects and implementers.Provides REST API design patterns, GraphQL schema design, API versioning strategies,error response formats, pagination patterns, and API documentation standards.Use when: designing API contracts, choosing between REST/GraphQL, planning versioning,defining error formats, implementing pagination, documenting APIs.

CROSS-CUTTING: Security patterns and best practices for ALL PACT phases.Provides OWASP Top 10 guidance, authentication/authorization patterns, input validation,secure coding practices, secrets management, and security testing checklists.Use when: implementing authentication, handling user input, storing secrets,designing authorization, reviewing code for vulnerabilities, planning security tests.

Use this skill to inspect what a Rails page currently displays, extract HTML content, or verify rendering WITHOUT starting a dev server. Useful for understanding page output before making changes, debugging views, searching for content, or testing that pages work correctly. Provides scripts/render.rb for quick page inspection and HTML extraction.

Deployment architecture, multi-tenancy design, and environment-specific deployment commands. Use when the user asks about how the application is deployed, multi-tenant architecture with Navigator, Fly.io deployment, or frontend stack details.

TEST PHASE: Testing strategies, patterns, and quality assurance workflows.Provides test strategy frameworks, coverage guidelines, unit/integration/e2e patterns,performance testing approaches, and security testing checklists.Use when: designing test strategies, writing tests, evaluating coverage,planning QA workflows, implementing test automation.

Working with the Navigator Go submodule for web server fixes and enhancements. Use when deployment plans require Navigator changes, config parsing issues arise, or new routing/proxy behavior is needed.