adobe-commerce-partnerships-ai-kit

Reads 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 plan.

Reads 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 write code — outputs a structured UI engineering plan.

Generate 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 any UI technology — JavaScript/TypeScript SPAs, Java JSP/Thymeleaf, C# Blazor/Razor, Python Django/Flask templates, Flutter, or others. Triggers on phrases like "generate service card", "create service card", "document this UI", or when a target app directory is provided with intent to generate cards.

Executes 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; the service cards define HOW to write it.

Audits 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 / partial / fail per file with specific gaps and fix guidance. Run after implement-feature or after manual edits.