Skills ecommerce
πŸ“¦

ecommerce

Content revision r1 Safe βš™οΈ External commands🌐 Network access

Build E-commerce Systems

E-commerce teams need clear models for products, carts, orders, payment, and inventory. This skill guides Claude, Codex, and Claude Code through practical architecture, checkout, compliance, and review workflows.

Supports: Claude Codex Code(CC)
πŸ₯‰ 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "ecommerce" from https://skillstore.io/skills/daichihoshina-ecommerce.md and its manifest at https://skillstore.io/api/skills/daichihoshina-ecommerce/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "ecommerce". Plan the main entities for a fashion store.

Expected outcome:

  • Product stores shared catalog details and images.
  • Variant tracks SKU, size, color, price, and stock.
  • Cart holds selected items before checkout.
  • Order records the confirmed purchase and delivery status.
  • Payment stores provider status without card data.

Using "ecommerce". Review checkout security for a custom store.

Expected outcome:

  • Use hosted payment fields or provider tokens for card handling.
  • Force HTTPS on all customer and payment pages.
  • Add CSRF and XSS controls to cart and checkout forms.
  • Record payment callbacks with idempotency checks.
  • Keep audit logs for order and payment state changes.

Using "ecommerce". Compare Shopify and a custom build for our catalog.

Expected outcome:

  • Shopify reduces platform work and provides mature commerce APIs.
  • A custom build gives more control over domain logic and integrations.
  • Compare catalog size, checkout needs, compliance scope, and maintenance cost.
  • Validate API limits and payment requirements before choosing.

Security Audit

Safe
v9 β€’ 7/6/2026 Open versioned report

No evidence found of command execution, system reconnaissance, obfuscation, malicious networking, or prompt injection. All static findings are false positives from Markdown fences, sample API routes, a public documentation URL, and Unicode-rich Japanese content. The skill provides e-commerce design guidance only.

2
Files scanned
316
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History β†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/daichihoshina-ecommerce/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/daichihoshina-ecommerce/security.svg)](https://skillstore.io/skills/daichihoshina-ecommerce?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/daichihoshina-ecommerce?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/daichihoshina-ecommerce/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/daichihoshina-ecommerce.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA Β· BibTeX Β· CFF)

APA citation

DaichiHoshina. (2026). ecommerce security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/daichihoshina-ecommerce/audits/9

BibTeX citation

@techreport{daichihoshina-daichihoshina-ecommerce-2026, author = {DaichiHoshina}, title = {ecommerce security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/daichihoshina-ecommerce/audits/9}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "ecommerce security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "DaichiHoshina" date-released: "2026-07-06" url: "https://skillstore.io/skills/daichihoshina-ecommerce/audits/9" identifiers: - type: other value: "skillstore:daichihoshina-ecommerce:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Plan a New Store

Create core domain models, state flows, and requirements before implementation.

Review Checkout Readiness

Check inventory reservation, payment handling, order states, and timeout behavior.

Choose Platform Integrations

Compare Shopify, STORES, custom payment providers, and search services for a project.

Try These Prompts

Create a Store Checklist
Build a launch checklist for a small online store. Cover product management, cart behavior, payments, customer accounts, legal pages, and security basics.
Design the Domain Model
Design the domain model for an e-commerce site. Include products, variants, carts, orders, customers, payments, inventory states, and key relationships.
Review an Existing Checkout
Review my checkout flow for gaps. Check stock reservation, payment status handling, order confirmation, timeout release, and customer error states.
Plan High-Traffic Operations
Plan a high-traffic inventory and payment flow. Include optimistic locking, idempotent payment callbacks, stock release rules, audit logging, and recovery paths.

Best Practices

  • Use optimistic locking or equivalent safeguards for stock reservation.
  • Make payment callbacks idempotent to handle duplicate provider events.
  • Keep card data outside the application by using trusted payment providers.

Avoid

  • Do not hold cart inventory forever without timeout release.
  • Do not store raw credit card numbers in the application database.
  • Do not combine every checkout step into one unrecoverable transaction.

Frequently Asked Questions

What does this skill help build?
It helps plan product catalogs, carts, checkout flows, payments, orders, inventory, and compliance checks.
Does it include payment provider guidance?
Yes. It references hosted payment options and common providers such as Stripe, GMO, PAY.JP, and platform payments.
Can it review an existing store?
Yes. It can structure a review around checkout, inventory, security, legal pages, and performance targets.
Does it generate production-ready code?
No. It provides design guidance and examples that need project-specific implementation and testing.
Is it useful for Shopify projects?
Yes. It includes Shopify and Hydrogen planning prompts, plus platform comparison guidance.
Does it replace compliance review?
No. Use qualified legal and PCI DSS experts for final compliance decisions.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

34f316ba14ef36c7a620fc09f2676d2429997a77

Maintenance freshness

7/18/2026

Usage

4 downloads Β· 165 views

File structure

πŸ“„ audit_output.json

πŸ“„ SKILL.md

View all