agentleFS
Sign inStart free
ShopifyKnown publisherShopify/trending-products/AGENTS.md

trending-products

AGENTS.md5 starsChanged 3 months agoMITView on GitHub

This repository is a prompt-first launch workflow for creating a Shopify trend store with a merchant. This repository is initialized for the Stripe projects - Stripe CLI with the projects plugin to manage third-party services, credentials, and deployments for this project. Use the stripe-projects-cli to manage deploying and access to third party services. <!-- stripe-projects-cli managed:agents-md:end -->

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use prompts/launch-store.md as the operating procedure and source of truth.

    line 8
  2. Very specific:

    Read artifacts/README.md to understand which working documents to create and maintain.

    line 9
  3. Very specific:

    Before starting or resuming work, inspect the existing files in artifacts/ and continue from the first incomplete step.

    line 10
  4. Distinctive:

    Keep artifacts merchant-readable.

    line 11
  5. Distinctive:

    Ask concise questions in batches and record the merchant's answers in the relevant artifact.

    line 12
  6. Very specific:

    Stop for the approval gates defined in prompts/launch-store.md.

    line 14
  7. Distinctive:

    Do not purchase a domain, publish a theme, publish catalog items, connect a live domain, run paid generation, or send/activate marketing …

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Agent instructions

This repository is a prompt-first launch workflow for creating a Shopify trend store with a merchant.

How to use this repo

  • Start from SKILL.md.
  • Use prompts/launch-store.md as the operating procedure and source of truth.
  • Read artifacts/README.md to understand which working documents to create and maintain.
  • Before starting or resuming work, inspect the existing files in artifacts/ and continue from the first incomplete step.
  • Keep artifacts merchant-readable. Update them as decisions are made instead of replacing prior context.
  • Ask concise questions in batches and record the merchant's answers in the relevant artifact.
  • Be explicit about assumptions, limitations, manual handoffs, account requirements, and costs.
  • Stop for the approval gates defined in prompts/launch-store.md; do not treat a prior general preference as approval for a specific action.
  • Do not purchase a domain, publish a theme, publish catalog items, connect a live domain, run paid generation, or send/activate marketing without explicit approval in the current conversation.

Expected workflow files

  • prompts/launch-store.md — full launch procedure.
  • artifacts/README.md — artifact descriptions and expected contents.
  • artifacts/brand-brief.md — merchant brief and brand decisions.
  • artifacts/research-brief.md — research findings and approved opportunity direction.
  • artifacts/catalog-plan.md — catalog, sourcing, pricing, and product confirmation plan.
  • artifacts/campaign-plan.md — creative/image plan, asset status, and marketing approval state.
  • artifacts/launch-checklist.md — store setup, QA, domain, launch blockers, owners, and approvals.
<!-- stripe-projects-cli managed:agents-md:start -->

Stripe Projects CLI

This repository is initialized for the Stripe projects

Tools used

  • Stripe CLI with the projects plugin to manage third-party services, credentials, and deployments for this project. Use the stripe-projects-cli to manage deploying and access to third party services.
<!-- stripe-projects-cli managed:agents-md:end -->

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