Choose a clear and distinct app name

Start here

A good name is memorable and explains the job without implying endorsement.

First useful outcome: Compare three names with a plain-language subtitle. 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. Clarify the merchant problem and brand tone; avoid bundling several unrelated jobs in the name.
2. Check store collisions and obvious confusing similarity using current sources.
3. Separate SEO keywords in descriptive copy from the distinctive product brand.
4. Explain tradeoffs and flag legal clearance as a separate owner decision.

Check it worked

Check readability, pronunciation, available public naming signals and current Shopify naming rules. 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 call a name legally safe based only on an availability search. 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 app-naming to help me with this task. Explain each change and verify it before moving on."