Reviews code changes from a design-engineer perspective -- component architecture, prop API design, separation of concerns, performance, accessibility in code, and DRY principles. Use proactively after writing code.
Next.js domain expert for file conventions, RSC boundaries, data patterns, metadata, composition patterns, error handling, and React 19 APIs. Use when writing or reviewing Next.js code.
Deeply analyzes PRDs and product documents from a designer's perspective. Extracts personas, user stories, competitive references, design questions, and open decisions. Use when analyzing a PRD, product spec, or Google Doc URL. More thorough than /ops lens for complex documents.
Conducts web research, Slack searches, and competitive analysis. Produces structured summaries with key findings, implications, and sources. Use when asked to research a topic, find competitors, or gather information.
Runs tests and reports results using Vitest. Use when running test suites, checking coverage, debugging test failures, or writing new tests.
Browser automation — login flows, form submission, screenshots, data extraction.
Cross-model plan review via OpenAI Codex CLI.
Multi-angle investigation across code, vault, systems, and workflows. Use when you need an audit, blind-spot review, dependency map, inconsistency hunt, architecture investigation, workflow fragility review, risk review, or a 'what are we missing?' pass.
AI image generation and editing via CLI scripts.
Optimize images and videos — compress, convert, resize.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A vault system for Claude Code. Gives Claude persistent memory, design intelligence, quality agents, and smart onboarding. Built for the design team at Razorpay.
/plugin marketplace add nawwwal/dex
/plugin install core@nawwwal-dex # everyone — setup, memory, workflow
/plugin install design@nawwwal-dex # designers — critique, dashboard, UI review
/plugin install tools@nawwwal-dex # optional — research, dev, creative tools
/dex setup
Add the marketplace once, then install the plugins you need. /dex setup reads your Slack and DevRev (with your permission) to generate a personalized CLAUDE.md and scaffold your memory structure.
| Category | Skills |
|---|---|
| Design | dashboard-design, critique-5f, design |
| Thinking | council, codex, deep-research |
| Development | tdd, react-doctor, agent-browser, agent-development |
| Workflow | assistant, ops, today, switch-project |
| Writing | writing-skills, beautiful-mermaid, generate-image |
| Meta | dex, self-review-gather, reflect-others |
Specialized subagents Claude spawns automatically: code reviewer, design reviewer, blade implementer, standup writer, sprint planner, animation expert, Next.js expert, GLSL reviewer, and more.
/dex setup creates this structure (one-time, outside the plugin):
~/.claude/
├── CLAUDE.md ← personalized identity + behavioral rules
├── TASKS.md ← task tracking
├── memory/ ← 20 files: goals, patterns, decisions, voice, projects, etc.
├── career/ ← promotion case, evidence
├── log/ ← session journals
├── sessions/ ← session state persistence
├── config/ ← project registry
├── work/ ← project workspaces
├── archive/ ← archived decisions, patterns
└── people/ ← people profiles
memory/projects.md is a lightweight index that points into work/ for project context.
Plugin files are managed by the plugin system. To customize a skill or agent:
~/.claude/skills/ or ~/.claude/agents/Your customizations are never overwritten by plugin updates.
Dex does not require ~/.agents/skills or ~/.agents/agents to mirror ~/.claude/.
Leave ~/.agents/ available for tools that manage their own installs there.
If you're developing dex (editing skills, agents, templates):
Working directory: Always ~/dex/.
After editing: Start a new Claude session or run /reload-plugins. Changes are live.
Release maintenance is project-local, not part of the shipped plugin.
dex setup workflow..claude/skills/dex/ and .codex/skills/dex/.When you're ready to push updates to teammates:
/dex release tools # patch bump tools
/dex release tools minor # minor bump tools
/dex release tools major # major bump tools
The project-level release skill bumps the selected plugin version, updates marketplace metadata, commits, tags, pushes, and creates a GitHub Release with changelog notes. Teammates update with:
/plugin update dex@nawwwal-dex
/plugin update core@nawwwal-dex
/plugin update design@nawwwal-dex
/plugin update tools@nawwwal-dex
Or reload plugins in an active session:
/reload-plugins
npx claudepluginhub nawwwal/dex --plugin toolsMemory scaffolding, core workflow, and onboarding
Design critique, dashboard patterns, UI review, motion
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Skill and agent authoring tools: generate, audit, and improve Claude Code skills, commands, and agents
Complete collection of 30 Claude Code skills for document processing, development, business productivity, and creative tasks
Persistent memory across sessions. Learns preferences, conventions, and corrections automatically.
Meta-cognitive tools for Claude Code self-improvement. Learn from feedback, optimize configuration, and evolve your AI development workflow.
114 battle-tested skills for Claude Code. Session memory, git workflows, database migrations, security scanning, deployments, and more. Auto-trigger commands and project handoffs via markdown-based skills.