Menu
Monorepo architecture, app boundaries, package ownership, and cross-domain implementation guidance for Dukkani.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns. Keywords: Tailwind v4, shadcn/ui, @tailwindcss/vite, @theme inline, dark mode, CSS variables, hsl() wrapper, components.json, React theming, theme switching, colors not working, variables broken, theme not applying, @plugin directive, typography plugin, forms plugin, prose class, @tailwindcss/typography, @tailwindcss/forms
apps/dashboard src layout — hooks (api vs controllers), stores, lib, product form.
apps/dashboard src layout — hooks (api vs controllers), stores, lib, product form.
Storefront app guidance for product browsing, cart, checkout, localization, and oRPC integration in apps/storefront.
Best practices for Remotion - Video creation in React
apps/dashboard src layout — hooks (api vs controllers), stores, lib, product form.
| name | dukkani-architecture |
| description | Monorepo architecture, app boundaries, package ownership, and cross-domain implementation guidance for Dukkani. |
| triggers | ["monorepo architecture","app boundaries","package boundaries","turborepo structure","where should this code live"] |
Use this skill when deciding where code should live, how apps/packages should interact, or how to structure cross-cutting changes.
apps/* own product surfaces and route composition.packages/* own reusable logic and shared abstractions.@dukkani/common.apps/api: API entrypoint for oRPC/OpenAPI/auth/webhooks.apps/dashboard: Merchant/admin product.apps/storefront: Customer storefront and checkout.apps/web: Marketing/public website.Prioritize these packages when placing logic:
@dukkani/common: schemas, entities, shared domain helpers.@dukkani/orpc: API routers and client contracts.@dukkani/core: server bootstrap composition (auth + db + env).@dukkani/db, @dukkani/storage, @dukkani/logger, @dukkani/tracing: infra concerns.@dukkani/env for typed env access..cursor/rules/00-project-overview.mdc and per-domain .mdc files as canonical project rules.For apps/dashboard folder structure, hooks (api vs controllers), stores, and product form patterns, use .cursor/rules/apps/dashboard.mdc or the dukkani-dashboard Windsurf skill.