By rizkiridha
Run agentic workflows to transform abstract design problems into evidence-based UX briefs: initialize workspace, ingest context from Slack/emails/docs, dispatch parallel agents for research, competitive UX mapping, audits with accessibility checks, ideation synthesis, outputting DESIGN-BRIEF.md ready for Figma.
Specialist agent — maps the competitive landscape and surfaces patterns and gaps. Outputs COMPETITIVE.md. Dispatched by design:run orchestrator.
Specialist agent — audits the current UX using the production URL or screenshot. Outputs CRITIQUE.md with severity-rated findings. Dispatched by design:run orchestrator.
Specialist agent — synthesizes all Wave 1 outputs into a reframed problem and design tensions. No directions. No solutions. Outputs IDEATION.md. Dispatched by design:run orchestrator after Wave 1 completes.
Internal orchestrator — manages wave scheduling and agent dispatch for design:run. Not user-invokable. Called by design:run skill.
Specialist agent — synthesizes pasted context from BRIEF.md into a structured UX problem statement. Outputs RESEARCH.md. Dispatched by design:run orchestrator.
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.
An agentic CLI workflow that moves designers from scattered context to evidence-based design brief — before they open Figma.
Designers face a common challenge:
Context lives everywhere. The designer holds it all in their head — or doesn't. Important insights get lost. Decisions get made without full picture.
This system brings context together, validates understanding, and surfaces gaps — before design begins.
/design:new → Create project workspace
↓
/design:feed → Paste MoMs, emails, docs, Slack threads
↓
/design:validate → Verify understanding, detect conflicts
↓
/design:run → Run agents (Research → Competitive → Critique)
↓
/design:validate → Validate research synthesis
↓
/design:brief → Get your evidence-based brief
↓
Open Figma
| Before | After |
|---|---|
| MoMs in Slack | All context in .design/BRIEF.md |
| Research in Notion | Synthesized in RESEARCH.md |
| Competitive intel scattered | Mapped in COMPETITIVE.md |
| Feedback in emails | Traced to source in BRIEF.md |
| "What do we know?" | Check GAPS.md or run /design:status |
Paste anything — MoMs, emails, research docs, Slack threads. The system accumulates all context in one place, traceable to source.
Before agents run, validate your understanding:
The system surfaces what's missing:
You'll know what you don't know.
The system remembers past issues:
Future runs learn from history.
| Command | Purpose |
|---|---|
/design:new | Create project workspace |
/design:feed | Add context (MoM, email, docs, Slack) |
/design:validate | Verify understanding, detect conflicts, check freshness |
/design:run | Execute research agents |
/design:brief | Generate design brief |
/design:status | Check current state and next step |
.design/
BRIEF.md ← All context, traceable to source
GAPS.md ← What we know vs missing
DESIGN-STATE.md ← Workflow state tracker
VALIDATION-REPORT.md ← Problem validation results
PROBLEM-REFLECTION.md ← Your confirmed understanding
LEARNING-LOG.md ← Past issues learned
research/
RESEARCH.md ← Problem statement
COMPETITIVE.md ← Landscape analysis
CRITIQUE.md ← UX audit
IDEATION.md ← Design tensions
DESIGN-BRIEF.md ← Final output for Figma
/design:feed
> Paste MoM from product sync...
/design:validate
> ## Stakeholders
> | Source | Role | Key Input |
> |--------|------|-----------|
> | MoM - Product Sync | PM | Users can't find export |
>
> ## Conflicts
> None detected
>
> ## Context Age
> 2026-03-14 (today) ✅ Fresh
>
> ## Problem Reflection
> What problem are we solving? [Your answer]
>
> Ready to proceed? (yes)
/design:run (Wave 1 complete)
/design:validate
> ## Research Validation
> Research says: "Users struggle to locate export..."
>
> Your earlier reflection: "Users can't find export button"
>
> ✓ Matches my understanding
> ✓ Worth solving
> ✓ Enough evidence
>
> Proceed to Ideation? (yes)
"What problem are we actually solving?" — Synthesizes context into a clear problem statement with user needs and constraints.
"What does the landscape look like?" — Maps competitors, table stakes, gaps, and opportunities. Descriptive, not prescriptive.
"Where is the current experience failing?" — Audits your product via URL/screenshot. Severity-rated findings + what's working.
"What tensions must we navigate?" — Synthesizes into design tensions and provocations. Ends with questions, not answers.
The designer brings the solutions. Agents provide the raw material.
npx claudepluginhub rizkiridha/abstract-to-concreate-design --plugin abstract-to-concrete-designCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,561 supported skills.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer