dukkani-storefront

Guide consistent storefront implementation across apps/storefront with architecture rules.

9|2|Updated Nov 10, 2025

Search Tags:#architecture #localization #checkout #ecommerce #storefront #orpc #product-listing

Ready to run

npx skills add https://github.com/FindMalek/dukkani --skill dukkani-storefront

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dukkani-storefront
Source: https://github.com/FindMalek/dukkani/tree/main/.cursor/skills/dukkani-storefront
Command: npx skills add https://github.com/FindMalek/dukkani --skill dukkani-storefront

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fragmented storefront implementations across apps/storefront lead to inconsistent behavior, duplicate logic, and difficulty enforcing architecture and localization standards.

Core Features & Use Cases

Product listing and product detail flows.
Cart state and checkout flow.
Localized storefront routes under app/[lang].
Storefront-specific API route handling in app/api/storefront/[[...rest]]/route.ts.

Quick Start

Apply this guide to align storefront work across apps/storefront, from product listing to localization and ORPC integration.

Frequently Asked Questions about dukkani-storefront

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a multi-language storefront to prevent fragmented architecture?▼

Structure a multi-language storefront using localized routes under app/[lang] to prevent fragmented architecture. This enforces consistent behavior across product listing, cart, and checkout flows while maintaining unified state and data management standards.

How do I implement storefront API route handling with ORPC integration?▼

Implement storefront API route handling by configuring endpoints in app/api/storefront/[[...rest]]/route.ts. This structure integrates ORPC directly into your multi-language storefront routes to manage data fetching and state consistently.

What is the best way to separate server components and client boundaries in an ecommerce checkout flow?▼

The best way to separate boundaries in an ecommerce checkout flow is by enforcing strict server component usage with clearly defined client boundaries. This architecture manages cart state efficiently and ensures robust error handling.

Do I need specific API route configurations for localized storefront routes?▼

Yes, localized storefront routes require specific API route handling configured in app/api/storefront/[[...rest]]/route.ts. This setup ensures that multi-language product listing and checkout data resolve correctly across different locales.

Why does my storefront architecture have duplicate logic across product listing and cart flows?▼

Storefront architecture develops duplicate logic when fragmented implementations lack unified state and data management rules. Applying consistent architecture rules across app/storefront eliminates this duplication for product listing and cart flows.