Menu
Finds and consolidates duplicate loaders across page JSONs to reduce redundant API calls.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose and fix headless login issues on VTEX storefronts — covering authorized domain setup and simulating an authenticated session by copying VtexIdclientAutCookie cookies.
Use when debugging what crawlers or bots see on a deco site, verifying if SSR is active for bots, or diagnosing firstByteThresholdMS behavior.
Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.
Configure deco.cx Variants — the mechanism that swaps the value of a section, page, image, message, or ANY custom-typed prop based on a matcher rule (device, cookie, date, A/B test, geo, path, query string, etc.). Use when the user asks to A/B test a section, personalize a page per audience/segment, show different banners per device or location, schedule a promotion by date/cron, add a new variant-able type (promotion, VTEX segment, product list, menu items), write a custom matcher, or generally wire up `website/flags/multivariate*` in `.deco/blocks/*.json`. Covers the JSON shape (`variants: [{ value, rule }]`), the resolution order (first match wins, catch-all last), every built-in matcher (`always`, `never`, `device`, `date`, `cron`, `random`, `cookie`, `host`, `pathname`, `queryString`, `userAgent`, `location`, `site`, `environment`, `multi`, `negate`), how to compose them with `multi` (and/or) and `negate`, the 8-line boilerplate to create your own `flags/multivariate/<type>.ts`, the shape of a custom `ma
Install and configure the Blog Manager on a deco-site storefront. Covers the blog app, page routes, sections, Blog Manager MCP connection in Studio, and first-run brand context initialization.
Use when inside a deco.cx ecommerce repository (deco.ts present, decobot in PR history) and the user wants automated QA for purchase-journey correctness — set up E2E coverage, test the add-to-cart / checkout flow, or scaffold a CI gate for the store with the @decocms/qa engine. NOT for load/cache performance testing (use deco-e2e-testing) or hand-written Playwright spec files.
| name | deduplicate-loaders |
| description | Finds and consolidates duplicate loaders across page JSONs to reduce redundant API calls. |
The main point is to reduce the number of API calls to the server.
At the JSON of the pages, you will see loaders defined.
When two equal loaders are defined, you can combine them into a single loader.
Start analyzing the JSON of the page that the user is editing.
If there is no current, page, look for home, categories and search page.
Avoid looping, ask how many pages the user wants to analyze.
Before: "page": { "__resolveType": "vtex/loaders/intelligentSearch/productListingPage.ts", "selectedFacets": [ { "key": "productClusterIds", "value": "334" } ], "count": 24 }, "seo": { "__resolveType": "vtex/loaders/intelligentSearch/productListingPage.ts", "selectedFacets": [ { "key": "productClusterIds", "value": "334" } ], "count": 24 }
After: New file: GlobalCluster334.json { "__resolveType": "vtex/loaders/intelligentSearch/productListingPage.ts", "selectedFacets": [ { "key": "productClusterIds", "value": "334" } ], "count": 24 } "page": { "__resolveType": "GlobalCluster334", }, "seo": { "__resolveType": "GlobalCluster334", }
