Menu
SkillsMP has collected 27 skills from stevenbian9266-cyber/pallastrade. Open a skill to review its source and details.
Showing 27 of 27 collected skills.
Use when the user is working with PallasTrade's payment system — payment methods, gateways (Stripe, Adyen, PayPal), payment sessions, the payment state machine, refunds, store credits, gift cards. Common phrasings include "add payment gateway", "Stripe…
Source text: Mixed languages
Use when the user gives a one-line requirement (一句话需求) and expects AI to expand it into a full PRD and drive the whole development loop — PRD creation (categorized, named, indexed), user confirmation, harness gate, implementation, acceptance criteria, and the…
Source text: Chinese
Use when the user is integrating with PallasTrade's v3 REST API — making requests as a customer, building an admin app, writing webhook consumers, debugging auth errors, parsing API responses. Distinguishes the Store API (customer-facing) from the Admin API…
Use when the user is working on a PallasTrade Commerce project — anything involving PallasTrade models, controllers, customization patterns (decorators, subscribers, services), PallasTrade conventions like prefixed IDs / PallasTrade::Model namespacing /…
Source text: Mixed languages
Use when the user is working on the optional Next.js storefront (the customer-facing online store) — adding a page, customizing checkout, fetching products, integrating with PallasTrade's Store API. Common phrasings include "customize storefront", "Next.js…
Use when the user runs "harness standards generate" and needs the standards JSON drafted, or when a project's standards coverage has gaps that need to be filled by reading business code. Also use when asked to audit or write machine-readable standards…
Source text: Chinese
Use when calling the PallasTrade Admin API from the command line or driving it programmatically as an agent — exploring endpoints, reading or mutating store data, and especially DEBUGGING (inspecting an order/product/customer, checking why a request failed,…
Use when the user wants to install a specific third-party PallasTrade gem (Stripe, Adyen, PayPal, i18n, search, social login, etc.), build their own PallasTrade extension to share across apps, or swap a core PallasTrade service via `PallasTrade.dependencies`.…
Use when the user is building a TypeScript or JavaScript client against PallasTrade — a Next.js storefront, a custom admin tool, a webhook receiver, a backend service that talks to the PallasTrade API. Covers @pallastrade/sdk (Store API) and…
Use when the user is working on PallasTrade's checkout flow — cart pipeline, order state machine, address handling, the transition from cart to completed order, customizing checkout steps, payment sessions, guest checkout. Common phrasings include "checkout…
Source text: Mixed languages
Use when the user is asking how PallasTrade's domain models relate — Orders, LineItems, Variants, Products, Stores, Channels, Markets, Payments, Shipments, Customers, Adjustments. Architecture and relationships only. Common phrasings include "how does X…
Use when the user is hardening a PallasTrade app, responding to a security finding, reviewing a PR for security issues, setting up secrets management, configuring CSP/CORS, or asking about PallasTrade-specific security (CanCanCan scopes, encrypted…
Use when the user is customizing the PallasTrade admin (the `pallastrade_admin` gem) — adding a new resource page, registering a sidebar item, customizing a column in an admin table, overriding a view, scaffolding a new admin section. Common phrasings include…
Source text: Mixed languages
Use when the user wants PallasTrade to react to something that happened — sync orders to an ERP, send notifications, fire webhooks, integrate with external services, configure webhook endpoints, verify webhook signatures. Common phrasings include "react to…
Use when the user is deploying a PallasTrade application to production — Heroku, Render, Fly, AWS, K8s, plain Docker. Covers required environment variables, Sidekiq setup, the release-phase command (`rake pallastrade:upgrade`), ActiveStorage backend config,…
Use when the user is working with PallasTrade's product catalog — Products, Variants, Options, Categories, search, images, product publication on channels. Common phrasings include "add a product type", "variants vs options", "product taxonomy", "categorize…
Use when the user gives a one-line requirement (一句话需求) and expects AI to expand it into a full PRD document and drive the whole development loop — PRD creation (categorized, named, indexed), user confirmation, harness gate, implementation, automated tests +…
Source text: Chinese
Use when the user wants to swap how a core PallasTrade service computes — cart add, cart recalculate, checkout flow, ability checks, payment processing, search, serializers in the API. Common phrasings include "PallasTrade.dependencies",…
Use FIRST when the user is about to customize PallasTrade and the right approach isn't obvious — "how do I customize X", "what's the best way to add Y", "how do I extend PallasTrade", "should I use a decorator or a subscriber", "where should I put this…
Use when the user wants to extend a PallasTrade model, controller, helper, or service class without forking — add an association to PallasTrade::Product, add a method to PallasTrade::Order, override a validation, add a scope, prepend a before_action, hook…
Use when the user is translating PallasTrade — adding a new locale, translating product names/descriptions, fixing missing translations, configuring RTL languages, building a multilingual storefront, working with Mobility, or wrangling PallasTrade.t / I18n.t…
Use when the user is investigating or improving PallasTrade performance — slow product listings, slow cart updates, search latency, image processing bottlenecks, Sidekiq queue tuning, N+1 in admin pages, cache invalidation strategies. Common phrasings include…
Use when the user is working with PallasTrade pricing — variant prices, currency-specific pricing, sale/compare-at prices, price lists (5.3), price rules, EU Omnibus compliance (PriceHistory + prior_price), tax-inclusive pricing. Common phrasings include "set…
Use when the user is working with PallasTrade promotions, discounts, or coupon codes — configuring a promo, writing a custom promotion rule, building a custom action, applying a discount programmatically. Common phrasings include "create promotion", "coupon…
Use when the user wants to add a new model, database table, or REST API endpoint to their PallasTrade project. Covers both `pallastrade:api_resource` (full surface — model + API controllers + serializers + factory + specs + routes) and `pallastrade:model`…
Use when the user is working with PallasTrade's shipping system — shipments, shipping methods, shipping rates, stock locations, the shipment state machine, splitter logic, returns. Common phrasings include "shipping method", "calculate shipping rate", "stock…
Use when the user is writing or running automated tests for a PallasTrade app — model specs, controller specs, API integration tests, admin feature specs, factories, fixtures. Covers RSpec + Factory Bot + Capybara (PallasTrade's stack — NOT Minitest +…