agentleFS
Sign inStart free
khadinakbarlabskhadinakbarlabs/shopify-app-builder/skills/polaris-ui/SKILL.md

polaris-ui

Skill2 starsChanged 40 days agoMITView on GitHub

Create Shopify embedded app pages with current Polaris patterns or maintain existing Polaris React UI.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only for missing information that changes this task.

    line 13
  2. Distinctive:

    Start with the merchant task, page hierarchy, meaningful fields, default state and clear help text.

    line 18
  3. Distinctive:

    Use supported component props and tokens.

    line 19
  4. Distinctive:

    Test keyboard, narrow screens, translated/long text and empty/error states before adding decoration.

    line 20
  5. Distinctive:

    Verify the real embedded page and persisted action.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build a familiar Shopify interface

Start here

Polaris is Shopify's design system; match the actual installed component generation.

First useful outcome: Build a page with one primary action and complete loading/error states. 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. For a new app follow current App Home/Polaris web components and scaffold wiring; inspect an existing app before any migration.
  2. Start with the merchant task, page hierarchy, meaningful fields, default state and clear help text.
  3. Use supported component props and tokens; keep validation, save/discard and status feedback understandable.
  4. Test keyboard, narrow screens, translated/long text and empty/error states before adding decoration.

Check it worked

Verify the real embedded page and persisted action; do not mix React-only props with web components. 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

Retained React examples are for compatible existing projects, not the default for a new app. 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. These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with official documentation before using them.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free