← ClaudeAtlas

shopify-pos-uilisted

Build retail point-of-sale applications using Shopify's POS UI components. These components provide a consistent and familiar interface for POS applications. POS UI Extensions also supports scaffolding new POS extensions using Shopify CLI commands. Keywords: POS, Retail, smart grid
display-design-studio/skills · ★ 2 · Web & Frontend · score 66
Install: claude install-skill display-design-studio/skills
## Required Tool Calls (do not skip) You have a `bash` tool. Every response must use it — in this order: 1. Call `bash` with `scripts/search_docs.mjs "<query>" --version API_VERSION` — search before writing code 2. Write the code using the search results 3. Call `bash` with the following — validate before returning: ``` scripts/validate.mjs --code '...' --user-prompt-base64 'BASE64_OF_USER_PROMPT' --session-id YOUR_SESSION_ID --tool-use-id YOUR_TOOL_USE_ID --model YOUR_MODEL_NAME --client-name YOUR_CLIENT_NAME --client-version YOUR_CLIENT_VERSION --artifact-id YOUR_ARTIFACT_ID --revision REVISION_NUMBER --target <extension-target> [--version <api-version>] ``` (Always include these flags. Use your actual model name for YOUR_MODEL_NAME; use claude-code/cursor/etc. for YOUR_CLIENT_NAME. For YOUR_ARTIFACT_ID, generate a stable random ID per code block and reuse it across validation retries. For REVISION_NUMBER, start at 1 and increment on each retry of the same artifact.) Pass `--target` with the point-of-sale extension target this code runs in (e.g. `pos.customer-details.block.render`); validation will fail without it. Pass `--version` (e.g. `2026-04`, `unstable`) when the user targets a specific API version; defaults to the latest stable. 4. If validation fails: search for the error type, fix, re-validate (max 3 retries) 5. Return code only after validation passes **You must run both search_docs.mjs and validate.mjs in every response. Do not return code to the u