Use this skill whenever the user wants to onboard a Spryker project onto a project-owned Cypress E2E baseline in place of Spryker's internal demo-shop test suites. Trigger on phrases like "migrate off spryker/cypress-tests", "remove the demo-shop…
Use whenever the user wants to implement a Spryker customization from a PRD or acceptance criteria. Triggers include "build this", "implement this", "here is a PRD - build it", "add X for the demo", "build this PoC", "production-quality build". Drives the…
Use at the very start of a new customer project, on an unmodified (booted or not) clone of a Spryker b2b/b2b-marketplace demoshop — 'turn this demoshop into our project', 'start the project setup', 'run the project starter'. Also the trigger for 'give me the…
Sets up the Spryker AI Dev SDK in a Spryker project. Covers two related flows: first-time onboarding (installs the Composer package, wires console commands, registers the MCP server, installs `CLAUDE.md` and `.claude/rules/`) and updating (refreshes just…
Use to take a transformed Spryker project from 'files written' to 'verified running' — the first boot at project start (the wizard's last mandatory step and commit point), re-applying data changes on an already-booted stack, or standalone per-store…
Use when code review is requested
Use when a Spryker project adopts a custom namespace instead of Pyz and the code layer must resolve, build, lint, and test it — namespace registration, composer autoload, frontend build config, codeception wiring. A pre-boot wizard step of project start;…
Use when changing what infrastructure a Spryker project runs on — disable optional dev services (mail catcher, swagger, dashboard), or applications in a deploy file — or when building a new environment deploy file (deploy.<project>-<env>.yml). A pre-boot…