Skip to content
Back to skills

Ux Polaris Antipatterns

ASecurity

Review Shopify app UI for task-blocking layout, forms, component misuse and accessibility problems.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 1, 2026
ai-agentsreactapidocumentation

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add khadinakbarlabs/shopify-app-builder --skill ux-polaris-antipatterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ux Polaris Antipatterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ux Polaris Antipatterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/khadinakbarlabs-ux-polaris-antipatterns/badge)](https://www.skillsdirectory.com/skills/khadinakbarlabs-ux-polaris-antipatterns)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ux-polaris-antipatterns
description: "Review Shopify app UI for task-blocking layout, forms, component misuse and accessibility problems."
---

# Fix confusing UI with focused changes

## Start here

An anti-pattern is an interaction that repeatedly creates avoidable friction.

First useful outcome: Find the three highest-impact issues in a real merchant journey.
Ask only for missing information that changes this task. Inspect the existing project and use synthetic data before touching a merchant store. Explain the next action and its expected result in plain language; offer a recommended default with its tradeoff.

## Guided workflow

1. Inspect the installed Polaris generation; distinguish existing React code from current web components.
2. Prioritize blocked tasks, unsaved-data loss, misleading status and inaccessible controls before cosmetic preferences.
3. Propose minimal fixes with correct component APIs, contextual help and clear primary actions.
4. Re-test the same journey and avoid a whole-design-system rewrite without need.

## Check it worked

Tie every issue to reproduction, merchant impact and a verified corrected state.
Report what was changed, what was tested, and what still needs account access or live verification. Do not claim production readiness or approval from generated code alone.

## If you get stuck

Do not apply old component rename tables blindly to a newer component generation.
Give one safe next step and a redacted error example, not a list of speculative fixes.

## Safety and optional depth

Use only the user's selected project/accounts. Never read credential caches or request secrets in chat; the operator configures the application's approved secret store. Ask before live deployment, store mutations, billing, publication or paid runs unless that exact action is already authorized. No MCP service is required by this plugin.

For concrete examples in an existing project, read only the relevant section of [technical-guide.md](references/technical-guide.md). These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with [official documentation](https://shopify.dev/docs/api/app-home) before using them.

Example request: "Use ux-polaris-antipatterns to help me with this task. Explain each change and verify it before moving on."

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…