Design Ecommerce logo

Design Ecommerce

Community
arimaML
design-ecommerce

Ecommerce / product site lens. Use when the site's purpose is to sell physical or digital products — online stores, product detail pages, catalogues, shopping cart flows. Load after design-core has established why the site exists and confirmed the goal is purchase. Does not replace design-core; adds subtype-specific priorities, typical failures, and layer-by-layer guidance.

Overview

PublisherarimaML
Repositoryuniversal-design
Skill namedesign-ecommerce
Stars
3
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by arimaML on GitHub. Read the source before you install it.

Installation

Install the Design Ecommerce AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/arimaML/universal-design/tree/main/design-ecommerce
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/arimaML/universal-design.git /tmp/universal-design
mkdir -p .claude/skills
cp -r /tmp/universal-design/design-ecommerce .claude/skills/design-ecommerce
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design Ecommerce in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design Ecommerce on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design Ecommerce is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Design Ecommerce — Stores & Product Pages

A subtype lens for design-core. Load this after design-core has run its three entry steps and confirmed the goal is purchase.

This file does not redefine the eight elements, the four layers, the two modes, or the two phases. It only adds what is specific to ecommerce sites.

Focus

Usability beats beauty, but a product card can be a piece. The purchase path runs without friction — every step the visitor must take is one step too many. Trust is visible early: shipping, returns, guarantees, reviews appear before the visitor has to wonder. Comparison between products is easy, not hidden behind a filter maze.

Marketing leads by default. The floor is non-negotiable: contrast, click zones, focus, body size.

Typical failures

  • Indistinguishable cards. Every card looks the same, so no card is remembered. Fix: let the product dictate the card's hierarchy — image, name, price, not a uniform template.
  • Price or availability buried. The two facts a buyer needs first are the two facts hidden last. Fix: price and availability are visible on the card, not only on the detail page.
  • Heavy filters. Ten filter dimensions, none applied by default, all distracting. Fix: filters reduce results, not attention.
  • Checkout that suddenly complicates. The cart works, then step 2 asks for a phone number, then step 3 requires an account. Fix: every step past "add to cart" must justify its existence.

Layer-by-layer

Frame (composition, space). The card grid is stable — one rhythm, even gaps, no surprises. Space between cards is consistent so the eye can scan, not re-orient per row. Navigation (categories, search) is a working tool, not a hero.

Body (form, color). Color serves the product. The palette recedes — the products provide the color. Button forms are unambiguous: "add to cart" is a distinct shape, "add to wishlist" is visibly secondary. Radius system is one token, applied consistently.

Surface (texture, typography). Price and product name are typographically clear — the two things that must be readable at a glance. Description text is readable at body size, not shrunk to make room. Product images are treated as surfaces, not just thumbnails.

Accent (point, line). The primary action is obvious everywhere it appears. Icons (cart, search, wishlist) are consistent in weight. Dividers and rules stay out of the way unless they separate distinct sections.

Reading order

The ecommerce flow has three distinct reading orders, and each is optimized for its own step:

  1. Browse — categories are scannable, products are distinguishable, price/availability visible.
  2. Decide — detail page answers the buyer's real questions (material, size, delivery, returns) in the order they arise.
  3. Buy — checkout confirms, doesn't interrogate. Every field has a visible reason.

Audit specifics

Beyond the common grid, these are the ecommerce breakages to hunt:

  • Typography → Surface → price and availability not readable on the card → the two facts a buyer needs first are on the card, not only on the detail page.
  • Form → Body → "add to cart" reads as decoration on the product image → shape and contrast distinct from the rest of the card.
  • Point → Accent → cart/wishlist/search icons differ in weight → one icon system, aligned to the type baseline.
  • Line → Frame → filters demand attention before they reduce results → filters cut results, not attention; sensible defaults applied.
  • Space → Frame → checkout compresses every step into one nervous screen → each step past "add to cart" justifies its existence, with air between decisions.

Return to core

For the method, see design-core/SKILL.md. For the marketing filter (which runs here), see design-core/references/marketing.md. For the words on the page — which sell at least as hard as the visuals — see design-core/references/copy.md. For the layers protocol, see design-core/references/layers.md.

Frequently asked questions

What does the Design Ecommerce AI skill do?

Ecommerce / product site lens. Use when the site's purpose is to sell physical or digital products — online stores, product detail pages, catalogues, shopping cart flows. Load after design-core has established why the site exists and confirmed the goal is purchase. Does not replace design-core; adds subtype-specific priorities, typical failures, and layer-by-layer guidance.

Why use Design Ecommerce on TypingMind?

Because you install it once and use it with any model. Design Ecommerce is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design Ecommerce in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/arimaML/universal-design/tree/main/design-ecommerce. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Design Ecommerce?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design Ecommerce?

As many as you like. As long as a model supports skills, you can use Design Ecommerce with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design Ecommerce AI skill free?

Yes. It is published on GitHub by arimaML under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇