dicce-framework-product

Audits product onboarding and in-app UX using the DICCE framework.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/chrisschouk/chrisscho-uk-marketing-skills --skill dicce-framework-product-chrisschouk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dicce-framework-product
Source: https://github.com/chrisschouk/chrisscho-uk-marketing-skills/tree/main/skills/_parked/dicce-framework-product
Command: npx skills add https://github.com/chrisschouk/chrisscho-uk-marketing-skills --skill dicce-framework-product-chrisschouk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often ship onboarding flows and in-app interfaces without a structured way to evaluate whether users reach value quickly, understand controls, and recover from errors. This Skill applies the DICCE framework (Desire, Interest, Connection, Clarity, Execution) to systematically audit product UX from first login to feature mastery. ## Core Features & Use Cases - Five-Pillar UX Audit: Evaluates Desire (aha moment in first 30 seconds), Interest (interactive feedback loops), Connection (humanized error states), Clarity (self-explanatory controls), and Execution (shortcuts for power users). - Actionable Checklist: Provides a concrete audit checklist covering aha moments, visual feedback, error recovery, labeling, and workflow speed. - Use Case: A product manager preparing a new dashboard release asks for a DICCE audit and receives a structured review of onboarding friction, empty states, tooltip clarity, and keyboard shortcut coverage before launch. ## Quick Start Audit my product onboarding flow using the DICCE framework and list the gaps in each of the five pillars.

Frequently Asked Questions about dicce-framework-product

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

FAQPage Schema
How do I audit my product onboarding UX?▼

Run a DICCE audit that scores five pillars: Desire (aha moment within 30 seconds of login), Interest (interactive feedback), Connection (helpful error states), Clarity (labeled controls), and Execution (shortcuts). Each pillar produces concrete findings and fixes.

What is the DICCE framework for product design?▼

DICCE stands for Desire, Interest, Connection, Clarity, and Execution. It is a structured method for evaluating in-app user experience from first login through feature mastery, focusing on activation rates and retention.

How do I improve empty states and error messages in my app?▼

Apply the Connection pillar: error messages should explain what happened and offer a one-click fix button rather than dead ends. Empty states should guide users toward their next action instead of showing blank screens.

When should I use a UX audit checklist versus user testing?▼

Use the DICCE checklist for fast heuristic reviews before release or when user testing is impractical. It catches obvious friction like unclear labels and missing feedback, but does not replace behavioral data from real users.

Does this framework cover feature activation for power users?▼

Yes, the Execution pillar specifically addresses power-user workflows, including quick-prompt presets, keyboard shortcuts, fast execution pathways, and easy export options for repetitive tasks.