commercetools

@commercetools source repo

27 skills
0 followers
6 hours ago last updated

▌
Commercetools Connect · commercetools bundle
Build, test, deploy, install, and certify production-ready commercetools Connect applications — service/API-extension, event/subscription, job, and merchant-center custom apps — in TypeScript, JavaScript, or Java, and integrate a deployed connector into a custom storefront. Covers the connect.yaml contract, least-privilege scopes, lifecycle scripts, sync-vs-async idempotency/ack, testing, and deployment. Includes connector sub-areas for payment (Stripe, Adyen), tax (Avalara, Vertex), PIM (Akeneo), CRM (Salesforce, HubSpot), order-management/OMS, gift cards, transactional email (SendGrid), marketplace (Mirakl), promotion and loyalty (Talon.One, Voucherify), analytics export to a warehouse/CDP (BigQuery, Segment), search/product discovery (Algolia), and shipping (carriers, rate engines). Use when building, configuring, forking, or debugging a commercetools Connect connector, or syncing commercetools data to or from an external system. Not for the hosted Checkout widget (see commercetools-checkout).

0
installs
▌
Commercetools Checkout · commercetools bundle
The Checkout — payment-only mode (integrating Checkout for payments while owning the rest of the flow), full hosted checkout (checkoutFlow), widget integration via @commercetools/checkout-browser-sdk, configuration, PSP connector setup (Stripe, Adyen, Mollie), and webhook handling. Use when integrating Checkout (the product) into a storefront or headless app — not for generic cart-to-order patterns (see commercetools-storefront).

0
installs
▌
Commercetools Platform · commercetools bundle
Core commercetools API and SDK patterns — TypeScript SDK setup, ClientBuilder authentication, project data model (products, customers, orders, types, channels, stores), GraphQL vs REST patterns, query predicates, optimistic concurrency, rate limits, and platform observability. Foundational layer that storefront, MC app, Connect, and integration skills all reference. Use for any commercetools project regardless of surface.

0
installs
▌
Commercetools Storefront · commercetools bundle
Production patterns for building customer-facing storefronts on commercetools - the full B2C and B2B domain feature set. Patterns are stated as decisions plus commercetools-exact code; framework-specific implementation. Assumes a server tier exists to host the BFF. Use for PDP, PLP, cart, checkout flow, customer login, search/facets, locale handling, and any B2B- or B2C-specific feature.

0
installs
▌
Commercetools Integrations · commercetools bundle
Integrate commercetools with an external system through Connect — payment (Stripe, Adyen, Mollie, PayPal), tax (Avalara, Vertex, TaxJar), PIM (Akeneo), CRM (Salesforce, HubSpot), order management/OMS (Fluent Commerce, fulfillmenttools, NewStore), gift cards (Voucherify), transactional email (SendGrid, Mailgun), marketplace (Mirakl, Marketplacer), promotion and loyalty (Talon.One, Voucherify), analytics export to a warehouse/CDP (BigQuery, Snowflake, Segment), search and product discovery (Algolia, Constructor, Bloomreach), and shipping (carriers, rate engines, label platforms). Each sub-area rules out the native capability first, then picks a rung — use a public connector, close the gap with config, fork, or build. Use when syncing commercetools to or from an external system, or configuring, forking, or debugging a connector. Type-agnostic build contracts live in commercetools-connect.

0
installs
▌
Commercetools Commerce Patterns · commercetools bundle
Surface-independent commerce domain logic — pricing models (customer groups, channel fallback, high-precision money), discount stacking (Product/Cart/Code/Direct/Groups), shipping predicates and cart score, tax modes, payment object modeling, Import API bulk patterns, and catalog architecture. Use for commerce-domain questions that are independent of surface (storefront, MC app, Connect).

0
installs
▌
Commercetools Spec Driven Development · commercetools bundle
Wire the commercetools skills into a spec-driven development framework — GitHub Spec Kit (.specify/) or OpenSpec (openspec/). Use when user wants to setup or check the status of a spec-driven development framework that touches commercetools.

0
installs
▌
Orca Review · commercetools bundle
Review Orca security alerts from a JSON export, clone affected repos, and cross-reference with open Renovate PRs to identify fixes.

0
installs
▌
Renovate Review · commercetools
Review Renovate dependency upgrade PRs to assess safety and effort. Use when reviewing PRs from Renovate bot that update NPM dependencies.

0
installs
▌
Renovate Migrate · commercetools
Perform migrations for Renovate dependency upgrades based on breaking changes identified in a review. Use after running /renovate-review.

0
installs
▌
Grafana Dashboard · commercetools
Create and edit monitoring dashboard JSON for import. Use when building dashboards, adding panels/widgets, or configuring metric queries and visualizations.

0
installs
▌
Pr Review Navigator · commercetools
Generate AI-assisted navigation aids to help humans start reviewing a pull request more efficiently. Use when starting a PR review to get oriented on large or unfamiliar changes.

0
installs
▌
Ticket Context Page · commercetools
Research a Jira ticket and create a Confluence context page with current understanding, dev action items, related tickets, domain docs, and people to consult. Use when asked to "create a context page for", "research this ticket", "gather context for", "create a knowledge brief for", "collect information about this Jira issue", "create a Confluence page for ticket", or "what do I need to know to solve this ticket".

0
installs
▌
Label Cloud Resources · commercetools
Add default labels to cloud providers using default_tags/default_labels blocks. Use when reviewing Terraform PRs that need consistent provider-level labeling.

0
installs
▌
On Call Skill Creator · commercetools bundle
Create a new on-call assistant skill for a rotation or team, modelled on the Merchant Center one. Use this whenever a team wants their own on-call skill, or someone says "create an on-call skill", "scaffold on-call for <team>", "adopt the Merchant Center on-call skill for us", or "make on-call-<rotation>". It interviews you, ingests your runbooks, dashboards, logs, and escalation setup, and generates a ready `on-call-<rotation>` skill. Trigger even when the user only names their rotation and asks for on-call help tooling.

0
installs
▌
On Call Merchant Center · commercetools bundle
Respond to a Merchant Center production alert or symptom while on call. Finds the matching Confluence runbook. Confirms live severity from Grafana. Flags recent deploys. Hands over the LogScale query to run. Use whenever you are paged for Merchant Center or Identity and see things like "errors exceed 100", "elevated error rate", "event loop lag", "pod restarts", "memory pressure", "502 accessing Merchant Center or Studio", "proxy unhealthy", "cannot log in via SSO", "Merchant Center unavailable", or a raw alert name. Also use for "which runbook covers this?" and "how do I respond to this alert?". Trigger even without the word "runbook". Do not use for building dashboards or general commercetools API or product how-to.

0
installs
▌
Production Readiness Report · commercetools bundle
Analyze a repository and pre-fill a local production-readiness questionnaire using evidence from charts/manifests, deployment/config files, dependencies, and reliability patterns. Use before go-live or readiness reviews.

0
installs
▌
Production Readiness Review · commercetools bundle
Review a completed production-readiness report and produce prioritized recommendations based on the expectations matrix in this skill. Use after running /production-readiness-report to get actionable next steps.

0
installs
▌
Prometheus Monitoring Migration · commercetools
Migrate Prometheus monitoring (alerts, recording rules, ServiceMonitors) in Kubernetes/Helm environments. Use this skill when the user wants to: move alert or recording rules between repos (e.g. from a centralized k8s-gitops repo into per-service Helm charts), set up ServiceMonitors with relabeling, migrate label selectors (like switching from `job="kubernetes-pods"` to `service_discovery_job`), analyze dependencies between recording rules and alert rules, plan safe deployment ordering, or lint Prometheus rules with pint. Also trigger when the user mentions PrometheusRule CRDs, Prometheus Operator monitoring setup, or golden-signals recording rules.

0
installs
▌
Remember · commercetools
Persist guidelines, conventions, and architectural decisions into the repository's knowledge base. Use when told to remember something for future sessions.

0
installs
▌
Security Auditor · commercetools
Perform comprehensive security audit of a repository with detailed findings and step-by-step PoCs. Use when assessing a repo's security posture or investigating potential vulnerabilities.

0
installs
▌
Jira Implement Task · commercetools
Fetch Jira ticket, create branch, implement changes, commit, push, open PR.

0
installs
▌
Agent Restore Context · commercetools
Manage restore context files so skills can survive /clear and /compact. Use to write, delete, check, or list .agent-restore-context-* files.

0
installs
▌
Repo Healthcheck Node · commercetools
Verify a Node.js/TypeScript repo's development environment is correctly set up. Checks Node.js version, pnpm version, dependency installation, and build success. Use when onboarding, troubleshooting CI failures, or verifying a fresh clone.

0
installs
▌
Repo Maintenance Node · commercetools
Perform a broad Node/TypeScript repository health sweep — formatting, linting, type errors, dead code, dependency hygiene, and open Renovate PRs. Use when cleaning up a repo or preparing for a release.

0
installs
▌
Jira Create Epic From Plan · commercetools
Create a Jira epic and child tickets from a plan or spec, with dependency links, phase labels, and a bulk link script.

0
installs
▌
Agent Restore Context Setup · commercetools bundle
Set up the restore-context hook so skills can resume workflows after /clear and /compact. Use when setting up a new project or after cloning a repo that uses restore-context skills.

0
installs

27 published skills