dex

Automate Dex onboarding by generating DESIGN.md and integrating it into CLAUDE memory.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nawwwal/dex --skill dex-nawwwal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dex
Source: https://github.com/nawwwal/dex/tree/main/plugins/core/skills/dex
Command: npx skills add https://github.com/nawwwal/dex --skill dex-nawwwal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dex onboarding often requires manual setup and capturing project design context. This skill automates the onboarding flow and design-context integration into CLAUDE's memory, reducing setup time and ensuring consistency.

Core Features & Use Cases

  • Dispatches to either project setup or design-context capture by reading Dex's setup.md or design-context.md and generating a persistent DESIGN.md.
  • Ensures idempotent writes and minimal changes to existing CLAUDE state, keeping design context up-to-date.
  • Use Case: New Dex users get a ready-to-load design context and project scaffold without manual configuration.

Quick Start

Run the dex setup command to initialize your Dex onboarding and create or update the design context file.

Frequently Asked Questions about dex

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

FAQPage Schema
How do I automate design context capture for new project onboarding?

Automating design context capture involves dispatching to a Markdown flow to generate a persistent DESIGN.md and integrate it into CLAUDE's memory. This reduces manual setup time and keeps project state consistent.

What is the best way to initialize a design system setup using Markdown?

Initializing a design system setup uses an automated flow that reads setup.md or design-context.md files. It safely generates a persistent DESIGN.md file and integrates it into CLAUDE's memory with idempotent writes.

Can I use frontmatter configuration to trigger project setup commands?

Yes, frontmatter-driven configuration allows invoking the setup process using specific commands like [setup | setup design]. This triggers the appropriate Markdown flow to capture design context safely.

Does updating the design system context overwrite existing CLAUDE memory?

No, updating design context ensures minimal changes to existing CLAUDE state and performs idempotent writes. It safely reads internal files to keep design context up-to-date without breaking current configurations.

Why does my persistent DESIGN.md file need to be integrated into memory?

Integrating DESIGN.md into memory ensures CLAUDE maintains a persistent, up-to-date understanding of your project's design context. This prevents manual configuration drift and maintains consistent onboarding state.