dukkani-dashboard

Document dashboard architecture with hooks, API boundaries, stores, and product form logic.

9|2|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/FindMalek/dukkani --skill dukkani-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dukkani-dashboard
Source: https://github.com/FindMalek/dukkani/tree/main/.cursor/skills/dukkani-dashboard
Command: npx skills add https://github.com/FindMalek/dukkani --skill dukkani-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps frontend teams organize the dashboard architecture by clearly documenting the distinctions between hooks, API boundaries, controllers, stores, and the product form logic, improving consistency and maintainability.

Core Features & Use Cases

  • Clear separation of concerns between API access and controller logic within the apps/dashboard area.
  • Documented state management with stores and reusable product-form components to accelerate feature delivery.
  • Use Case: a developer adding a new product form workflow follows the documented layout to wire hooks, stores, and UI components in a cohesive, testable way.

Quick Start

Set up the dashboard feature following the documented layout and start implementing the product form and hooks.

Frequently Asked Questions about dukkani-dashboard

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

FAQPage Schema
How do I organize frontend dashboard architecture for product management?

Organize frontend dashboard architecture by clarifying hooks, API boundaries, stores, and product form logic to ensure consistent separation of concerns and maintainability across the application.

What is the best way to separate API access from controller logic in a dashboard app?

Separate API access from controller logic by documenting strict boundaries within the apps/dashboard area, ensuring that data retrieval operations remain decoupled from state and component logic.

How do I wire hooks and stores for a new product form workflow?

Wire hooks and stores for a product form workflow by following the documented file layout to connect reusable form components, state management, and UI interactions in a cohesive, testable way.

Does this dashboard architecture approach require specific state management libraries?

The dashboard architecture approach documents state management using stores without requiring specific external libraries, relying instead on documented interaction flows and import patterns across the module.

What are the limitations of documenting dashboard architecture through hooks and stores?

Limitations include being scoped specifically to the dashboard module and product form logic, meaning the documented file layout and interaction flows may not directly map to other application areas.