shopify-functions
Skill2 starsChanged 38 days agoMITView on GitHub
Build and test Shopify Functions after checking extension target, input schema and store eligibility.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Shopify/Shopify-AI-Toolkittheir own version, first seen Oct 13, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- Shopify/agent-skillstheir own version, first seen Apr 1, 2026
- dragnoir/Shopify-agent-skillstheir own version, first seen Feb 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- openai/plugins★ 7.8ksame name
- Shopify/Shopify-AI-Toolkit★ 621same name
- Shopify/agent-skills★ 84same name
- dragnoir/Shopify-agent-skills★ 48same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- admin-graphqlSkill
- admin-restSkill
- app-accessibilitySkill
- app-authSkill
- app-billingSkill
- app-bridgeSkill
- app-frameworkSkill
- app-listing-optimizationSkill
- app-market-researchSkill
- app-namingSkill
- app-niche-finderSkill
- app-performanceSkill
- app-pricing-strategySkill
- app-release-readinessSkill
- app-validationSkill
- b2b-marketsSkill
- built-for-shopify-standardsSkill
- dev-troubleshootingSkill
- hydrogen-storefrontSkill
- liquid-themesSkill
- merchant-pain-preventionSkill
- metafields-metaobjectsSkill
- polaris-uiSkill
- shopify-app-store-adsSkill
- shopify-cliSkill
- shopify-connectionsSkill
- shopify-project-copilotSkill
- storefront-apiSkill
- top-app-ux-patternsSkill
- using-shopify-app-builderSkill
- ux-empty-error-statesSkill
- ux-modern-app-feelSkill
- ux-onboardingSkill
- ux-polaris-antipatternsSkill
- webhooksSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 13
Ask only for missing information that changes this task.
- Distinctive: line 18
Use the project's CLI generator, current target schema and language/runtime rather than guessing payload fields.
- Distinctive: line 24
Test no-op, valid case, boundaries, malformed input and applicable execution limits before release.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customize commerce logic with Functions
Start here
Functions are Shopify-run logic, with constrained inputs and execution limits.
First useful outcome: Generate one supported Function and test a synthetic input locally. 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
- Confirm function target, merchant plan and distribution eligibility using current docs.
- Use the project's CLI generator, current target schema and language/runtime rather than guessing payload fields.
- Implement deterministic bounded logic; treat absent/invalid data safely and do not assume network access.
- Generate types, run/build with version-supported CLI commands, then test in an authorized dev store.
Check it worked
Test no-op, valid case, boundaries, malformed input and applicable execution limits before release. 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
A local build does not prove the Function is enabled or compatible on a merchant's store. 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 shopify-functions to help me with this task. Explain each change and verify it before moving on."
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
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.